#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:"3dd5e71752c993df00e01fca8086a1af5ba89176" 3dd5e717]:
{{{
#!CommitTicketReference repository=""
revision="3dd5e71752c993df00e01fca8086a1af5ba89176"
[2.2.x] Refs #30172 -- Prevented removing a field's check or unique
constraint from removing Meta constraints.
Backport of 4bb859e24694f6cb8974ed9d2225f18214338ea3 from master.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/30172#comment:9>
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.ff0980e002860792a295578528af19d9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
