That doesn't sound healthy at all. If your application dies, what happens to the database? What if something rogue starts hitting it and just chews up your memory?
IMO, Mem databases should be short lived and treated simply as an intentional cache. I get they're fast, but, long term life for a finite resource isn't something I want kicking around when an application dies. On Mon, Jan 14, 2019 at 1:43 PM Thomas Kurz <sqlite.2...@t-net.ruhr> wrote: > It would also be very helpful if more control about in-memory-databases > was available. As far as I have understood, an in-memory database is > deleted when the last connection closes. This requires me to always hold a > connection to an in-memory database even if don't need it right now. > > Maybe one could introduce a pragma "persistent_inmemory" that allows to > keep an in-memory-database until explicitely deleted. (DROP DATABASE IF > EXISTS ...) > > _______________________________________________ > 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
