#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
------------------------------+-----------------------------------------
Changes (by Tim Graham):
* stage: Unreviewed => Accepted
Comment:
I think the problem is in `ForeignKey.db_type()`. It uses
`self.target_field` which is using the state of the current model files
rather than migration's state.
--
Ticket URL: <https://code.djangoproject.com/ticket/28056#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 [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/069.b8b0dad36267f5621aaa63e335f51b55%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
