Fixed #23512 -- Made migration docs about initial_data clearer

Thanks @abhillman and @Markush2010 for submitting the ticket.
This commit is contained in:
Ola Sitarska 2014-09-21 17:46:01 +02:00 committed by Baptiste Mispelon
parent b9b8895acb
commit 21819e6dbf
1 changed files with 3 additions and 1 deletions

View File

@ -65,7 +65,9 @@ but a few of the key features are:
it as soon as possible (nothing more than renaming is required). it as soon as possible (nothing more than renaming is required).
* ``initial_data`` fixtures are no longer loaded for apps with migrations; if * ``initial_data`` fixtures are no longer loaded for apps with migrations; if
you want to load initial data for an app, we suggest you do it in a migration. you want to load initial data for an app, we suggest you create a migration for
your application and define a :class:`~django.db.migrations.operations.RunPython`
or :class:`~django.db.migrations.operations.RunSQL` operation in the ``operations`` section of the migration.
* Test rollback behavior is different for apps with migrations; in particular, * Test rollback behavior is different for apps with migrations; in particular,
Django will no longer emulate rollbacks on non-transactional databases or Django will no longer emulate rollbacks on non-transactional databases or