editing several layers in geopackage - database is locked

[qgib]

Author Name: Jochen Huber (@huber-j)
Original Redmine Issue: 15754
Affected QGIS version: 2.18.0
Redmine category:data_provider/ogr

---

In a QGIS project with several layers from a single geopackage database, the following problem frequently occurs:
Switch layer to editing mode, do geometry edits, save edits, deactivate layer editing mode.
Switch second layer to editing mode, do geometry edits, try to save edits -> Database provider errors (OGR) e.g. "failed to execute insert: database is locked".
After closing QGIS and reopening the same project, the second layer can be edited and the edits are successfully saved, but the problem occurs again when another layer from the same geopackage is edited.
Maybe this problem is related to the one in #23283.

---

• test.gpkg (Even Rouault)

[qgib]

Author Name: Even Rouault (@rouault)

---

I tried with master on Linux with the attached DB and couldn't reproduce the issue (I'm attaching the simple DB I used for reference). Normally locking issues should have been fixed in 2.18.0 per #0497e4a454c7ad689a0fc7b767208f95d53266b0. Can you have provide a reproducable procedure + test DB ?

---

• 10611 was configured as test.gpkg

---

• test.gpkg (Even Rouault)

[qgib]

Author Name: Jochen Huber (@huber-j)

---

I tried again with the sample DB you supplied and still experienced the same problem. Open QGIS, create a new project, add all layers from the DB, edit the geometry of one layer and save, edit the geometry of the second layer -> saving fails.
A test with the DB located on a local drive did NOT show the problem, prompting further investigation:

• Network share on Windows Server 2008 R2 Standard, Access via domain-integrated DFS (Distributed File System): Problem occurs
• Network share on Windows Server 2008 R2 Standard, direct access to server: Works fine
• Network share on Windows Server 2012 R2 Standard (direct access), Windows 7 Professional SP 1, QNAP NAS or Western Digital MyBook Live: Works fine

So this seems to be a problem which only occurs when accessing a network share via DFS (which is the standard case in our company). Interestingly, there is no problem with Spatialite DBs, so there seems to be a difference in how QGIS accesses Geopackage DBs vs. Spatialite DBs.

[qgib]

Author Name: Jérôme Guélat (Jérôme Guélat)

---

We are also experiencing this problem with QGIS 2.18.3 (OGR/GDAL 2.1.3) on Windows.

[qgib]

Author Name: Ger CO (Ger CO)

---

Same here on Win 7 and qgis 2.18.3

[qgib]

Author Name: Giovanni Manghi (@gioman)

---

• easy_fix was configured as 0
• regression was configured as 0

[qgib]

Author Name: Even Rouault (@rouault)

---

Can anyone retry with QGIS master ? Changes done in 8f3d44d should likely fix that

---

• description was changed from In a QGIS project with several layers from a single geopackage database, the following problem frequently occurs:
  Switch layer to editing mode, do geometry edits, save edits, deactivate layer editing mode.
  Switch second layer to editing mode, do geometry edits, try to save edits -> Database provider errors (OGR) e.g. "failed to execute insert: database is locked".
  After closing QGIS and reopening the same project, the second layer can be edited and the edits are successfully saved, but the problem occurs again when another layer from the same geopackage is edited.
  Maybe this problem is related to the one in geopackage edits workflow is broken #23283. to In a QGIS project with several layers from a single geopackage database, the following problem frequently occurs:
  Switch layer to editing mode, do geometry edits, save edits, deactivate layer editing mode.
  Switch second layer to editing mode, do geometry edits, try to save edits -> Database provider errors (OGR) e.g. "failed to execute insert: database is locked".
  After closing QGIS and reopening the same project, the second layer can be edited and the edits are successfully saved, but the problem occurs again when another layer from the same geopackage is edited.
  Maybe this problem is related to the one in geopackage edits workflow is broken #23283.
• status_id was changed from Open to Feedback

[qgib]

Author Name: Jochen Huber (@huber-j)

---

I tried with QGIS master (2.99.0, code version af5b2a7) and also on 2.18.14. I didn't experience the problem any more on both versions (not only on master).

[qgib]

Author Name: Giovanni Manghi (@gioman)

---

• status_id was changed from Feedback to Closed
• resolution was changed from to fixed/implemented

[djes]

Have this bug today. Geopackage on a network share, several layers edited. Last edit cannot be saved, "database is locked". Bug occured on 3.4.1 and 3.6.3.