Your impression is only correct if you are running in WAL journal_mode. In all other modes, readers will block the writer(s) and yo need to set a busy timeout or a busy handler.
-----Ursprüngliche Nachricht----- Von: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] Im Auftrag von Gerlando Falauto Gesendet: Dienstag, 07. August 2018 13:55 An: SQLite mailing list <sqlite-users@mailinglists.sqlite.org> Betreff: [EXTERNAL] [sqlite] Database locks Hi, I'm trying to implement a logging system based on SQLite, using python3 package apsw. There's one process constantly writing and another one reading. From time to time I get an exception from the writer, complaining the database is locked. I'm pretty sure there's no other process writing, and I was under the impression that readers should not block writers, they should just see a previous version of the dataset. Is my assumption wrong? The package I'm using is based on Sqlite version 3.9.2, so perhaps it's a bit outdated. Could anyone please shed some light on this topic? Thank you! Gerlando _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users ___________________________________________ Gunter Hick | Software Engineer | Scientific Games International GmbH | Klitschgasse 2-4, A-1130 Vienna | FN 157284 a, HG Wien, DVR: 0430013 | (O) +43 1 80100 - 0 May be privileged. May be confidential. Please delete if not the addressee. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
