Skip to content
Browse files

[django-1.0.X] Fixed #9468 -- Fixed a misleading FAQ answer.

Backport of r9428 from trunk.


git-svn-id: http://code.djangoproject.com/svn/django/branches/releases/1.0.X@9430 bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information...
1 parent 1c6f2b9 commit 68a74843d75ee8003213ddb0a3ec474fb621b909 @malcolmt malcolmt committed
Showing with 1 addition and 1 deletion.
  1. +1 −1 docs/faq/models.txt
View
2 docs/faq/models.txt
@@ -79,7 +79,7 @@ Why is Django leaking memory?
Django isn't known to leak memory. If you find your Django processes are
allocating more and more memory, with no sign of releasing it, check to make
-sure your ``DEBUG`` setting is set to ``True``. If ``DEBUG`` is ``True``, then
+sure your ``DEBUG`` setting is set to ``False``. If ``DEBUG`` is ``True``, then
Django saves a copy of every SQL statement it has executed.
(The queries are saved in ``django.db.connection.queries``. See

0 comments on commit 68a7484

Please sign in to comment.
Something went wrong with that request. Please try again.