Hick Gunter wrote: > Reading "stale" data (i.e. the DB state at the beginning of a transaction) > is at least almost always caused by indvertently leaving a transaction > open. Setting the journal mode to WAL hides this problem, because the > writer is no longer blocked by the reader's transaction. Disable WAL mode > and you will probably find that the writer will find that the "database is > locked".
Alternatively, put explicit BEGIN/COMMITs around all reads; then you'll see if you accidentally try to nest transactions. Regards, Clemens _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
