On Aug 9, 10:05 am, Steve Smith <[email protected]> wrote: > Hey, I haven't seen the errors personally and have quite a few apps running > on Heroku. I have been really happy with the service. > > However, does the failure actually stop the rendering of your page and raise > an error? I think what heroku are suggesting is that when the connection is > lost the client library should reconnect and try again without raising an > error, I take it this is not the case?
Yes, it stops rendering the page since the Exception is not caught by anything. My problem with their response (and what I asked them with no response back) is: 1. Where do I do this re-connection. Shoud I surround each DB query with a rescue block? Seems cumbersome. Or do I monkey-patch it deep in the Rails framework where the requests are being submitted. 2. For a SELECT I could just re-submit but what about an INSERT or UPDATE? Did the previous one go through? Should I resubmit those? To these questions I got NO response from Heroku. -- You received this message because you are subscribed to the Google Groups "Heroku" 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/heroku?hl=en.
