#29000: RenameModel does not rename M2M column when run after RenameField
-------------------------------------+-------------------------------------
     Reporter:  David Nelson Adamec  |                    Owner:  Jeff
         Type:  Bug                  |                   Status:  closed
    Component:  Migrations           |                  Version:  2.0
     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 Mariusz Felisiak <felisiak.mariusz@…>):

 In [changeset:"ad811335bdd57d65dddbc05375ec3a70b59c96fb" ad81133]:
 {{{
 #!CommitTicketReference repository=""
 revision="ad811335bdd57d65dddbc05375ec3a70b59c96fb"
 Refs #29000 -- Restored delayed model rendering of RenameField.

 Non-delayed rendering is unnecessary and wasteful now that state models
 relationship consistency on delayed reload is ensured.

 This partly reverts commit fcc4e251dbc917118f73d7187ee2f4cbf3883f36.
 }}}

-- 
Ticket URL: <https://code.djangoproject.com/ticket/29000#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/065.16ef01d2b6477994396e13a6f56edecc%40djangoproject.com.

Reply via email to