Chris Withers wrote: > Hi All, > > We had to restart our MySQL server recently. > > All our SQLAlchemy-based client apps then threw an error like the > following: > > File > "/usr/lib/python2.5/site-packages/SQLAlchemy-0.5.8-py2.5.egg/sqlalchemy/engine/base.py", > line 931, in _handle_dbapi_exception > raise exc.DBAPIError.instance(statement, parameters, e, > connection_invalidated=is_disconnect) > OperationalError: (OperationalError) (2006, 'MySQL server has gone away') > > They were fine after that, but I have a (maybe overly high?) expectation > that SQLAlchemy would know about this class of error (which basically > means "start a new connection and try your statement again", right?) and > "do the right thing". > > Is there any way to get the behaviour I'm after?
how many times did you get the error ? assuming you have a single engine/pool for your whole app, you'd get that error exactly once. If you turn on pool logging you'd see the whole pool disposed and replaced with a new one. > > Chris > > -- > 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. > > -- 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.
