On Tue, 3 Sep 2019 18:26:01 +0100, you wrote: >> // do SELECT on db1 >> // do UPDATE on db2 > > Do you expect the SELECT to see the results of the previous > UPDATE ? It won't, until the transaction has ended > (unless you arrange this explicitly).
That's the nice thing about this construct: isolation between the SELECT and the UPDATE, the pattern is indeed: * Iterate over unchanged rows, without seeing DELETEs, UPDATEs and INSERTs on the tables in the select, * Be free to act upon the original rows without disturbance of the read. I think it only works for WAL journal mode. -- Regards, Kees Nuyt _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
