Technically it is a problem. The fact is even if the DAL catches it, how does it know how to deal with it?
Isn't it better if you catch it in you code or if you use routes_onerror to redirect the user to an error page? On Nov 4, 5:51 am, Guillermo <gnh...@gmail.com> wrote: > Dear all > > Yesterday (november 3rd) Googgle's datastore was in maintenance and > during that period it was in read only mode. > > In the app engine website they recommended us to include the following > code do handle exceptions: > > google.appengine.runtime.apiproxy_errors.CapabilityDisabledError. This > will be thrown by db.Model.put(), db.Model.delete(), and > db.run_in_transaction(). You can use Python's try syntax to fail > gracefully on writes like this: > > from google.appengine.ext import db > from google.appengine.runtime.apiproxy_errors import > CapabilityDisabledError > myModel = db.Model() > try: > myModel.put() > except CapabilityDisabledError: > # fail gracefully here > pass > > In the web2py framework the web2py.gluon.contrib.gql.py file has > several calls for these functions (db.Model.put(), db.Model.delete(), > and db.run_in_transaction()). > > It is possible to update the gql.py file to handle the exception? > Thank you. > > Best regards, > > Guillermo --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
