Opened 8 years ago

Closed 8 years ago

#7059 closed (fixed)

Effect of the DEBUG setting not explained in the settings documentation

Reported by: Simon Blanchard Owned by: nobody
Component: Documentation Version: master
Severity: Keywords: debug, settings
Cc: bnomis@… Triage Stage: Ready for checkin
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:

Description

The full effects of setting the DEBUG setting to True should be mentioned in the settings documentation. Specifically the caching of SQL queries leading to ever increasing memory use.

Attachments (1)

7059.diff (614 bytes) - added by Jeff Anderson 8 years ago.

Download all attachments as: .zip

Change History (3)

Changed 8 years ago by Jeff Anderson

Attachment: 7059.diff added

comment:1 Changed 8 years ago by Jeff Anderson

Has patch: set
Needs documentation: unset
Needs tests: unset
Patch needs improvement: unset
Triage Stage: UnreviewedReady for checkin

Adding this clarification about this particular feature is almost definitely a good idea. I know I've read it elsewhere, but it probably should live here too.

comment:2 Changed 8 years ago by Russell Keith-Magee

Resolution: fixed
Status: newclosed

(In [7702]) 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.

Note: See TracTickets for help on using tickets.
Back to Top