>Another interesting distinction between shared and private cache mode >I found while experimenting. Ordinarily if connection A is in the >middle of fetching result rows from a SELECT (i.e., sqlite3_step was called, >but not sqlite3_reset), and connection B tries to do a CREATE/UPDATE/DELETE, >B will get back SQLITE_BUSY. However, with a shared cache, B's operation >will immediately succeed, provided it doesn't affect the same table(s).
See also Write Ahead Logging journal mode (WAL) where in the case you specified B's operation will succeed even if it is updating a table being read by connection A. https://sqlite.org/wal.html --- The fact that there's a Highway to Hell but only a Stairway to Heaven says a lot about anticipated traffic volume. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
