#30597: Improve documentation on reseting an app's migrations to zero.
-------------------------------------+-------------------------------------
Reporter: Keryn Knight | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Documentation | 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
-------------------------------------+-------------------------------------
Changes (by felixxm):
* type: New feature => Cleanup/optimization
Comment:
Thanks for the report. I'm not sure how we could clarify what
`"unapplying" migrations` means, it seems clear to me. Moreover my
understanding is that it's not a common use case to unapply all migrations
to "zero" state, so I don't think that it deserves a separate section in
[https://docs.djangoproject.com/en/2.2/topics/migrations/ "migrations
topics"].
[https://docs.djangoproject.com/en/2.2/topics/migrations/ "migrations
topics"] contains information that `migrate` is responsible for unapplying
migrations and also a link to the
[https://docs.djangoproject.com/en/2.2/ref/django-admin/#migrate "migrate
doc"] with `zero` option (added 6 years ago, see
162f7b938f6cff91b1e4d6086ddcc88cbb1a1cd6).
--
Ticket URL: <https://code.djangoproject.com/ticket/30597#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 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/067.7b56d657fa18fbf4e623b45eb2b787de%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
