Have a database and an application wherein , concurrent writes and reads to/from the db happen (each DB connection is independent , autocommit mode and no SQLITE_BUSY handler / timeout ).
I see "Database is locked" message. Is there a good practice /setting for such high rate of concurrent writes with reads ? I understand that multiple readers with single writer at any time t is the model which sqlite has with various locks/states (unlocked, pending , shared , reserved , exclusive). Will a busy_timeout setting for all connections and making write transactions as "begin immediate" handle the situation ? Any thoughts appreciated . -- View this message in context: http://old.nabble.com/concurrent-writes-and-reads-to--from-DB-tp32784852p32784852.html Sent from the SQLite mailing list archive at Nabble.com. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
