#29198: Add a --plan option to the migrate command
----------------------------------+------------------------------------
Reporter: Craig de Stigter | Owner: nobody
Type: New feature | Status: new
Component: Migrations | Version: 2.0
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
----------------------------------+------------------------------------
Changes (by Carlton Gibson):
* type: Uncategorized => New feature
* stage: Unreviewed => Accepted
Comment:
This seems as if it should be viable, at least at the individual migration
level. The `migrate` command calls `MigrationExecutor.migration_plan()`,
making the plan available prior to running any operations. We could
intercept execution there and format the plan for display.
We could expect to list app_name and migration (in order). Users would
need to look at the migrations for the exact operations but, if I'm
reading the intent here correctly, that would probably be enough.
--
Ticket URL: <https://code.djangoproject.com/ticket/29198#comment:1>
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.71c2157f75577dd89e1e5a217ec0316b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
