Add database constraints to enforce unique version numbers #1538
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.
Short description
Ensure version numbers are unique for all content objects in each language.
Proposed changes
UniqueConstraint
s for all content translation modelsResolved issues
My hope is that this is a quick temporary fix for #1518 and #1530 to make sure that at least the database integrity is preserved and an internal server error is thrown instead of creating duplicate translation versions.