Make unique constraints consistent across databases #2895
Merged
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
raviks789
changed the title
nilmerg
approved these changes
Aug 15, 2024
There was a problem hiding this comment.
Why do they differ to begin with? (7c18c0b)
Because: b9aea20
And: #1187 (comment)
So, what works for MySQL users since 7 years, should now also work for PostgreSQL users.
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.
Unique constraints
import_row_modifier_prioandservice_branch_object_nameare only present in PostgreSQL and not in MySQL. But the constraints needs to be consistent across databases.fixes #2270