Here's a long-ago thread on this: http://www.mail-archive.com/sqlite-users@sqlite.org/msg30540.html Looks like it hasn't been addressed, and I've yet to come up for air on it.
There's a ticket out there which looks like the same thing: http://www.sqlite.org/cvstrac/tktview?tn=3338 which is closed, but it sounds like if you put up a simple repro-case you might get a re-hearing on it. -scott On Mon, Oct 19, 2009 at 9:13 AM, Wanadoo Hartwig <hartwig.wiesm...@wanadoo.nl> wrote: > > Am 18.10.2009 um 18:55 schrieb Roger Binns: > >> Wanadoo Hartwig wrote: >>> Slightly different question but related to FTS3. Does anybody know >>> why >>> this fails using FTS3? >> >> It isn't failing. Behind the scenes FTS3 is implemented using 3 other >> tables (try .dump to see). You are indeed seeing the last inserted >> rowid. >> > > As the FTS related tables are modified by a trigger the last rowid > should still be the one of the table "triggering the trigger" and not > of any the tables being modified by the trigger. Isn't this the > general idea of a trigger? > > Hartwig > >> Roger >> _______________________________________________ >> 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