Checked this on WIndows 7 & 8, works as expected. This means either Windows 10 has some glitch or the access level to the folder is not correct, files may not be deleted by that process or some antivirus is checking the file while SQLite is trying to delete it, or you are not closing the DB connection fully (though if it works with previous versions of SQLite, this last option should not be the problem).
On 2015-08-15 07:28 PM, Ashwin Hirschi wrote: > > Hello, > > I've recently found SQLite doesn't always remove its journal files > anymore. > > The issue seems to occur when opening WAL databases in read-only mode > (i.e. using SQLITE_OPEN_READONLY). > > A scenario to reproduce this (using version 3.8.11.1) looks like: > > 1. open a WAL database in read-only mode > 2. prepare & finalize a query > 3. close the database > > The "-shm" and "-wal" journal files are created during the prepare() > in step 2. But, after step 3, they're both still present. > > If the database is opened in read-write mode, everything is fine. > Lastly, I'm having the issue on a Windows 10 machine and am not > currently able to test anywhere else... > > So, can anyone else reproduce the above scenario? > > Ashwin. > > P.S. I've also checked some older SQLite versions. It looks like this > unfortunate "non-cleanup" was introduced in 3.8.11. > _______________________________________________ > sqlite-users mailing list > sqlite-users at mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
