On Wed, Jun 3, 2009 at 2:41 AM, Nikolaus Rath <nikol...@rath.org> wrote: > Nuno Lucas <ntlu...@gmail.com> writes: >> On Tue, May 26, 2009 at 5:17 PM, Nikolaus Rath <nikol...@rath.org> wrote: >>> Hello, >>> >>> How can I determine the rowid of the last insert if I am accessing the >>> db from different threads? If I understand correctly, >>> last_insert_rowid() won't work reliably in this case. >> >> It should work if you do: >> >> BEGIN >> INSERT ... >> last_insert_rowid() >> END > > That would be very nice. But does "it should work" mean that you know > that it works (and it is documented and guaranteed)? The above sounds a > bit uncertain to me...
It just means I'm too old to assume anything is certain. The Universe is always conspiring against you ;-) What I mean is that if it doesn't work, then you found a bug, most probably in your own code. Regards, ~Nuno Lucas > > Thanks for the clarification, > > -Nikolaus > > -- > »Time flies like an arrow, fruit flies like a Banana.« > > PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6 02CF A9AD B7F8 AE4E 425C > > _______________________________________________ > 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
