#29198: Add a --plan option to the migrate command
-------------------------------------+-------------------------------------
Reporter: Craig de Stigter | Owner: Calvin
| DeBoer
Type: New feature | Status: assigned
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 Calvin DeBoer):
Added a WIP Pull Request that outlines the basic functionality. Main todo
is completing the rest of the testing framework / adjusting code based on
comments from django core maintainers.
Running a {{{./manage.py migrate --plan}}} will yield a look at all the
migrations to be run (in order), which all the operations (in order),
which inclusion on what that migration will do (if it is adequately
defined).
{{{
Planned operations:
migrations.0001_initial
Undo Create model Salamander --> No further Detail
Raw Python operation --> Moves salamander to pond
migrations.0002_second
Undo Create model Book --> No further Detail
Raw SQL operation --> SELECT * FROM migrations_book
migrations.0003_third
Undo Create model Author --> No further Detail
Raw SQL operation --> SELECT * FROM migrations_author
}}}
Thoughts ?
--
Ticket URL: <https://code.djangoproject.com/ticket/29198#comment:6>
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.76dbaa1ef7af53c487ce149b7e54f42a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.