From 8c20f4af12d1f0f4798467dfac33858d05bfc182 Mon Sep 17 00:00:00 2001 From: Greg Chapple Date: Wed, 11 Jun 2014 19:46:57 +0100 Subject: [PATCH] [1.7.x] Added link to data migrations in initial data deprecation note Backport of 4123f55c33 from master --- docs/howto/initial-data.txt | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/howto/initial-data.txt b/docs/howto/initial-data.txt index 4e8d3aef6a..b22cf73d34 100644 --- a/docs/howto/initial-data.txt +++ b/docs/howto/initial-data.txt @@ -82,7 +82,7 @@ Automatically loading initial data fixtures If an application uses migrations, there is no automatic loading of fixtures. Since migrations will be required for applications in Django 2.0, this behavior is considered deprecated. If you want to load initial data - for an app, consider doing it in a migration. + for an app, consider doing it in a :ref:`data migration `. If you create a fixture named ``initial_data.[xml/yaml/json]``, that fixture will be loaded every time you run :djadmin:`migrate`. This is extremely convenient, @@ -115,7 +115,8 @@ Providing initial SQL data If an application uses migrations, there is no loading of initial SQL data (including backend-specific SQL data). Since migrations will be required for applications in Django 2.0, this behavior is considered deprecated. - If you want to use initial SQL for an app, consider doing it in a migration. + If you want to use initial SQL for an app, consider doing it in a + :ref:`data migration `. Django provides a hook for passing the database arbitrary SQL that's executed just after the CREATE TABLE statements when you run :djadmin:`migrate`. You can