From 3bcd42d343db97f57fbeb2984bbf3a3588329f13 Mon Sep 17 00:00:00 2001 From: Mads Jensen Date: Tue, 22 Dec 2015 15:28:18 +0100 Subject: [PATCH] [1.9.x] Fixed #25936 -- Added showmigrations to migrations topic guide. Backport of 394e59099c89eb82cf4a37c78ab5f329b76ce0cc from master --- docs/topics/migrations.txt | 2 ++ 1 file changed, 2 insertions(+) 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