I’ve seen the server mode <https://sqlite.org/src/raw/README-server-edition.html?name=0c6bc6f55191b6900595fe37470bbe5772953ab5c64dae967d07a5d58a0c3508> branch, but to me it’s a deal-breaker that it requires SYNCHRONOUS = OFF.
This BEGIN CONCURRENT idea really interests me. By using WAL mode, where I can have synchronous commits, the feature becomes much more valuable. Any word from Mr. Hipp on the status of this branch? Will it ever make it into the official version of SQLite3, perhaps under a compile-time option? > On Mar 22, 2019, at 5:07 PM, Jens Alfke <j...@mooseyard.com> wrote: > > > >> On Mar 22, 2019, at 1:38 PM, Barry Smith <smith.bar...@gmail.com> wrote: >> >> You might be interested in the BEGIN CONCURRENT branch. It does page level >> locking (not quite as granular as row level). >> >> https://www.sqlite.org/cgi/src/doc/begin-concurrent/doc/begin_concurrent.md >> <https://www.sqlite.org/cgi/src/doc/begin-concurrent/doc/begin_concurrent.md> > > Oh, this is interesting. Is this a feature in development that will be > released soon? > > [And to be pedantic: according to those docs, this feature does not do page > level locking; it’s optimistic not pessimistic concurrency.] > > —Jens > _______________________________________________ > sqlite-users mailing list > sqlite-users@mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
