summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorKrzysztof Gogolewski <krz.gogolewski@gmail.com>2016-11-05 21:56:13 +0100
committerSimon Charette <charettes@users.noreply.github.com>2016-11-05 21:56:13 +0100
commitd1dbaeaadb659e61c8f351457c25cac1604675bb (patch)
tree022cd98f1af057a9b43f3a353ae00c6c048da2ab /docs
parent802dd1ffc5cfa3d547efeb285dac70884b99e16d (diff)
Adjusted documentation of migration related commands.
Diffstat (limited to 'docs')
-rw-r--r--docs/topics/migrations.txt7
1 files changed, 4 insertions, 3 deletions
diff --git a/docs/topics/migrations.txt b/docs/topics/migrations.txt
index 41d8727f21..b193333d47 100644
--- a/docs/topics/migrations.txt
+++ b/docs/topics/migrations.txt
@@ -16,15 +16,16 @@ The Commands
There are several commands which you will use to interact with migrations
and Django's handling of database schema:
-* :djadmin:`migrate`, which is responsible for applying migrations, as well as
- unapplying and listing their status.
+* :djadmin:`migrate`, which is responsible for applying and unapplying
+ migrations.
* :djadmin:`makemigrations`, which is responsible for creating new migrations
based on the changes you have made to your models.
* :djadmin:`sqlmigrate`, which displays the SQL statements for a migration.
-* :djadmin:`showmigrations`, which lists a project's migrations.
+* :djadmin:`showmigrations`, which lists a project's migrations and their
+ status.
You should think of migrations as a version control system for your database
schema. ``makemigrations`` is responsible for packaging up your model changes