#30172: Incorrect migration applying for new Meta.constraints/indexes and field
check/unique or unique/index_together constraints with same fields for
postgres
-------------------------------------+-------------------------------------
Reporter: Pavel Tyslacki | Owner: Pavel
| Tyslacki
Type: Bug | Status: assigned
Component: Migrations | Version: 2.2
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Tim Graham <timograham@…>):
In [changeset:"2a92e2e3c12e5c4cad0ce2a2d5964675ef837fe7" 2a92e2e]:
{{{
#!CommitTicketReference repository=""
revision="2a92e2e3c12e5c4cad0ce2a2d5964675ef837fe7"
[2.2.x] Refs #30172 -- Prevented removing a model Meta's
index/unique_together from removing Meta constraints/indexes.
Backport of 5c17c273ae2d7274f1fa78218b3b74690efddb86 from master.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/30172#comment:10>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/063.294cfa3ad96c53636a686b66c9e2dba4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
