AFAIK, your best bet is to put a file db on a ramdisk (tmpfs). The ":memory:" DB is per connection only.
Wout. On Mon, Jan 14, 2019 at 11:37 AM Dominique Devienne <ddevie...@gmail.com> wrote: > According to [1] WAL mode does not apply to in-memory databases. > But that's an old post, and not quite authoritative when not from the > official SQLite docs. > > I'd like to benefit from the MVCC of WAL mode, but for an in-memory > database, > with different threads, each with its own connection, accessing a single > in-memory DB. > > Can this do done? If not, why is WAL mode deemed not useful for in-memory? > i.e. is there a work-around that makes WAL-mode in-memory superfluous? > Or it's not superfluous and not supported, but could technically be > supported? > > Thanks for any insights. --DD > > [1] > > https://stackoverflow.com/questions/28358153/sqlite-wal-mode-in-memory-database-with-private-cache > _______________________________________________ > 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
