On MySQLdb (1.2.2) we still experience stale uncommitted transactions and...

On MySQLdb (1.2.2) we still experience stale uncommitted transactions and different warden_server processes don't see actual db data. Looks like there is at least one stale transaction per daemon, appearing at any call to execute. I have no better idea than to implicitly commit after each SELECT (INSERTs are committed/rolled back explicitly).