#35469: Squashing migrations from unique=True to unique=False to
UniqueConstraint
produces irreversible migration
-----------------------------+--------------------------------------
Reporter: Jacob Walls | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 4.2
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------+--------------------------------------
Comment (by Sarah Boyce):
Hi Jacob, thank you for this. I tried to replicate on main with SQLite and
couldn't, so this might be postgres specific (I will try out again later).
I was wondering if you have seen #28646 and whether you think this is
related or this issue would be resolved with that ticket?
--
Ticket URL: <https://code.djangoproject.com/ticket/35469#comment:2>
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/0107018f9f7cafd2-8310c1fa-e315-4843-b2b8-00e3a7182ba8-000000%40eu-central-1.amazonses.com.
