#27737: Investigate if reloading old relational fields in migration operations'
state_forwards is needed
--------------------------------------+------------------------------------
Reporter: Markus Holtermann | Owner: (none)
Type: Cleanup/optimization | Status: closed
Component: Migrations | Version: dev
Severity: Normal | Resolution: wontfix
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 Markus Holtermann):
* resolution: => wontfix
* status: new => closed
Comment:
After 9 years, I'm not entirely sure anymore, what I had in mind when I
opened this issue 9 years ago. The only reference to this ticket is in the
[https://github.com/django/django/blob/6f030e8e5d13ee94bf45d4322c17ca7c2d8aaffb/django/db/migrations/state.py#L298-L299
alter_field] method of the `ProjectState`.
Practically, the lack of reloading old models hasn't caused any problems
that could be attributed to this code here.
Logically, after the `alter_field` state operation, the previously
`new_state` becomes an `old_state` for the next operation. Which means,
the former `old_state` is unused. Thus no reloading is needed.
--
Ticket URL: <https://code.djangoproject.com/ticket/27737#comment:5>
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 visit
https://groups.google.com/d/msgid/django-updates/0107019d77685846-14b95da6-17ea-45f7-ae91-5d87cd46f34f-000000%40eu-central-1.amazonses.com.
