Another approach could be to create an in-memory database (and in in- memory table, like CREATE TABLE last_transaction(id INTEGER);) and after each write operation save the rowid of the row using sqlite3_last_insert_rowid (in C) or using SELECT last_insert_rowid(); (SQL) into that table.
--- Marco Bambini http://www.sqlabs.net http://www.sqlabs.net/blog/ http://www.sqlabs.net/realsqlserver/ On Apr 17, 2008, at 9:43 PM, Alex Katebi wrote: > The reason I did not keep track in a seperate table was because I > wanted to > do it using triggers. But triggers don't trigger until commit. > > On Thu, Apr 17, 2008 at 3:36 PM, Scott Hess <[EMAIL PROTECTED]> wrote: > >> Until the data is committed, it's not really in the database. If you >> crash, it will be rolled back. So if it's really important to know >> what data has been written to the database but not committed, why >> don't you just track what you're writing to the database in an >> in-memory data structure of some sort? Or, to save space, just track >> the rowid of the rows you modify. >> >> -scott >> >> >> On Thu, Apr 17, 2008 at 12:33 PM, Alex Katebi <[EMAIL PROTECTED]> >> wrote: >>> Hi Richard, >>> >>> create table t1 (name); >>> insert into t1 values ('Alex'); >>> begin; >>> insert into t1 values ('Richard'); >>> select * from t1; >>> >>> How can I select only the second row in the above example? >>> If there is not an easy way to do this I would probably have to use >> another >>> connection then diff the two selects right? >>> >>> Thanks, >>> -Alex >>> >>> >>> >>> >>> >>> On Thu, Apr 17, 2008 at 2:38 PM, D. Richard Hipp <[EMAIL PROTECTED]> >>> wrote: >>> >>>> >>>> On Apr 17, 2008, at 2:35 PM, Alex Katebi wrote: >>>>> Is there a way to select rows that have not been committed yet? >>>>> >>>> >>>> No. SQLite doesn't really commit rows. It commits pages. A >>>> single page might hold multiple rows, only some of which might >>>> have changed. Or a single row might span multiple pages. >>>> >>>> >>>> D. Richard Hipp >>>> [EMAIL PROTECTED] >>>> >>>> >>>> >>>> _______________________________________________ >>>> 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 >>> >> _______________________________________________ >> 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 _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
