Django

Code

Ticket #7059 (closed: fixed)

Opened 6 months ago

Last modified 4 months ago

Effect of the DEBUG setting not explained in the settings documentation

Reported by: simonb Assigned to: nobody
Milestone: Component: Documentation
Version: SVN Keywords: debug, settings
Cc: bnomis@gmail.com Triage Stage: Ready for checkin
Has patch: 1 Needs documentation: 0
Needs tests: 0 Patch needs improvement: 0

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

7059.diff (0.6 kB) - added by programmerq on 06/15/08 01:01:54.

Change History

06/15/08 01:01:54 changed by programmerq

  • attachment 7059.diff added.

06/15/08 01:06:59 changed by programmerq

  • needs_better_patch changed.
  • has_patch set to 1.
  • stage changed from Unreviewed to Ready for checkin.
  • needs_tests changed.
  • needs_docs changed.

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.

06/19/08 07:13:44 changed by russellm

  • status changed from new to closed.
  • resolution set to fixed.

(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/Change #7059 (Effect of the DEBUG setting not explained in the settings documentation)




Change Properties
Action