#32263: squashmigrations produces incorrect result with a RenameModel on a
ForeignKey target.
-------------------------------------+-------------------------------------
Reporter: InvalidInterrupt | Owner: Anvesh
| Mishra
Type: Bug | Status: assigned
Component: Migrations | Version: 3.1
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 Anvesh Mishra):
Tried running around the files, the first problem that was the creation of
model with `ForeignKey` before the target of `ForeignKey` seems to be
resolved due to some previous patches I guess. For the second problem it
seems that the `RenameModel` misses the functionality where it needs to
change the `to` parameter of the `ForeignKey` model. the
`RenameModel.reduce()` doesn't seems to be getting called here.
--
Ticket URL: <https://code.djangoproject.com/ticket/32263#comment:11>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/01070183b0b9dd4d-e6d1079e-f5a6-4b6f-b833-5b0042f7b1e6-000000%40eu-central-1.amazonses.com.
