So can anyone tell me what exactly happens with NullPool, I'm not clear from the docs. Does that mean a fresh connection will be made on a new hit, and we'll never get the "gone away", but at the expense of slower connections?
Is is terribly slower? thanks! Iain On Fri, Sep 19, 2014 at 2:27 PM, Iain Duncan <[email protected]> wrote: > Thanks guys! > > Iain > > On Fri, Sep 19, 2014 at 12:41 PM, Jonathan Vanasco <[email protected]> > wrote: > >> Just to add to jeff's response, I had a similar situation with Postgres >> under a twisted app a while back. >> >> Someone else on the twisted list was using Mysql + Twisted + Sqlalchemy >> and pointed to some pessimistic reconnect code they used in buildbot : >> >> >> http://twistedmatrix.com/pipermail/twisted-python/2014-June/028410.html >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "sqlalchemy" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To post to this group, send email to [email protected]. >> Visit this group at http://groups.google.com/group/sqlalchemy. >> For more options, visit https://groups.google.com/d/optout. >> > > -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
