Re: [sqlalchemy] more granular logging configuration

2018-03-20 Thread Mike Bayer
On Tue, Mar 20, 2018 at 4:15 PM, Uri Okrent wrote: > > On Thursday, March 15, 2018 at 9:11:06 AM UTC-4, Mike Bayer wrote: >> >> use execution events for this, before_cursor_execute tends to be a >> good choice (but not the only one): >> >> >>

Re: [sqlalchemy] more granular logging configuration

2018-03-20 Thread Uri Okrent
On Thursday, March 15, 2018 at 9:11:06 AM UTC-4, Mike Bayer wrote: > use execution events for this, before_cursor_execute tends to be a > good choice (but not the only one): > > >

Re: [sqlalchemy] more granular logging configuration

2018-03-15 Thread Mike Bayer
On Thu, Mar 15, 2018 at 8:25 AM, Uri Okrent wrote: > Hey all, are there any more knobs to turn besides the logging debug level > ("DEBUG", "INFO")? Specifically I would like to somehow be able to log > read-only queries to a separate log (or maybe even skip logging those >

[sqlalchemy] more granular logging configuration

2018-03-15 Thread Uri Okrent
Hey all, are there any more knobs to turn besides the logging debug level ("DEBUG", "INFO")? Specifically I would like to somehow be able to log read-only queries to a separate log (or maybe even skip logging those altogether) since they are far more numerous and frequent. Thanks --