Code

Opened 6 years ago

Closed 6 years ago

#7059 closed (fixed)

Effect of the DEBUG setting not explained in the settings documentation

Reported by: simonb 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 programmerq 6 years ago.

Download all attachments as: .zip

Change History (3)

Changed 6 years ago by programmerq

comment:1 Changed 6 years ago by programmerq

  • Has patch set
  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Triage Stage changed from Unreviewed to Ready 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 6 years ago by russellm

  • Resolution set to fixed
  • Status changed from new to closed

(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.

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.