[sqlalchemy] Re: expensive .rollback() in pool implementation?

2008-05-05 Thread Andrew Stromnov
Ordered by: internal time List reduced from 178 to 20 due to restriction 20 ncalls tottime percall cumtime percall filename:lineno(function) # 2150.3710.0020.3710.002 {method 'query' of '_mysql.connection' objects} * 2150.3060.0010.3060.001 {method 'rollback'

[sqlalchemy] Re: expensive .rollback() in pool implementation?

2008-05-05 Thread Michael Bayer
thanks for the effort. Please use r4640 and specify rollback_returned=False to the Pool constructor. On May 5, 2008, at 5:53 AM, Andrew Stromnov wrote: Ordered by: internal time List reduced from 178 to 20 due to restriction 20 ncalls tottime percall cumtime percall

[sqlalchemy] Re: expensive .rollback() in pool implementation?

2008-05-05 Thread jason kirtland
Michael Bayer wrote: thanks for the effort. Please use r4640 and specify rollback_returned=False to the Pool constructor. I changed that name in r4643 to 'reset_on_return'. I'm hoping to be able to support database-specific methods for state reset in 0.5, and the new option name is a

[sqlalchemy] Re: expensive .rollback() in pool implementation?

2008-05-04 Thread Michael Bayer
On May 4, 2008, at 9:41 AM, Andrew Stromnov wrote: Recently I'd switched to SA MySQL connection pool implementation. Every time, when app returns connection to pool (through .close() method), SA triggers .rollback() on this connection (http://