#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: invalid
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 Roman Odaisky):
Replying to [comment:1 Mariusz Felisiak]:
> Working with migrations on feature branches is difficult and each
situation is different, I don't see a way to add an option to the
`migrate` command that can decide for you. Personally I would recommend
using a separate db for each feature that can be abandoned if not needed.
Can we at the very least add something like `manage.py migrate --unapply-
one <app> <migration>` that would unapply one migration, having ensured
that no currently applied migrations depend on it? This will solve the use
case I outlined and maybe some others while not being able to corrupt the
DB state.
--
Ticket URL: <https://code.djangoproject.com/ticket/32267#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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.bda3d3fa93a3207737b87e422e53368b%40djangoproject.com.
