#23740: Cannot drop unique_together constraint on a single field with its own
unique=True constraint
-------------------------------------+-------------------------------------
Reporter: Mihail Milushev | Owner: David
| Wobrock
Type: Bug | Status: closed
Component: Migrations | Version: 1.7
Severity: Normal | Resolution: fixed
Keywords: unique_together | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak <felisiak.mariusz@…>):
In [changeset:"176d5ec2422bf7513ef5d58953c6c74377c4170f" 176d5ec2]:
{{{
#!CommitTicketReference repository=""
revision="176d5ec2422bf7513ef5d58953c6c74377c4170f"
[4.1.x] Refs #23740 -- Added
BaseDatabaseSchemaEditor._unique_constraint_name().
Backport of 115a978fceac4c4de2f9fc70ce19001c3f6d6918 from main
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/23740#comment:15>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/01070180ff317056-dc22b0b9-b8fb-49c4-9f5e-d2ede74e6f96-000000%40eu-central-1.amazonses.com.
