innov
/
django1
1
0
Fork 0
Code Issues Pull Requests 1 Projects Releases Wiki Activity

Fixed #23263 -- Added sqlmigrate to migration topic guide.

This commit is contained in:
Tim Graham 2014-08-18 09:15:24 -04:00
parent dfde0b3b06
commit 7ed3d0bb61
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/topics/migrations.txt
View File

@ -26,7 +26,7 @@ important enough that support was brought into core Django.
Two Commands 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: and Django's handling of database schema:
* :djadmin:`migrate`, which is responsible for applying migrations, as well as * :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 * :djadmin:`makemigrations`, which is responsible for creating new migrations
based on the changes you have made to your models. 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. 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 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 are referred to as "unmigrated" apps) - these apps will instead mimic the