Try to drop the unique constraint on tables.table_name again #788
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.
There is an existing script
b4456560d4f3_change_table_unique_constraint.py
that tries to drop the unique constraint ontables
.table_name
. In that script, it assumes the constraint is namedtables_table_name_key
. But on my MySQL, it is not named that way. This PR tries to find the correct constraint name and tries to drop it again