By "constantly writing" I presume you mean "periodically writing". For example doing one independent INSERT every millisecond where there is no dependency from between inserts is "periodic writing". "Constantly writing", from a database perspective, means a single transaction that never ends ...
--- The fact that there's a Highway to Hell but only a Stairway to Heaven says a lot about anticipated traffic volume. >-----Original Message----- >From: sqlite-users [mailto:sqlite-users- >[email protected]] On Behalf Of Gerlando Falauto >Sent: Tuesday, 7 August, 2018 05:55 >To: SQLite mailing list >Subject: [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 >[email protected] >http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
