>-----Original Message----- >From: Jacob Steinberger [mailto:trefal...@realitybytes.net] >Sent: Wednesday, August 25, 2010 8:36 PM >To: mysql@lists.mysql.com >Subject: Complicated SQL Query > >I have a requirement to keep track of a set of data, and all changes >that might occur. In order to do this, for each field of the data set, >I've created a table that keeps track of the version, the value, the >time the change was made, and a linking number that links all the >different tables back to a single record. I'm assuming, hoping, and >believe this is a very common setup. > [JS] That's a lot of tables. Do you need separate version tracking for each individual field? Or would it be sufficient to have version tracking for each row, with a list of fields modified and their "before" values?
If the latter, then you can get by with a lot less complexity; if the former, then I think your design might be the only way to go. Regards, Jerry Schwartz Global Information Incorporated 195 Farmington Ave. Farmington, CT 06032 860.674.8796 / FAX: 860.674.8341 E-mail: je...@gii.co.jp Web site: www.the-infoshop.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=arch...@jab.org
