#24895: Migration loader fails to load pair of squashed apps when dependent
app's
squashed migrations are partially applied
----------------------------+--------------------------------------
Reporter: carljm | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.8
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------+--------------------------------------
Comment (by carljm):
Pull request: https://github.com/django/django/pull/4732
Rather than trying to detect whether the replacement in question will
actually occur (which duplicates logic that will occur when that
replacement is itself processed), we just update the dependencies of every
migration that depends on this one, replacing or replaced. This means we
may update the dependencies of a migration that won't in the end be used,
but there's no harm in that; better to keep more state accurate than less.
--
Ticket URL: <https://code.djangoproject.com/ticket/24895#comment:1>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.ecb325516db1c6a4ec3d5f9863baa031%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
