Implement Unique Constraint for Transaction Evidence Identifier #382
Conversation
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
1 participant
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.
Implement Unique Constraint for Transaction Evidence Identifier
Original Task
Design Transaction Evidence Uniqueness Schema
Summary of Changes
Added database migration to enforce uniqueness of transaction evidence identifiers to prevent duplicate entries
Acceptance Criteria
Create a new database migration file for the uniqueness tracking schema
Add a unique constraint on evidence identifier column
Verify that attempting to insert a duplicate evidence record raises a database-level constraint violation
100% branch coverage for database schema changes
Performance overhead of uniqueness check is less than 10ms
Tests