#27737: Investigate if reloading old relational fields in migration operations'
state_forwards is needed
-------------------------------------+-------------------------------------
Reporter: Markus Holtermann | Owner: Markus
Type: | Holtermann
Cleanup/optimization | Status: assigned
Component: Migrations | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Description changed by Markus Holtermann:
Old description:
> As a followup to #27666
New description:
As a followup to #27666
The new behavior inside `state_forwards()` of migration operations is to
not reload related models of old relationships in the old state
(https://github.com/django/django/pull/7589/files#diff-
efb7d00c2383393046c9c5d842f45499R202). This might be just fine, but might
cause issues.
--
--
Ticket URL: <https://code.djangoproject.com/ticket/27737#comment:1>
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/065.f028ed7c6cc63701d7c89f2fa7e50ffe%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
