Rick Morrison wrote: > > I was thinking of a user-level option for liveliness checking on pool > checkout, with dialect-specific implementations (e.g. execute a 'SELECT > 1', or something more efficient if the driver allows). Is that in line > with what you were thinking? > > > I had in mind something more of a optimistic / reactive nature, like a > retry on a cursor failure. But this could work equally well and could be > much simpler, albeit at some round-trip time on every pool checkout. > > What's the recovery strategy if the connection is found to be dead? An > auto-reconnect with some retry count limit, or would it just notify the > dialect and that's it?
I believe right now it's a limited # of retries. (The basic support for ping-on-checkout is already in the pool as of 0.4, but no dialect hooks yet.) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
