summaryrefslogtreecommitdiff
path: root/docs/topics
diff options
context:
space:
mode:
authorMads Jensen <mje@inducks.org>2015-12-22 15:28:18 +0100
committerTim Graham <timograham@gmail.com>2015-12-22 13:17:27 -0500
commit3bcd42d343db97f57fbeb2984bbf3a3588329f13 (patch)
treeaa66e0c37064c0926ca0a4731a113742e8afd339 /docs/topics
parent36d0aa43036090685cebe6c9f757631cdadb1400 (diff)
[1.9.x] Fixed #25936 -- Added showmigrations to migrations topic guide.
Backport of 394e59099c89eb82cf4a37c78ab5f329b76ce0cc from master
Diffstat (limited to 'docs/topics')
-rw-r--r--docs/topics/migrations.txt2
1 files changed, 2 insertions, 0 deletions
diff --git a/docs/topics/migrations.txt b/docs/topics/migrations.txt
index 24236ec9da..a202676aea 100644
--- a/docs/topics/migrations.txt
+++ b/docs/topics/migrations.txt
@@ -24,6 +24,8 @@ and Django's handling of database schema:
* :djadmin:`sqlmigrate`, which displays the SQL statements for a migration.
+* :djadmin:`showmigrations`, which lists a project's migrations.
+
You should think of migrations as a version control system for your database
schema. ``makemigrations`` is responsible for packaging up your model changes
into individual migration files - analogous to commits - and ``migrate`` is