#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):
Replying to [comment:13 houston0222]:
> Just a quick update: I'm preparing a small example project that shows
the issue, explains how it was found and debugged, and helps confirm that
the fix works.
>
> The goal is to make the problem and the review process clearer for
anyone looking at the patch.
>
> I’ll follow up with more details once it’s ready. Thank you for your
time.
Hi, all
I’ve written an article explaining how the issue was identified and how
the proposed logic resolves it
https://dev.to/houston_wong_78b96dd3a773/fixing-django-squashed-migration-
in-multi-app-issue-36168-5g39
the new PR: https://github.com/django/django/pull/19623
Thank you!
--
Ticket URL: <https://code.djangoproject.com/ticket/36168#comment:14>
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/01070197e648d4be-1da33068-77cb-4919-a591-c35ed86d5ee5-000000%40eu-central-1.amazonses.com.
