#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 Jacob Walls):
Thanks for the ping on github. I agree some investigation is needed about
whether & where to unset `replace_migrations = False` back to True.
Have you looked into pre-walking the graph nodes to find out if any
migrations are missing, so we could reload with `replace_migrations =
False` *before* the loop? I didn't get a chance to do a deeper dive than
that.
--
Ticket URL: <https://code.djangoproject.com/ticket/36168#comment:7>
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/0107019500155261-5e1c633d-026d-4e0a-98dc-c751ba221d01-000000%40eu-central-1.amazonses.com.
