Commit 68a74843 authored by Malcolm Tredinnick's avatar Malcolm Tredinnick
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
parent 1c6f2b9e

docs/faq/models.txt

+1 −1
Original line number Diff line number Diff line
@@ -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