You can add a version field to each row. Then add a seperate table with info with a list of the versions and a flag for deleted. Queries would look for each record that has the highest version number thats not deleted. Having a lot undo/redo info can get kind of complicated, especialy with multiple end users playing with it and chains of dependant changes.
If the info can be modeled as documents this is frequenetly done with CVS. On Fri, 2 Jan 2004 13:06:36 +0530, "karthikeyan.balasubramanian" <[EMAIL PROTECTED]> said: > Hi, > > I posted this question in MySQL mailing list and got no reply. > > The basic problem is that I have committed the transaction and then > replicated to another DB. Now I want to rollback the committed > transaction. > Is there a way to rollback to a particular point. This requirement is > very > similar to rolling back using save points. I guess an option would be to > backup database before changes and restore it if the user is not > satisfied > with the changes he has made. One transaction in my application would > affect > 6-8 tables with at least 50 - 100 records getting inserted/updated or > deleted. > > Please advice > > PS : Wish you all a very Happy New Year > > Karthikeyan B > > > > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
