On Jan 27, 2011, at 10:38 AM, Jon Nelson wrote: > I'm trying to diagnose an issue with temporary tables, so I cranked up > the debug levels to DEBUG. > > I noticed something strange: > > 2011-01-27 09:34:12,818 DEBUG [sqlalchemy.pool.QueuePool.0x...e410] > Connection <connection object at 0x12e1d50; dsn: 'dbname=BLAH > host=localhost user=BLAH password=xxxxxxx', closed: 0> checked out > from pool > 2011-01-27 09:34:12,819 INFO > [sqlalchemy.engine.base.Engine.0x...e510] BEGIN (implicit) > > NOTE: The connection object (0x12e1d50) doesn't match the log string > of the subsequent statement (0x...e510). > That identifier matches an /earlier/ connection that was checked out > and returned to the pool. > > BUG?
The log string 0x...e510 refers to the identity of the Engine itself, not any of the DBAPI connections that happen to be stored in its connection pool. I've never had anyone confused by that before but FWIW the hex string from engine logging won't be present anymore in 0.7. -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com. To unsubscribe from this group, send email to sqlalchemy+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en.
