#32267: Unable to unapply a branch of migrations
-------------------------------+--------------------------------------
Reporter: Roman Odaisky | Owner: nobody
Type: New feature | Status: closed
Component: Migrations | Version: 3.1
Severity: Normal | Resolution: wontfix
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 Guðlaugur Stefán Egilsson):
I believe that what is missing here is the ability to migrate back to a
point in time based on the migrations table of that particular deployment,
instead of relying exclusively on the migrations graph. Migrations are
always applied in a linear fashion and should be "unappliable" in the
exact reverse order recorded in the migrations table, regardless of merge
migrations.
So something like
{{{
python manage.py 2022-01-17T09:46:51.444
}}}
Should unapply all migrations applied after this timestamp. This would
solve this issue here.
An alternative would be to use the ID of the migration.
{{{
python manage.py 42
}}}
Would unapply migrations with ID greater than 42 in the migrations table
for all apps.
Or am I missing something?
--
Ticket URL: <https://code.djangoproject.com/ticket/32267#comment:9>
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 on the web visit
https://groups.google.com/d/msgid/django-updates/01070185bf28d33d-42e05c2e-2596-4a55-a02b-2c230c598702-000000%40eu-central-1.amazonses.com.
