#12012: Integration with the Python standard library logging module
-------------------------------------+--------------------------------------
Reporter: simon | Owner: nobody
Status: new | Milestone: 1.3
Component: Core framework | Version: SVN
Resolution: | Keywords:
Stage: Accepted | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-------------------------------------+--------------------------------------
Changes (by russellm):
* needs_better_patch: 1 => 0
* needs_tests: 1 => 0
* needs_docs: 1 => 0
Comment:
@anon - Nothing in particular; if you want to log to database, that's
certainly an option with an appropriate handler.
My only concern would be the extra database load that this logging
technique would introduce, but that isn't something that you can declare
as universally bad; it entirely depends on your load pattern and the
amount of logging you intend to do.
--
Ticket URL: <http://code.djangoproject.com/ticket/12012#comment:23>
Django <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 django-upda...@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
