hey there -attached is another patch, which affects the instrumented Cursor and Connection objects so that it is impossible to return a connection to the pool without all cursors being closed; it throws an error otherwise.
after running all the unit tests with SA, the only time this happens is during a rollback(); i added an extra step to rollback to explicitly close all open cursors after rolling back to fix that issue.
so when you apply this patch, im hoping that it either fixes the problem, or you suddenly get lots of errors saying "This connection still has X open cursors", which will pinpoint exactly where cursors are staying open when connections are being returned to the pool.
because it will potentially raise a bunch of errors im trying to hold off on committing this patch just yet.
give it a try ! also attached to ticket # 306.
cursors_check.diff
Description: Binary data
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________ Sqlalchemy-users mailing list Sqlalchemy-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users
