On 3/25/07, Michael Bayer <[EMAIL PROTECTED]> wrote: > Still, all of these measures require that we actually get an error > thrown to detect that a restart took place, which inconveniently > usually happens not at the point of cursor() but at the point of > execute(), and we dont have any frameworks in place (nor am i > terribly comfortable with) to handle "error was thrown, reconnect and > try execute() again". lots of things can go wrong with that, namely > transactional state getting lost, mis-interpreted errors resulting in > double-executions, race conditions, etc. so i dont know if theres a > way to recover from DB restarts 100% seamlessly.
I agree, trying to make it seamless is a waste of time. I'd just like to see it be able to re-connect and work again on new queries, eventually. I'll have a look at the ticket but the Fairies intimidate me. :) -Jonathan --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
