Opened 9 years ago
Closed 3 weeks ago
#27737 closed Cleanup/optimization (wontfix)
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: | Suzannah Cooper | 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 (5)
comment:1 by , 9 years ago
| Description: | modified (diff) |
|---|
comment:2 by , 9 years ago
| Triage Stage: | Unreviewed → Accepted |
|---|
comment:3 by , 4 years ago
| Owner: | removed |
|---|---|
| Status: | assigned → new |
comment:4 by , 4 weeks ago
| Cc: | added |
|---|
comment:5 by , 3 weeks ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
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 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_fieldstate operation, the previouslynew_statebecomes anold_statefor the next operation. Which means, the formerold_stateis unused. Thus no reloading is needed.