diff options
| author | Krzysztof Żuraw <krzysztof.zuraw@gmail.com> | 2016-11-05 17:14:26 +0100 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2016-11-06 12:51:36 +0100 |
| commit | eaa6ea2f37509f2e54de5268f32469deeff89eb9 (patch) | |
| tree | f68a03c51b00fcc161a5dd65953df9a0dc97823f /docs/howto/initial-data.txt | |
| parent | d9b65f639769fca7282119e3b4887c3eec0e549c (diff) | |
Fixed #27133 -- Doc'd how to provide initial data with migrations.
Diffstat (limited to 'docs/howto/initial-data.txt')
| -rw-r--r-- | docs/howto/initial-data.txt | 11 |
1 files changed, 10 insertions, 1 deletions
diff --git a/docs/howto/initial-data.txt b/docs/howto/initial-data.txt index ac5839022d..5945073889 100644 --- a/docs/howto/initial-data.txt +++ b/docs/howto/initial-data.txt @@ -3,7 +3,8 @@ Providing initial data for models ================================= It's sometimes useful to pre-populate your database with hard-coded data when -you're first setting up an app. You can provide initial data via fixtures. +you're first setting up an app. You can provide initial data with fixtures or +migrations. .. _initial-data-via-fixtures: @@ -83,3 +84,11 @@ directories. Fixtures are also used by the :ref:`testing framework <topics-testing-fixtures>` to help set up a consistent test environment. + +Providing initial data with migrations +====================================== + +If you want to automatically load initial data for an app, don't use fixtures. +Instead, create a migration for your application with +:class:`~django.db.migrations.operations.RunPython` or +:class:`~django.db.migrations.operations.RunSQL` operations. |
