Re: [sqlite] Controlling the lifetime of shared-cache, in-memory SQLite databases.

Errr … Clemens has cites. I don’t. Believe him, not me. Sorry about that. Simon. ___ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Controlling the lifetime of shared-cache, in-memory SQLite databases.

Randall Smith wrote: > A shared-cache, in-memory database is "persistent" across connections > from the same process that do not overlap in time? No. says: | The database is automatically deleted and memory is reclaimed when the | last

Re: [sqlite] Controlling the lifetime of shared-cache, in-memory SQLite databases.

On 28 Apr 2017, at 2:14am, Randall Smith wrote: > (a) Is this right? A shared-cache, in-memory database is "persistent" > across connections from the same process that do not overlap in time? Correct. SQLite doesn’t count connections and do anything special when

[sqlite] Controlling the lifetime of shared-cache, in-memory SQLite databases.

SQLite has the useful ability to provide an in-memory database that can be shared by multiple connections in the same process by opening the DB with the following syntax: rc = sqlite3_open("file:memdb1?mode=memory=shared", ); I'm testing a database having this configuration in a unit