#29193: Altering a field with a unique constraint drops and rebuilds FKs to 
fields in the table
     Reporter:  Jeremy Bowman    |                    Owner:  Jeremy Bowman
         Type:  Bug              |                   Status:  closed
    Component:  Migrations       |                  Version:  1.11
     Severity:  Release blocker  |               Resolution:  fixed
     Keywords:                   |             Triage Stage:  Accepted
    Has patch:  1                |      Needs documentation:  0
  Needs tests:  0                |  Patch needs improvement:  1
Easy pickings:  0                |                    UI/UX:  0

Comment (by Tim Graham <timograham@…>):

 In [changeset:"d5018abf1c4e3c68f1a825d05eb9035325707e16" d5018abf]:
 #!CommitTicketReference repository=""
 [2.0.x] Fixed #29193 -- Prevented unnecessary foreign key drops when
 altering a unique field.

 Stopped dropping and recreating foreign key constraints on other fields
 in the same table as the one which is actually being altered in an
 AlterField operation.

 Regression in c3e0adcad8d8ba94b33cabd137056166ed36dae0.

 Backport of ee17bb8a67a9e7e688da6e6f4b3be1b3a69c09b0 from master

Ticket URL: <https://code.djangoproject.com/ticket/29193#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 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 
For more options, visit https://groups.google.com/d/optout.

Reply via email to