#35469: Squashing migrations from unique=True to unique=False to
UniqueConstraint
produces irreversible migration on Postgres
-----------------------------+------------------------------------
Reporter: Jacob Walls | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 4.2
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------+------------------------------------
Comment (by Jacob Walls):
Sorry, still forming first impressions here, but just piping up to clarify
that my last comment mostly barks up the wrong tree: the field values for
`db_index` and whatnot look fine. And on a closer read of #28646, it
strikes me as mostly focused on SlugField, which *doesn't* have the
problem presented here. So I think having separate tickets makes sense.
--
Ticket URL: <https://code.djangoproject.com/ticket/35469#comment:5>
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/0107018fa0933187-8d92ae29-ab14-45fa-9a24-19e3b45ff0d2-000000%40eu-central-1.amazonses.com.
