opening and closing a connection corresponds with its being retreived/ returned from/to the connection pool. you should generally keep connections opened for as short a time as possible.
the save() method on session doesnt use a connection for anything as far as i can recall so im not sure how thats related. On Sep 26, 2006, at 1:54 PM, Ed Suominen wrote: > Currently, sAsync re-uses the connection object for every transaction, > but that doesn't seem to be working with session.save(u). > > I could just close the connection after each transaction.commit() or > session.flush() and open a new one for the next transaction, but I'm > wondering what impact that would have on performance, if any. > > Best regards, Ed > > ---------------------------------------------------------------------- > --- > 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 ------------------------------------------------------------------------- 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
