#24902: Unapply separate migrations when squashed migrations exist
--------------------------------------+------------------------
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 |
--------------------------------------+------------------------
This is basically the inverse of #24628: separate migrations, that have
been applied, and at a later stage the squash has been marked as applied.
When you roll back before the squash the separate migrations won't be
marked as unapplied.
--
Ticket URL: <https://code.djangoproject.com/ticket/24902>
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.caf2e2cac703294a36da5982607736f4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
