#36168: Backwards migration to replaced migration when other app has squashed
migrations can lead to FieldDoesNotExist error due to incorrect state
------------------------------------+------------------------------------
Reporter: Klaas van Schelven | Owner: (none)
Type: Bug | Status: new
Component: Migrations | Version: 5.1
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------------------+------------------------------------
Comment (by Klaas van Schelven):
I'm not sure what you mean exactly... in particular with "pre walking".
Also I'm not sure what you mean with "the loop"; the whole point is that
there are 2 usage locations (and that in certain conditions they need
different values for replace_migrations).
I think the graph is cached (and this caching is overridden for the case I
highlighted). In my mind, as long as that "clobbering" is done after the
function that needs it returns, we're probably good. In my PoC I did that
by storing the unclobbered result, but any other solution would do to, I
think.
--
Ticket URL: <https://code.djangoproject.com/ticket/36168#comment:8>
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/0107019503857ad1-69d75ac2-eadc-4675-a34b-09f4992e8843-000000%40eu-central-1.amazonses.com.
