#31263: remote_field model caching issues in RenameModel migration
-------------------------------------+-------------------------------------
Reporter: Sean Esterkin | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 2.2
Severity: Normal | Resolution:
Keywords: migration, caching, | Triage Stage:
remote_field, RenameModel | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Simon Charette):
That's likely an issue with `RenameModel.state_forwards`
https://github.com/django/django/blob/1712a76b9dfda1ef220395e62ea87079da8c9f6c/django/db/migrations/operations/models.py#L304-L343
Could you set `delay=False` in the `reload_models` calls and see if it
helps
https://github.com/django/django/blob/1712a76b9dfda1ef220395e62ea87079da8c9f6c/django/db/migrations/operations/models.py#L339-L343
That should trigger an immediate re-rerender of all `to_reload` models
instead of ''deferring'' on demand which seems to be the issue here.
In order to address this issue we'll need a way to reproduce it so if you
could reduce your large project to a simplified set of apps/migrations
that would be greatly appreciated.
--
Ticket URL: <https://code.djangoproject.com/ticket/31263#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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.53785b74904067586a405a37432286bb%40djangoproject.com.
