Snapshot from before and after an entry

[buratti]

Ok so this question might be a little off topic for this heading but hopefully someone can at least point me in the right direction. My company software uses a MySQL database for its back end data. Its front end software is pretty primitive and basic. I am using MS Access to make up for the shortcomings that this software/front end lacks. So to make sure my custom Access front end would be entering data into the MySQL backend correctly, matching the way the original software does, I need to analyze how the original software enters data first. For one example, if I want my Access front end to enter a new customer, its probably just as simple as entering the data in a new record in the customers table, however, I want to make SURE that that the original front end software doesn't automatically, or behind the scenes, enter any new or related information in any OTHER table when creating that new customer.

So, in theory, a way I thought of testing what the original front end actually does is take a snapshot of the database right before entering a new customer with the original system, and again right after entering a new customer. Then somehow (which is my question) comparing what tables has different data. From there I can confirm if any other tables are effected or not when entering new customers, and design my Access front end accordingly.

I do have MySQL workbench/Server to host the existing database. Any thoughts on how to compare different database states?

 

[sneuberg]

If the tables don't already have a timestamp on them you could add this using table triggers. With that in place you could query all of the tables for records added or modified after your test.

Personally this wouldn't be enough. I'd need to read and understand the existing code. There could be too many variations to test and I'd never be sure I caught everything.