Hi, it's not obvious, nothing said in a docs about default pool setup and The Database options section has: pool=None - an actual pool instance. that's why I conclude that pool is NOT setup by default. I just want to confirm that.
Valentin. On Mar 14, 1:34 pm, Sébastien LELONG <[EMAIL PROTECTED] securities.fr> wrote: > > So that's why I'm confused. Does the pooling is turn on by default or > > not ? > > IIRC, a default pool is set according to the type of engine (eg. > SingletonThreadPool for sqlite, QueuePool for MySQL, or the like...). So it's > set by default, but you can of course override this with your own pool, > as > you described. > > > In this case when I invoke multiple times con=engine.connect(), does > > the connection will be take from pool? If connection will timeout, > > does pool guarantee to make a new one? > > Use pool_recycle parameter so prevent any timeout. > > Hope it helps. > > Cheers > > Seb > -- > Sébastien LELONG > sebastien.lelong[at]sirloon.nethttp://www.sirloon.net --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
