#28784: Clarify migrate --fake documentation
-------------------------------------+-------------------------------------
Reporter: Ramez Kabbani | Owner: gagan
Type: | trivedi
Cleanup/optimization | Status: assigned
Component: Documentation | Version: 1.11
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Israel Saeta Pérez):
Replying to [comment:2 tothegump]:
> What about:
> `Tells Django to mark the migrations before and including this
<migrationname> as having been applied, meanwhile mark the migrations
after this <migrationname> as having been unapplied?`
>
> But it is not concise.
What about:
`Tells Django to mark the migrations up to the target one (following the
rules described above) as applied, but without actually running the SQL to
change your database schema.`
IMO the source of confusion could be the `or unnaplied` in the
description. But after having read the behavior rules above for the second
argument and the meaning of the word `fake` itself I believe it is pretty
clear.
--
Ticket URL: <https://code.djangoproject.com/ticket/28784#comment:4>
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/070.2a6c924140b066054c7a0035f273d6ca%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
