#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:
| houston0222
Type: Bug | Status: assigned
Component: Migrations | Version: 5.1
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by houston0222):
Hi everyone,
I've submitted a pull request to address this issue:
https://github.com/django/django/pull/19612
It adds a conditional check to avoid reapplying replaced migrations when
migrating backwards, which can lead to duplicate operations.
Feedback welcome:)
--
Ticket URL: <https://code.djangoproject.com/ticket/36168#comment:12>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/01070197c2a613d1-f2e4fe7a-b25a-4c55-97c0-cec9cc640377-000000%40eu-central-1.amazonses.com.
