-
-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[queued_ltr_backports] OGR provider: only enable journal_mode = wal when editing. requires GDAL >= 3.4.2 (fixes #23991) #47301
[queued_ltr_backports] OGR provider: only enable journal_mode = wal when editing. requires GDAL >= 3.4.2 (fixes #23991) #47301
Conversation
0df8b3e
to
a78eaa7
Compare
a78eaa7
to
8bc3b5b
Compare
@rouault can you rebase this on queued_ltr_backports again? |
…DAL >= 3.4.2 (fixes qgis#23991) This requires the NOLOCK open option of the GPKG driver added per OSGeo/gdal#5207 For earlier GDAL version, previous behaviour is kept. With GDAL >= 3.4.2, when creating a QgsOgrProvider object, we first open it in update mode without forcing WAL, to get the appropriate capabilities, close it, and re-open it in read-only mode with the NOLOCK=YES open option. This option will only be honoured if the file wasn't already in WAL mode. When editing a layer, the file is re-opened in update mode and with enabling WAL to avoid blocking between readers and writers. When closing a file, journal mode is attempted to be reset to DELETE as before. I've verified that test_provider_ogr_gpkg.py and test_provider_ogr.py pass locally with GDAL master + OSGeo/gdal#5207
f6918a5
to
d75f9e2
Compare
done |
The QGIS project highly values your contribution and would love to see this work merged! Unfortunately this PR has not had any activity in the last 14 days and is being automatically marked as "stale". If you think this pull request should be merged, please check
|
keep alive |
Backport of PR #47098