#23577: CREATE INDEX-related OperationalError on migrating renamed models with
colliding field names
----------------------------+------------------------------------
     Reporter:  CrimsonZen  |                    Owner:
         Type:  Bug         |                   Status:  new
    Component:  Migrations  |                  Version:  1.7
     Severity:  Normal      |               Resolution:
     Keywords:              |             Triage Stage:  Accepted
    Has patch:  0           |      Needs documentation:  0
  Needs tests:  0           |  Patch needs improvement:  0
Easy pickings:  0           |                    UI/UX:  0
----------------------------+------------------------------------

Comment (by skyjur):

 This also happens when renaming a ManyToManyField and then adding a new
 ManyToManyField with the same name. I've opened a ticket then @timgraham
 pointed out that it's duplicate of this one
 https://code.djangoproject.com/ticket/25752

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

Reply via email to