From a2e3c9694823d6d451d6dd234e9d416600aacc68 Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Wed, 7 May 2014 09:01:37 -0400 Subject: Updated some docs for the delayed deprecation of legacy table creation; refs #22340. --- docs/howto/initial-data.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'docs/howto/initial-data.txt') diff --git a/docs/howto/initial-data.txt b/docs/howto/initial-data.txt index d55cd38609..4e8d3aef6a 100644 --- a/docs/howto/initial-data.txt +++ b/docs/howto/initial-data.txt @@ -80,7 +80,7 @@ Automatically loading initial data fixtures .. deprecated:: 1.7 If an application uses migrations, there is no automatic loading of - fixtures. Since migrations will be required for applications in Django 1.9, + 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. @@ -114,7 +114,7 @@ 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 1.9, this behavior is considered deprecated. + 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. Django provides a hook for passing the database arbitrary SQL that's executed -- cgit v1.3