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/howto/initial-data.txt | |
| parent | b6a6cf4ab791b092e18ab16537aa88dd7ae9bc36 (diff) | |
| download | django-27f04e79b1a639b2f6360e9159f003a3db60f567.tar.gz | |
Fixed #21479 -- Favor 'migrate' over 'syncdb' in the docs.
Diffstat (limited to 'docs/howto/initial-data.txt')
| -rw-r--r-- | docs/howto/initial-data.txt | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/howto/initial-data.txt b/docs/howto/initial-data.txt index 70d1ae18a6..61885a0803 100644 --- a/docs/howto/initial-data.txt +++ b/docs/howto/initial-data.txt @@ -78,9 +78,9 @@ Automatically loading initial data fixtures ------------------------------------------- If you create a fixture named ``initial_data.[xml/yaml/json]``, that fixture will -be loaded every time you run :djadmin:`syncdb`. This is extremely convenient, +be loaded every time you run :djadmin:`migrate`. This is extremely convenient, but be careful: remember that the data will be refreshed *every time* you run -:djadmin:`syncdb`. So don't use ``initial_data`` for data you'll want to edit. +:djadmin:`migrate`. So don't use ``initial_data`` for data you'll want to edit. Where Django finds fixture files -------------------------------- @@ -104,7 +104,7 @@ Providing initial SQL data ========================== Django provides a hook for passing the database arbitrary SQL that's executed -just after the CREATE TABLE statements when you run :djadmin:`syncdb`. You can +just after the CREATE TABLE statements when you run :djadmin:`migrate`. You can use this hook to populate default records, or you could also create SQL functions, views, triggers, etc. |