On Jun 28, 2019, at 2:12 AM, ingo <i...@ingoogni.nl> wrote: > > I see a wal file being created and deleted. Just for my > understanding, would it be of advantage to have a second persistent > connection just for keeping the wal alive?
You’ve basically got it backwards. It’s a *good thing* when the WAL file disappears: it means the prior connection was able to push everything from the WAL into the DB file, so the WAL isn’t needed on the next DB conn until more writes are attempted. Conversely, if the last DB conn closes and the WAL is left behind, it means someone didn’t clean SQLite up nicely, so on the first subsequent connection to the DB, that SQLite instance will start trying to recover. A WAL file left behind is a sign of a problem in the app which should be corrected. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
