GEODIFF_makeCopySqlite does not close source DB correctly #132
Labels
bug
Something isn't working
Comments
wonder-sk
added a commit
that referenced
this issue
Jun 24, 2021
Even though it is possible to open databases in WAL mode as read-only since sqlite 3.22 (released in 2018), there seem to be a couple of limitations: https://sqlite.org/wal.html#readonly The -wal and -shm are left behind even after the database is closed. So better let's open it in read/write mode as usual and those files will get proper treatment - they will be removed when connection is closed.
wonder-sk
added a commit
that referenced
this issue
Jun 25, 2021
Even though it is possible to open databases in WAL mode as read-only since sqlite 3.22 (released in 2018), there seem to be a couple of limitations: https://sqlite.org/wal.html#readonly The -wal and -shm are left behind even after the database is closed. So better let's open it in read/write mode as usual and those files will get proper treatment - they will be removed when connection is closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If
a.gpkgis in WAL mode, runninggeodiff copy a.gpkg b.gpkgwill leavea.gpkg-walanda.gpkg-shmfiles when it is finished, so probably it is not closing the source database correctly.The text was updated successfully, but these errors were encountered: