[2.2.x] Doc'd that migrate commmand accepts a unique migration name prefix.
Backport of e02f67ef2d
from master
This commit is contained in:
parent
4116b369b1
commit
43c894ffe7
|
@ -801,8 +801,10 @@ The behavior of this command changes depending on the arguments provided:
|
||||||
* ``<app_label> <migrationname>``: Brings the database schema to a state where
|
* ``<app_label> <migrationname>``: Brings the database schema to a state where
|
||||||
the named migration is applied, but no later migrations in the same app are
|
the named migration is applied, but no later migrations in the same app are
|
||||||
applied. This may involve unapplying migrations if you have previously
|
applied. This may involve unapplying migrations if you have previously
|
||||||
migrated past the named migration. Use the name ``zero`` to migrate all the
|
migrated past the named migration. You can use a prefix of the migration
|
||||||
way back i.e. to revert all applied migrations for an app.
|
name, e.g. ``0001``, as long as it's unique for the given app name. Use the
|
||||||
|
name ``zero`` to migrate all the way back i.e. to revert all applied
|
||||||
|
migrations for an app.
|
||||||
|
|
||||||
.. warning::
|
.. warning::
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue