Fixed #9572 -- Corrected some documentation that misleadingly gave the extension for YAML fixtures as YML. Thanks to django@i-sh.me.uk for the report.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@9401 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
parent
95d8c0619a
commit
e32299e0bc
|
@ -77,7 +77,7 @@ out any changes you've made.
|
||||||
Automatically loading initial data fixtures
|
Automatically loading initial data fixtures
|
||||||
-------------------------------------------
|
-------------------------------------------
|
||||||
|
|
||||||
If you create a fixture named ``initial_data.[xml/yml/json]``, that fixture will
|
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:`syncdb`. This is extremely convenient,
|
||||||
but be careful: remember that the data will be refreshed *every time* you run
|
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:`syncdb`. So don't use ``initial_data`` for data you'll want to edit.
|
||||||
|
|
Loading…
Reference in New Issue