On Fri, Sep 19, 2014 at 05:43:46PM -0700, Iain Duncan wrote: > 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?
Yes, that's right, I think. You'll get a brand new connection every time. (The connection will be closed when the Session committed or rolled back, and a new one opened whenever the Session needs one again.) > Is is terribly slower? It depends on how many connections you're making. My guess is that the difference is probably not noticeable until your connection rate gets up to a few connections per second. Using a (non-null) pool with a short (few seconds) setting for ``recycle`` would accomplish much the same thing, while allowing for connection pooling during times of high connection rate. -- 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.
