You need WAL mode http://www.sqlite.org/draft/wal.html
Michael D. Black Senior Scientist Advanced Analytics Directorate Advanced GEOINT Solutions Operating Unit Northrop Grumman Information Systems ________________________________ From: sqlite-users-boun...@sqlite.org [sqlite-users-boun...@sqlite.org] on behalf of David Levinson [dlevin...@worldnow.com] Sent: Tuesday, November 22, 2011 9:07 AM To: sqlite-users@sqlite.org Subject: EXT :[sqlite] SQLite Locking Issue From Another Process We have Process A which writes constantly to our SQLite database and we have Process B which occasionally reads from this same database. When Process B opens the database for read-only access and performs a select statement on the database it causes Process A to get SQLITE_BUSY errors when executing the insert statements and will continue to return busy until Process B closes the connection to the database. So my basic question is why is Process B locking the database when it is opening the file for read-only access and not performing any writes on the database being written to by Process A. Is it possible that a select statement can lock a table? Thanks, Dave. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
