Fix 5288 adds PostgreSql drop constraint #5289
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
griffio
force-pushed
the
fix-5288-postgresql-drop-constraint
branch
from
8f115eb
to
004db6a
Compare
ensure that DROP CONSTRAINT is higher than DROP COLUMN as would match first
consider constraint doesn't exist in table schema
griffio
force-pushed
the
fix-5288-postgresql-drop-constraint
branch
from
004db6a
to
3e3bc62
Compare
JakeWharton
approved these changes
Jul 9, 2024
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.
fixes #5288
DROP CONSTRAINT [ IF EXISTS ] constraint_name [ RESTRICT | CASCADE ]DROP COLUMNconflictsNote: Currently there is no way, at compile time, to verify that a named check constraints exist