#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: closed
Component: Migrations | Version: 5.1
Severity: Normal | Resolution: needsinfo
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------------------+-------------------------------------
Changes (by Sarah Boyce):
* cc: Jacob Walls (added)
* stage: Unreviewed => Accepted
* summary: migration plan in the context of squashmigrations has too many
leaves =>
Backwards migration to replaced migration when other app has squashed
migrations can lead to FieldDoesNotExist error due to incorrect state
* type: Uncategorized => Bug
Comment:
Agreed this can be treated separate to #36166 assuming we want to support
backwards migrating to replaced migrations
--
Ticket URL: <https://code.djangoproject.com/ticket/36168#comment:5>
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/01070194d07ca952-a974d1b7-675c-4b00-9f63-0ff046c18ffa-000000%40eu-central-1.amazonses.com.
