Re: [Sqlalchemy-tickets] [sqlalchemy] #1926: Patch for letting multiple engines and pools use a sin
Brought to you by:
zzzeek
Menu
▾
▴
Re: [Sqlalchemy-tickets] [sqlalchemy] #1926: Patch for letting multiple engines and pools use a single stdlib logger each
|
From: sqlalchemy <mi...@zz...> - 2010-11-18 10:37:54
|
#1926: Patch for letting multiple engines and pools use a single stdlib logger
each
-------------------------+--------------------------------------------------
Reporter: guest | Owner: zzzeek
Type: enhancement | Status: new
Priority: medium | Milestone: 0.7.0
Component: engine | Severity: major - 1-3 hours
Keywords: | Status_field: in queue
-------------------------+--------------------------------------------------
Comment(by guest):
Replying to [comment:6 zzzeek]:
> agree on libraries adding handlers. but the echo=True is unbelievably
useful for quick scripts. if the echo flag isn't used, none of the
handler stuff is used either.
I see that. What I say about libraries adding handlers is that they
shouldn't do so ''automatically'', but that it's OK for them to provide a
documented convenience API that adds handlers. The echo flag is
effectively that, and as long as application developers are made aware
that setting echo has the double effect of setting verbosity + adding
handlers, there (hopefully) shouldn't be any problems.
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/1926#comment:7>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|