#5236: Provide stack trace information in sql debug entries
---------------------------------+------------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: PhiR
Status: closed | Component: Database wrapper
Version: SVN | Resolution: wontfix
Keywords: feature debug | Stage: Ready for checkin
Has_patch: 1 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
---------------------------------+------------------------------------------
Changes (by mtredinnick):
* status: assigned => closed
* resolution: => wontfix
Comment:
Thanks for taking the time to make the patch, but no thanks. Running with
DEBUG=True is useful in a lot of situations and we don't need this type of
overhead all the time there.
If you want to do this, you can replace the !CursorDebugWrapper.execute
with your own function in, say, settings.py, so no changes to core are
necessary (the advantage of functions as first class objects).
--
Ticket URL: <http://code.djangoproject.com/ticket/5236#comment:6>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
