Bug report #15975
GeoPackage: field seems to be editable (but is not) after stopping editing
|Affected QGIS version:||2.18.0||Regression?:||No|
|Operating System:||Easy fix?:||No|
|Pull Request or Patch supplied:||No||Resolution:|
|Crashes QGIS or corrupts data:||No||Copied to github as #:||23891|
Here's how to reproduce the bug:
1. Create a new GeoPackage layer
2. Digitize a few features
3. Open the attribute table and add values in the different fields
4. Stop editing (and save the edits)
One cell remains active and appears to be editable (you can write something else). The original value will appear again when you click somewhere else in the table.
Disable current cell on editing off
because otherwise on single cell change the change would not been stored in mEditBuffer
#4 Updated by David Signer over 2 years ago
It's even worse.
First scenario (working fine):
Edit first field, go to the next and edit it as well and without getting out of the field, toggle to "not-editing". The message appears "Do you want to save changes" -> if yes, the changes are made and the table is read only.
Second scenario (not saving, not read only):
Edit one field and before going out of it, toggle to "not-editing". The message does not appear and nothing is saved. The field is still editable but does not save something. If loosing focus it's read only.
What it should do:
I guess the behavior of the first scenario is correct. This means, if changing a value and not leaving the field but toggle to "not-editing" it should store the values.
Edit: And if another field is changed as well that lost the focus before - message appears and both fields are stored successfully in the end.