-
Notifications
You must be signed in to change notification settings - Fork 18
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
DB Editor gives successful message when adding data has failed to to a locked DB #2201
Comments
In a locked db if existing values are updated, the changes are stored in the cache and can be committed when the db is no longer locked. Removing items also works the same way. Adding items to a locked db is denied and will result in an error. If trying to commit changes in the db while it is locked an error telling the commit failed pops up. When the lock is resolved the changes can again be committed. Re spine-tools/Spine-Toolbox#2201
In a locked db if existing values are updated, the changes are stored in the cache and can be committed when the db is no longer locked. Removing items also works the same way. Adding items to a locked db is denied and will result in an error. If trying to commit changes in the db while it is locked an error telling the commit failed pops up. When the lock is resolved the changes can again be committed. Re #2201
When a locked db failed to commit the listener would still be deleted, leading to weird behaviour in the db editor. Re #2201
@DillonJ @jkiviluo @manuelma if any of you have time, could you check out the above linked pull requests to check that I didn't accidentally break some obvious functionality in the db editor that the unit tests or my rudimentary testing don't catch. Just so nothing catastrophic gets into 0.7. Both branches need to be checked out, the one in spine-toolbox and also in spinedb-api. |
I haven't had any issues while using that branch (not extensively). I think it could be merged. |
Reimplement the fix on 0.8-dev branch. Re spine-tools/Spine-Toolbox#2201
Reimplement the fix on 0.8-dev branch. Re #2201
When adding data, such as adding new relationships when the DB is locked, DB Editor reports the operation as successful via a message in the bottom corner, but a traceback in the console indicates the operation has failed and the data is not changed in the DB and can't be comitted.
The text was updated successfully, but these errors were encountered: