Connection checkouts from pool are not logged
I remeber that this worked on previous versions but I'm not sure when it stopped working. It seems like there are no longer log lines when a connection is being checked out from the pool, only when it is returned back to the pool.
Tested with 0.9.7.
The output for running the attached test file is: DEBUG:sqlalchemy.pool.QueuePool:Created new connection <pymysql.connections.Connection object at 0x7f129737d3d0> DEBUG:sqlalchemy.pool.QueuePool:Connection <pymysql.connections.Connection object at 0x7f129737d3d0> being returned to pool DEBUG:sqlalchemy.pool.QueuePool:Connection <pymysql.connections.Connection object at 0x7f129737d3d0> rollback-on-return DEBUG:sqlalchemy.pool.QueuePool:Connection <pymysql.connections.Connection object at 0x7f129737d3d0> being returned to pool DEBUG:sqlalchemy.pool.QueuePool:Connection <pymysql.connections.Connection object at 0x7f129737d3d0> rollback-on-return
Comments (4)
-
repo owner -
repo owner - changed status to resolved
- Fixed bug in connection pool logging where the "connection checked out"
debug logging message would not emit if the logging were set up using
logging.setLevel()
, rather than using theecho_pool
flag. Tests to assert this logging have been added. This is a regression that was introduced in 0.9.0. fixes#3168
→ <<cset 92b0ad0fef0b>>
-
repo owner - Fixed bug in connection pool logging where the "connection checked out"
debug logging message would not emit if the logging were set up using
logging.setLevel()
, rather than using theecho_pool
flag. Tests to assert this logging have been added. This is a regression that was introduced in 0.9.0. fixes#3168
→ <<cset 7704b7ec52a0>>
- Fixed bug in connection pool logging where the "connection checked out"
debug logging message would not emit if the logging were set up using
-
repo owner thanks for your report !
- Log in to comment