Adding entities to DB sometimes requires committing twice #2296
Comments
PiispaH
added a commit
to spine-tools/Spine-Database-API
that referenced
this issue
Sep 6, 2023
The need for double committing arose from the fact that if an entity or entity class was re-added after it had already been deleted from the db, some of its data was still present in the db. That caused some unique constraint errors. - Previously when an entity was deleted, only the entity table was considered. Now the data corresponding to the entity is also deleted from the entity_element -table. - When deleting an entity class, the data form the entity_class_dimension -table corresponding to the classes id is also deleted. Re spine-tools/Spine-Toolbox#2296
|
Should be fixed |
|
Nice one @PiispaH ! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If a parameter value like in the picture below is added to the db and then committing is tried, the committing will result in an error like in the image. If then the error popup is closed and committing is tried again, the commit goes through smoothly. This doesn't seem to happen on parameter values of one dimensional entities.
The text was updated successfully, but these errors were encountered: