diff options
| author | Tim Graham <timograham@gmail.com> | 2014-08-18 09:15:24 -0400 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2014-08-18 09:16:18 -0400 |
| commit | ad2faaa4918ff1cfce2671a91d0e016515319481 (patch) | |
| tree | 1820953aca91cd075e28cb4d5cd5af334f492fa2 | |
| parent | ee7289656c4aa18df91b3b18fff31cd010109de7 (diff) | |
[1.7.x] Fixed #23263 -- Added sqlmigrate to migration topic guide.
Backport of 7ed3d0bb61 from master
| -rw-r--r-- | docs/topics/migrations.txt | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/docs/topics/migrations.txt b/docs/topics/migrations.txt index 8b6d19764f..ec462ea0fa 100644 --- a/docs/topics/migrations.txt +++ b/docs/topics/migrations.txt @@ -26,7 +26,7 @@ important enough that support was brought into core Django. Two Commands ------------ -There are two commands which you will use to interact with migrations +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 @@ -35,6 +35,8 @@ and Django's handling of database schema: * :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. + It's worth noting that migrations are created and run on a per-app basis. In particular, it's possible to have apps that *do not use migrations* (these are referred to as "unmigrated" apps) - these apps will instead mimic the |