#25255: Squashed migration is not marked as unapplied
----------------------------+------------------------------------
Reporter: MarkusH | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.8
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------+------------------------------------
Old description:
> When unapplying a squashed migration an the replaced migration files are
> still around, the `MigrationExecutor` schould also mark those as
> unapplied.
New description:
When unapplying a squashed migration and the replaced migration files are
still around, the `MigrationExecutor` mark the squash migration as
unapplied, too, not only the replaced migrations.
--
Comment (by MarkusH):
While working on #24800 I realized that the issue is actually not fully
correct. The squashed migration i not marked as applied
--
Ticket URL: <https://code.djangoproject.com/ticket/25255#comment:2>
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/065.6d1f52d4abd560bb7587e642bfa8805a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
