test: handling of duplicate claim events #109
Open
Conversation
This file contains 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
added 6 commits
February 11, 2025 09:30
This reverts commit e1a7484.
This comment was marked as resolved.
This comment was marked as resolved.
juliangruber
requested changes
Feb 14, 2025
bajtos
requested changes
Feb 14, 2025
NikolasHaimerl
changed the title
Co-authored-by: Julian Gruber <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR tests the recently observed bug while trying to insert a duplicate deal.
The hot fix was merged in this PR.
This PR tests this change by inserting two events with a different event id. This event id is not part of the unique constraint of the
active_dealstable and events that only differ in their event id lead to a unique constraint violation.The database should handle this by ignoring the duplicate event.