Fixed #9468 -- Fixed a misleading FAQ answer.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@9428 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
parent
23657aaf16
commit
a0d4749920
|
@ -79,7 +79,7 @@ Why is Django leaking memory?
|
||||||
|
|
||||||
Django isn't known to leak memory. If you find your Django processes are
|
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
|
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.
|
Django saves a copy of every SQL statement it has executed.
|
||||||
|
|
||||||
(The queries are saved in ``django.db.connection.queries``. See
|
(The queries are saved in ``django.db.connection.queries``. See
|
||||||
|
|
Loading…
Reference in New Issue