#23740: Cannot drop unique_together constraint on a single field with its own
unique=True constraint
---------------------------------+------------------------------------
Reporter: Mihail Milushev | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.7
Severity: Normal | Resolution:
Keywords: unique_together | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+------------------------------------
Comment (by Claude Paroz):
As a workaround, it may be possible to migrate the unique_together to a
UniqueConstraint, keeping the same index name, and then dropping the
UniqueConstraint. Just an idea, untested.
--
Ticket URL: <https://code.djangoproject.com/ticket/23740#comment:8>
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/01070180765d0b22-d24981a9-3b24-4f57-b78e-e325095b0f83-000000%40eu-central-1.amazonses.com.
