On Wednesday, February 21, 2018 at 10:31:30 PM UTC+1, Mike Bayer wrote: > > or have your logger look for that "log_only" token in the logger name > and skip on that, that's more future-proof. >
Yes, using a specific logger for the engine seems to work. :-) I had looked for something like this, but didn't find it. I found http://docs.sqlalchemy.org/en/latest/core/engines.html#configuring-logging , but didn't see anything there on engine-specific logging names, so I thought it wasn't possible. (The `logging_name` argument for `create_engine` _is_ documented though.) Best regards, Stefan -- SQLAlchemy - The Python SQL Toolkit and Object Relational Mapper http://www.sqlalchemy.org/ To post example code, please provide an MCVE: Minimal, Complete, and Verifiable Example. See http://stackoverflow.com/help/mcve for a full description. --- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to sqlalchemy+unsubscr...@googlegroups.com. To post to this group, send email to email@example.com. Visit this group at https://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.