On Sat, Oct 23, 2010 at 9:22 PM, Michael Bayer <mike...@zzzcomputing.com> wrote: > > pool recycle means a connnection that is 3600 seconds old will be thrown > away. does not help with reconnects. > > When a "server gone away" error is detected, the entire connection pool is > thrown away and rebuilt. So assuming one engine, you'd get this error once > for each connection that is still checked out and attempts a new operation. > Subsequent transactions will proceed since the pool has been rebuilt. > > There was also a Mysql-reconnect bug fixed in 0.6.3 where previous versions > might have impacted this. >
I want to know if this means that the first transaction will still be failed, and others will be successful? And sqlalchemy can automatically rebuild at the time the error occured but not the next time? -- I like python! UliPad <<The Python Editor>>: http://code.google.com/p/ulipad/ UliWeb <<simple web framework>>: http://code.google.com/p/uliweb/ My Blog: http://hi.baidu.com/limodou -- 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.
