Fixed #23740 -- Fixed removing unique_together constraint if exists primary key/unique constraint on the same field. #15732
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.
Hi,
Tackling ticket-23740.
In short:
1/ If the field is the primary key, fix it by filtering on
"primary_key": False
indjango.db.backends.base.schema.BaseDatabaseSchemaEditor.alter_unique_together
2/ If the field has a
unique=True
constraint, to fix we check that the constraint name is the default one we would give to aunique_together
constraint, based on the observation that aunique=True
and aunique_together
constraints are named differently at the time of writing