#29224: Migration crashes deleting an index_together if there is a
unique_together
on the same fields
--------------------------------+------------------------------------
Reporter: Matthieu Rigal | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.11
Severity: Normal | Resolution:
Keywords: index | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------+------------------------------------
Comment (by Jeff):
I haven't looked under the hood on this yet, but could it be related to
the ordering of the operations generated for the mgiration? on first
inspection it feels like this and
[https://code.djangoproject.com/ticket/28862 #28862] could be caused by
the same/similar underlying problem in how `FieldRelatedOptionOperation`
subclasses ordering is handled in the migration `autodetector`'s migration
optimizer.
--
Ticket URL: <https://code.djangoproject.com/ticket/29224#comment:2>
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
https://groups.google.com/d/msgid/django-updates/064.64a8d129ee47b9a43ea6df2b76f65949%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
