#28056: Reverse migration for model rename with cross-app ForeignKey fails
------------------------------+-----------------------------------------
Reporter: Paul Tiplady | Owner: Gaurav Sehgal
Type: Bug | Status: assigned
Component: Migrations | Version: 1.10
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 Gaurav Sehgal):
Can't we have a different migration for rename1 as alterfield, so that its
migration's state handled properly.
--
Ticket URL: <https://code.djangoproject.com/ticket/28056#comment:3>
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/069.1e771313800dc3b085b768a83f62844a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
