diff options
| author | Russell Keith-Magee <russell@keith-magee.com> | 2008-06-19 12:13:43 +0000 |
|---|---|---|
| committer | Russell Keith-Magee <russell@keith-magee.com> | 2008-06-19 12:13:43 +0000 |
| commit | a7f6faaa818d91aa9baaf1db99974cb1209c8ee6 (patch) | |
| tree | 7780bee25d386161381b9f23ed99dcea03939a9e /docs | |
| parent | 5da67a084ad6a814c867c3c374f7e869dffac29e (diff) | |
Fixed #7059 -- Added a note to the settings documentation reminding users that when DEBUG=True, Django keeps a log of queries. Thanks for the suggestion, simonb.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@7702 bcc190cf-cafb-0310-a4f2-bffc1f526a37
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/settings.txt | 9 |
1 files changed, 7 insertions, 2 deletions
diff --git a/docs/settings.txt b/docs/settings.txt index a1c8c749dd..3fe999d0d2 100644 --- a/docs/settings.txt +++ b/docs/settings.txt @@ -388,8 +388,13 @@ be able to give backtraces without seeing sensitive (or offensive) settings. Still, note that there are always going to be sections of your debug output that are inappropriate for public consumption. File paths, configuration options, and -the like all give attackers extra information about your server. Never deploy a -site with ``DEBUG`` turned on. +the like all give attackers extra information about your server. + +It is also important to remember that when running with ``DEBUG`` turned on, Django +will remember every SQL query it executes. This is useful when you are debugging, +but on a production server, it will rapidly consume memory. + +Never deploy a site into production with ``DEBUG`` turned on. DEBUG_PROPAGATE_EXCEPTIONS -------------------------- |