From 7db89f79b33474f21f3a1b402e63d243976cc110 Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Wed, 22 Oct 2014 14:12:47 -0400 Subject: [PATCH] [1.7.x] Added a warning about running migrations with DEBUG=True. Thanks Charles Lanahann for the report. --- docs/topics/migrations.txt | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/docs/topics/migrations.txt b/docs/topics/migrations.txt index 1321d5908d..dd5f5e7d1f 100755 --- a/docs/topics/migrations.txt +++ b/docs/topics/migrations.txt @@ -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 the data migration will run in place alongside other migrations. +.. note:: + + Be careful when running a migration with :setting:`DEBUG=True ` as + Django :ref:`saves all 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 :class:`~django.db.migrations.operations.RunPython` to run whatever logic you want executed when migrating backwards. If this callable is omitted, migrating