#28784: Clarify migrate --fake documentation
------------------------------------------------+------------------------
Reporter: Ramez Kabbani | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Documentation | Version: 1.11
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 1
UI/UX: 0 |
------------------------------------------------+------------------------
[https://docs.djangoproject.com/en/1.11/ref/django-admin/#cmdoption-
migrate-fake migrate documentation] implies that running migrate --fake on
a specific migration toggles its applied status (applied => unapplied and
vice versa). The reality is that one needs to run migrate --fake on the
preceding migration to mark the migration as unapplied.
--
Ticket URL: <https://code.djangoproject.com/ticket/28784>
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/055.ef92c5dc9d2df3bbbdbf46a9b8192429%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
