> Le 26 mars 2018 à 10:20, Simon Slavin <slav...@bigfraud.org> a écrit : > > On 26 Mar 2018, at 8:57am, Marco Bambini <ma...@sqlabs.net> wrote: > >> So it has nothing to do with which table/row the transaction is modifying? > > Correct. SQLite does not have table-locking or row-locking. Any locks in a > SQLite database lock the entire database. This is a fundamental aspect of > SQLite and one of the reasons it's so fast and simple.
Simon, if this discussion is really around the branch 'server-process-edition', it was my (possibly wrong) understanding that this is not really true. This branch does apply page-level locking, or I got it all wrong. See: https://sqlite.org/src/artifact/0c6bc6f55191b690 > The "server-process-edition" branch contains two modifications to stock > SQLite that work together to provide concurrent read/write transactions using > page-level-locking provided that: > > • All clients are in the same process, and > • The application uses "PRAGMA synchronous=off. -- Best Regards, Meilleures salutations, Met vriendelijke groeten, Olivier Mascia _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
