Consider options when removing UNIQUE KEYs #47647
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
|
Would you address the conflict? |
fatkodima
force-pushed
the
remove_unique_key-by-options
branch
from
7336580
to
1c469c5
Compare
|
@yahonda Rebased. |
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.
Follow up to #46192.
Currently, it is possible to remove the unique constraint only by name (specified as a String). So added support for removing by columns and checking additional options, if specified. Similar to how foreign keys are implemented, for example.
Also renamed
:column_nameoption to:column, to be consistent with theadd_foreign_key/remove_foreign_keyandremove_index.cc @alpaca-tc @yahonda