diff options
| author | Malcolm Tredinnick <malcolm.tredinnick@gmail.com> | 2008-11-14 07:42:50 +0000 |
|---|---|---|
| committer | Malcolm Tredinnick <malcolm.tredinnick@gmail.com> | 2008-11-14 07:42:50 +0000 |
| commit | 68a74843d75ee8003213ddb0a3ec474fb621b909 (patch) | |
| tree | 1b1ed7b43c3743b57111f10cd6a603745ace086d | |
| parent | 1c6f2b9ec8ee37dfcc2c712ebe39fb9be99506f5 (diff) | |
[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
| -rw-r--r-- | docs/faq/models.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/faq/models.txt b/docs/faq/models.txt index 4a33914ec9..822fdc9d77 100644 --- a/docs/faq/models.txt +++ b/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 |