> On Feb 11, 2019, at 11:07 PM, Rowan Worth <[email protected]> wrote: > > if process A is updating the DB via write() calls, the locking protocol > ensures that no other process will call write() or fsync(), and in fact not > even read() (because the DB might be in a partially-updated inconsistent > state) before process A has finalised the transaction and called fsync().
WAL mode allows reads while a writer is in a transaction. The readers will ‘see' the state of the database prior to the start of the transaction, until it commits. This is a key reason to use WAL if you have multiple connections to your database — much greater availability. —Jens _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
