#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:"5c17c273ae2d7274f1fa78218b3b74690efddb86" 5c17c273]:
{{{
#!CommitTicketReference repository=""
revision="5c17c273ae2d7274f1fa78218b3b74690efddb86"
Refs #30172 -- Prevented removing a model Meta's index/unique_together
from removing Meta constraints/indexes.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/30172#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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/063.91084f132c48b336948f0e49b1dbe5af%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
