fix: to avoid uniqueness violation we try deleting and inserting#169
Merged
Conversation
|
the-only-queen-anna
approved these changes
Jun 11, 2026
the-only-queen-anna
left a comment
the-only-queen-anna
left a comment
Collaborator
There was a problem hiding this comment.
Geht alles, danke!
Closed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Context
This PR contains a fix to the DB uniqueness violation problem when creating a second snapshot.
Description
Currently the saving to the DB works once, the second creates a uniqueness violation. A simple fix would be to delete the old entry and reinsert it.
Changes in the code base
Changes outside the code base
N/A
Additional information
N/A