On 4/22/15, Simon Slavin <slavins at bigfraud.org> wrote: > Dear folks, > > I have a setup where an app creates a single-user SQLite database by opening > a connection, uses it for a number of complicated things, closes the > connection, then deletes the database before quitting. The data which goes > into this database is highly sensitive and it's very important that my app > deletes all files which might contain this data (journal, temp index, etc.) > before my application quits.
Can you add the SQLITE_OPEN_MEMORY option to the sqlite3_open() call, forcing SQLite to keep all content exclusively in memory and never writing to disk? -- D. Richard Hipp drh at sqlite.org
