Good to hear some work is being done one this. I'm having the exact same problem as the OP describes. In my case, downgrading down to SA 0.2.7, not changing anything else, makes the problem go away - except of course I don't have many wonderfuls SA 0.3.0 features :o)
On 12/8/06, Michael Bayer <[EMAIL PROTECTED]> wrote: > So i have checked in a fix in 2132 that does not prevent the error but > *does* keep it from being catastrophic, and its that the mysql dialect > catches error code 2006 and 2014 and invalidates the connection before > re-throwing the error, so that at least the pool doesnt get filled up > with busted connections. So in a webserver environment this makes just the request where the error happens fail, instead of making all subsequent requests on the same thread fail.. correct? If so, half the battle is won in my case. Arnar --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
