#29198: Add a --plan option to the migrate command
----------------------------------+------------------------------------
Reporter: Craig de Stigter | Owner: nobody
Type: New feature | Status: new
Component: Migrations | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------+------------------------------------
Comment (by Sam Handler):
I'm very interested in some version of this functionality as well, though
my case may be different enough to warrant another ticket. I'd like to see
top-level feedback along the lines suggested by Craig in the specific
"and" general migration case (./manage.py migrate and ./manage.py migrate
account 0001_initial). I'd also like to be able to run `sqlmigrate`
against all pending migrations so that I can easily know the queries that
will be run against the DB. I'm not too knowledgeable about Django's
migration internals (yet!) but am glad to take a first stab at this
functionality!
--
Ticket URL: <https://code.djangoproject.com/ticket/29198#comment:3>
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.7788a4546f03749da694fb2444f0716d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
