#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
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak <felisiak.mariusz@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"b949e40e8c32a393f480399e2d70b653108098b6" b949e40e]:
{{{
#!CommitTicketReference repository=""
revision="b949e40e8c32a393f480399e2d70b653108098b6"
Fixed #23740 -- Fixed removing unique_together constraint if exists
primary key/unique constraint on the same field.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/23740#comment:14>
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/01070180ff309ecf-966a2a04-a863-400c-a89f-d4113035fb7e-000000%40eu-central-1.amazonses.com.
