On Fri, Nov 4, 2011 at 4:45 PM, Michael Bayer <mike...@zzzcomputing.com> wrote: ... > > OK this is clearer to me. So you're really trying to get it so that any > number of create_engine() calls all use the same pool based on hostname, OK. > > If i have time today I might want to try paring this down a lot more. > Also not sure why you need the "disconnect check" stuff in execute() , SQLA > has that stuff built in.
I did not know. Do you have any pointer ? > But it does raise an important point that the mechanism by which we dispose >the pool when a disconnect is detected probably should be different here, >since the disposal is per-engine, just gives itself a new pool. The other >engines will still point to the old, disposed pool, probably causing some kind >of pileup. Ah I see.. maybe some kind of event the engine can register to, to refresh its pool variable ? Cheers Tarek -- Tarek Ziadé | http://ziade.org -- 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 sqlalchemy+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en.
