#28862: Removing a field from index_together/unique_together and from the model
generates a migration that crashes
-----------------------------------+------------------------------------
     Reporter:  Artem Maslovskiy   |                    Owner:  Jeff
         Type:  Bug                |                   Status:  closed
    Component:  Migrations         |                  Version:  1.9
     Severity:  Normal             |               Resolution:  fixed
     Keywords:  models migrations  |             Triage Stage:  Accepted
    Has patch:  1                  |      Needs documentation:  0
  Needs tests:  0                  |  Patch needs improvement:  0
Easy pickings:  0                  |                    UI/UX:  0
-----------------------------------+------------------------------------

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

 In [changeset:"1e9b02a4c28142303fb4d33632e77ff7e26acb8b" 1e9b02a]:
 {{{
 #!CommitTicketReference repository=""
 revision="1e9b02a4c28142303fb4d33632e77ff7e26acb8b"
 Refs #28862 -- Removed the FieldRelatedOptionOperation.reduce()
 optimization.

 It isn't required anymore since AlterTogetherOperations can be reduced
 into
 CreateModels which can reduce DeleteField operations.
 }}}

-- 
Ticket URL: <https://code.djangoproject.com/ticket/28862#comment:29>
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 post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.6586d65439b198af7b9596d09ca8f712%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to