#36185: manage.py migrate --check --prune actually prunes, which is surprising
----------------------------+--------------------------------------
Reporter: Ari Pollak | Type: Bug
Status: new | Component: Migrations
Version: 5.1 | 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
----------------------------+--------------------------------------
I ran "manage.py migrate --check --prune app" in a Django 5.1.4 app. Based
on the description of --check, I expected this to not delete any
migrations from the database, but just tell me which ones would be
deleted, like a dry run. But it did delete outdated migrations from the
django_migrations table.
To avoid surprising destructive behavior in the future, I think "migrate
--check --prune" should either not be allowed to run with those combined
options, or should just report which migrations would be pruned and not
actually prune them.
--
Ticket URL: <https://code.djangoproject.com/ticket/36185>
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 visit
https://groups.google.com/d/msgid/django-updates/01070194fa9f8d5a-7788c4cc-1cf4-4f4d-bc53-b761cebbd6b4-000000%40eu-central-1.amazonses.com.
