From eaa6ea2f37509f2e54de5268f32469deeff89eb9 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Krzysztof=20=C5=BBuraw?= Date: Sat, 5 Nov 2016 17:14:26 +0100 Subject: [PATCH] Fixed #27133 -- Doc'd how to provide initial data with migrations. --- docs/howto/initial-data.txt | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) 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 ` 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.