#25255: MigrationExecutor.check_replacements() doesn't take care of unapplied
migrations
--------------------------------------+------------------------
Reporter: MarkusH | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.8
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
--------------------------------------+------------------------
When unapplying a squashed migration an the replaced migration files are
still around, the `MigrationExecutor` schould also mark those as
unapplied.
--
Ticket URL: <https://code.djangoproject.com/ticket/25255>
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/050.210509799f1d0097579483df9888f92b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
