#35469: Squashing migrations from unique=True to unique=False to 
UniqueConstraint
produces irreversible migration on Postgres
-----------------------------+---------------------------------------------
     Reporter:  Jacob Walls  |                    Owner:  Jacob Walls
         Type:  Bug          |                   Status:  closed
    Component:  Migrations   |                  Version:  4.2
     Severity:  Normal       |               Resolution:  fixed
     Keywords:               |             Triage Stage:  Ready for checkin
    Has patch:  1            |      Needs documentation:  0
  Needs tests:  0            |  Patch needs improvement:  0
Easy pickings:  0            |                    UI/UX:  0
-----------------------------+---------------------------------------------
Comment (by Sarah Boyce <42296566+sarahboyce@…>):

 In [changeset:"db349fc464ffcc1fbd426277d1ce1d239f1a061f" db349fc4]:
 {{{#!CommitTicketReference repository=""
 revision="db349fc464ffcc1fbd426277d1ce1d239f1a061f"
 [5.1.x] Fixed #35469 -- Removed deferred SQL to create index removed by
 AlterField operation.

 Backport of 99f23eaabd8da653f046dc1d19f5008c030a4f79 from main.
 }}}
-- 
Ticket URL: <https://code.djangoproject.com/ticket/35469#comment:14>
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/0107019016b3011b-34979d7f-4f3b-430e-8f76-8cf5ff1c5667-000000%40eu-central-1.amazonses.com.

Reply via email to