See https://www.sqlite.org/sharedcache.html and in particular, section 6 at the bottom.
Peter On 5/10/2015 10:42 AM, Joe Pasquariello wrote: > Hello, > > One thread of our Windows application is an HTTP server reading data > from an SQLite database for display by web clients. Some tables are > updated infrequently (minutes), but one contains current status of > numerous machines, and it is written/read relatively frequently. Data > is written to the DB by a dedicated writer thread. The > frequently-written table is temporary in the sense that it is > dropped/created at run-time, and the data doesn't need to persist > between executions. > > My question is whether there is a way for this table to be in memory. > Each thread has its own connection, which I understand to be > necessary. Am I correct that this means they can't share an in-memory > DB or an in-memory TEMP table, because those are restricted to a > single connection? It's very convenient to use SQLite for this purpose > because each client may be interested in a different row or set of > rows from the "real-time" table, and it seems a shame for the shared > data to have to be on disk and not simply in memory. > > Thanks, > > Joe > _______________________________________________ > sqlite-users mailing list > sqlite-users at mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users >
