Actually I am not interested on rows that have been committed. I am interested on the rows that have been changed but not commited yet. As I understand the triggers trigger of of a commit. The example that you are refering to is for undoing the already commited rows. I am merely interested in seeing the rows that are in my transaction queue before the commit.
On Thu, Apr 17, 2008 at 1:54 PM, Dennis Cote <[EMAIL PROTECTED]> wrote: > Alex Katebi wrote: > > Can you give an example on how to use this. Basically I want to see > > (select) only the uncommited rows. > > > > You will have to keep track of the rows that have been changed yourself. > > You can have SQLite do it for you if you create a change_log table and > then setup triggers to add the rowids of any rows modified during the > transaction. You clear this table at the beginning of your transaction. > The triggers will insert rows for each change to the table. At the end > of the transaction you can select all the rows from the main table that > have their rowids stored in the change_log table. > > If you want to get fancier you can look at this page for more ideas > http://www.sqlite.org/cvstrac/wiki?p=UndoRedo > > 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
