Hello, The following scenario raises a BUSY error immediately
process A. keeps a write lock process B keeps a read-lock and tries to promote this to a write-lock This is the traditional SQLite deadlock situation, detected by the engine as soon as possible. In my test this still occurs unchanged after switching to WAL. Should process B not be allowed to carry on now? Using WAL, A. can still commit while B. keeps a read-lock. Thanks for this version, -- Edzard _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
