Here's another question: What's the best practice for handling timeout (and other) db errors?
This is partly prompted by ryan's recent comment that "regardless of how your data is shaped, you'll at least see a small timeout rate. .01% is in the ballpark." [http:// groups.google.com/group/google-appengine/browse_thread/thread/ dd90847d0e7c1ceb#] I admit to not checking for timeouts for a single small put. It means that there should be some thought behind all uses of datastore with respect to db.Error. I looked at rietveld source code for some error handling examples but didn't find any interesting patterns. There are some general db.Error catches but no Timeout or CapabilityDisabled exception handling. (By the way, a couple of the last exceptions in datastore_errors.py aren't documented at http://code.google.com/appengine/docs/datastore/exceptions.html. Should documentation issues be logged in the SDK area?) If you receive a timeout, do you need to launch another request from the client because your time is already used up for the current request? I assume that many errors should re-initiate a request (or ask user to resubmit) because the time quota on each request. Is this correct? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" 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/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
