Thanks Richard. I take it this is what you’re talking about
“Even though a disk file is allocated for each temporary database, in practice the temporary database usually resides in the in-memory pager cache and hence there is very little difference between a pure in-memory database created by ":memory:" and a temporary database created by an empty filename. The only difference is that a ":memory:" database must remain in memory at all times whereas parts of a temporary database might be flushed to disk if database becomes large or if SQLite comes under memory pressure.” I’ll have to look into how to increase the in-memory pager cache. ________________________________ From: sqlite-users <sqlite-users-boun...@mailinglists.sqlite.org> on behalf of Richard Hipp <d...@sqlite.org> Sent: Friday, December 15, 2017 7:35:14 PM To: SQLite mailing list Subject: Re: [sqlite] What happens if an in memory database runs out of memory On 12/15/17, x <tam118...@hotmail.com> wrote: > > Is there any easy way of creating a table that will use mem for speed but > revert to disc for backup if memory runs out? > Make the database filename be an empty string. -- D. Richard Hipp d...@sqlite.org _______________________________________________ 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
