diff options
| author | Loic Bistuer <loic.bistuer@sixmedia.com> | 2013-11-21 21:04:31 +0700 |
|---|---|---|
| committer | Baptiste Mispelon <bmispelon@gmail.com> | 2013-11-21 15:12:39 +0100 |
| commit | 27f04e79b1a639b2f6360e9159f003a3db60f567 (patch) | |
| tree | a635be089d0c81a2250d414e212a05ce639995a4 /docs/faq | |
| parent | b6a6cf4ab791b092e18ab16537aa88dd7ae9bc36 (diff) | |
Fixed #21479 -- Favor 'migrate' over 'syncdb' in the docs.
Diffstat (limited to 'docs/faq')
| -rw-r--r-- | docs/faq/models.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/faq/models.txt b/docs/faq/models.txt index 97732131f0..eb2bb621dd 100644 --- a/docs/faq/models.txt +++ b/docs/faq/models.txt @@ -45,7 +45,7 @@ Take a look at Django's support for :mod:`schema migrations If you don't mind clearing data, your project's ``manage.py`` utility has a :djadmin:`flush` option to reset the database to the state it was in -immediately after :djadmin:`syncdb` was executed. +immediately after :djadmin:`migrate` was executed. Do Django models support multiple-column primary keys? ------------------------------------------------------ |