#24543: Add checks / command options for "migrations not applied" and
"migrations
needed"
-----------------------------+--------------------------------------
Reporter: blueyed | Owner:
Type: New feature | Status: new
Component: Migrations | Version: master
Severity: Normal | Resolution:
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 timgraham):
I'm still not perfectly clear on the use case. `migrate` does list the
migrations as it runs so it seems it would be possible to roll back
manually using that list. I'm not sure if an automated way to rollback is
feasible or a good idea. Since migrations can often be destructive/non-
reversible, I'd tend to prefer recommending to restore the database from a
backup if needed rather than trying to engineer some attempt at a rollback
mechanism in Django. That said, if there's an easy, simple solution I'm
overlooking, maybe it's a good idea.
--
Ticket URL: <https://code.djangoproject.com/ticket/24543#comment:5>
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.aba14d81d69220c0203a94fbb6d0ab67%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
