diff options
| author | Ola Sitarska <ola@sitarska.com> | 2014-09-21 17:46:01 +0200 |
|---|---|---|
| committer | Baptiste Mispelon <bmispelon@gmail.com> | 2014-09-21 18:34:08 +0200 |
| commit | 99c2e40384ff74755145e05bd12f081316941e81 (patch) | |
| tree | 813028a8c843dcf7bc7ad9744f42408b4a0191f1 | |
| parent | 02b3a6dcc0aef39f9174d4ac7a70679161de0962 (diff) | |
[1.7.x] Fixed #23512 -- Made migration docs about initial_data clearer
Thanks @abhillman and @Markush2010 for submitting the ticket.
Backport of 21819e6dbf422fe3ebe23cc006c0ef7bfc5c73de from master.
| -rw-r--r-- | docs/releases/1.7.txt | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/docs/releases/1.7.txt b/docs/releases/1.7.txt index 4ab25b7e72..4749e300fa 100644 --- a/docs/releases/1.7.txt +++ b/docs/releases/1.7.txt @@ -65,7 +65,9 @@ but a few of the key features are: it as soon as possible (nothing more than renaming is required). * ``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, Django will no longer emulate rollbacks on non-transactional databases or |