> On Jul 14, 2019, at 10:05 AM, ardi <ardillasdelmo...@gmail.com> wrote: > > Do you have any recommendation for saving the inmemory db in a safe > way?
If you’re going to keep your data in memory, there’s no good reason to use SQLite at all. Just define custom model objects that you can operate on efficiently, and write the data out in a standard format like JSON or XML. (Most frameworks have serialization features that make this easy.) The point of using a database is that you _don’t_ have all the data in memory, and can still access it quickly. This is attractive if you want to scale to large data sets that won’t fit in RAM or which take too long to read/write from storage. If that’s not an issue for you, don’t use a database; it just adds more complexity to your data model layer. —Jens _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
