#29123: Changing an IntegerField to a ForeignKey generates incorrectly ordered
migration operations if the field is in unique_together
----------------------------+------------------------------------
Reporter: Ed Morley | Owner: Jeff
Type: Bug | Status: assigned
Component: Migrations | Version: master
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 Jeff):
I have tracked down the issue to the migration optimization. Debugging now
to determine how to ensure a field cannot be removed while it is a part of
a `unique_together` constraint.
--
Ticket URL: <https://code.djangoproject.com/ticket/29123#comment:6>
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/066.3847ff34729139d1b50af38c0d131d4f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
