automatically, no. manually, call engine.dispose() or connection.invalidate(). we have some support for automatic connection invalidation in mysql. in postgres we have made some attempts but havent really narrowed down where the errors get thrown and how to distinguish them from regular SQL errors....generally its extremely tedious to test since you have to keep stopping/starting postgres, etc.,
FTR, ive never seen any connection pools in any language (Java, etc. ) that can gracefully handle reconnections...they all require restarting of some kind. On Mar 25, 2007, at 2:15 PM, Andreas Jung wrote: > How does SA deal internally with connection errors or when connections > go away. In my particular case Zope creates a new session for every > incoming HTTP request. What will happen if the corresponding server > process dies (e.g. the postmaster of Postgres crashes)? Is SA able > to re-establish a connection when needed? > > Andreas --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
