Thanks Dannis, The problem is a little bigger. I must have 2 instances of same table: original and latest. Then my problem is what is the best way to: - transform 'original' with same data as 'latest'. This is 'save'. - transform 'latest' with same data as 'original'. This is 'undo'.
I must always have 2 tables. Client will read from original and Administrator will make changes. Then, if Administrator wants to apply those changes to Client a copy from 'latest' to 'original' must happen. Francisco A > On 10-02-26 2:25 PM, Francisco Azevedo wrote: >> Hi all, >> >> I want to create a "publish/undo system" for some tables but i don't >> know what is the best approach to do it. >> Imagine i have a table with columns id (auto-inc), data (text) then i >> want to edit table data (eg: create 2 new rows now, delete one tomorrow, >> update 3 rows tomorow too) and then decide if i want to preserve that >> modification or reverse it to the state it was before start that >> modifications. >> >> > Hi Francisco, > > You should read this page in the wiki > http://www.sqlite.org/cvstrac/wiki?p=UndoRedo. It explains how to do > this sort of undo system using triggers. > > HTH > Dennis Cote > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
