mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2025-07-20 17:49:12 +00:00
Code Issues 32 Releases Wiki Activity

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

Browse Source 
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
This commit is contained in:
Malcolm Tredinnick 2008-11-14 07:42:50 +00:00
parent 1c6f2b9ec8
commit 68a74843d7
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/faq/models.txt
View File

@ -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