mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2025-06-05 03:29:12 +00:00
Code Issues 32 Releases Wiki Activity

[1.7.x] Added a warning about running migrations with DEBUG=True.

Browse Source 
Thanks Charles Lanahann for the report.
This commit is contained in:
Tim Graham 2014-10-22 14:12:47 -04:00
parent 81095a1ae5
commit 7db89f79b3
1 changed files with 7 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
docs/topics/migrations.txt
View File

@ -418,6 +418,13 @@ need to do is use the historical model and iterate over the rows::
Once that's done, we can just run ``python manage.py migrate`` as normal and Once that's done, we can just run ``python manage.py migrate`` as normal and
the data migration will run in place alongside other migrations. the data migration will run in place alongside other migrations.
.. note::
Be careful when running a migration with :setting:`DEBUG=True <DEBUG>` as
Django :ref:`saves all SQL queries <faq-see-raw-sql-queries>` that are run
which may result in large memory usage. This issue is addressed in
Django 1.8 where only 9000 queries are saved.
You can pass a second callable to You can pass a second callable to
:class:`~django.db.migrations.operations.RunPython` to run whatever logic you :class:`~django.db.migrations.operations.RunPython` to run whatever logic you
want executed when migrating backwards. If this callable is omitted, migrating want executed when migrating backwards. If this callable is omitted, migrating