do people have this problem working with MySQLDB directly ? im sorta running out of options here.
to clean out the pool you can say engine.connection_provider._pool.dispose(), or just engine.dispose (). im pretty sure it will create new connections if you keep using it after the dispose. On Sep 14, 2006, at 1:19 PM, Karl Guertin wrote: > On 9/14/06, Michael Bayer <[EMAIL PROTECTED]> wrote: >> perhaps MySQLDB is not doing a good job of cleaning up cursors. and >> when i just looked, i saw that SQLAlchemy isnt either. try this >> patch: > > Unfortunately, that doesn't fix the problem. And for Andrius, I am > running 1.2.1, so I can't really upgrade further. The known bug in > mysqldb only occurs with 5.0.24 due to an ABI change. ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Sqlalchemy-users mailing list Sqlalchemy-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users
