Opened 7 years ago
Last modified 2 years ago
#27737 new Cleanup/optimization
Investigate if reloading old relational fields in migration operations' state_forwards is needed
| Reported by: | Markus Holtermann | Owned by: | |
|---|---|---|---|
| Component: | Migrations | Version: | dev |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Accepted | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description (last modified by )
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.
Change History (3)
comment:1 by , 7 years ago
| Description: | modified (diff) |
|---|
comment:2 by , 7 years ago
| Triage Stage: | Unreviewed → Accepted |
|---|
comment:3 by , 2 years ago
| Owner: | removed |
|---|---|
| Status: | assigned → new |
Note:
See TracTickets
for help on using tickets.