Adding the following line in the app.yaml solves the issue: auto_id_policy: legacy
This changes the ID generation from scattered to legacy mode (I assume sequential?). I presume the number returned by GAE_DB_Entity.id() is of smaller size and the exception does not occur anymore. But when I read GAE documentation, there is a statement that legacy mode will not be supported in future - so web2py needs to find a solution to this problem. Should I raise a ticket for this issue? Are there impacts to application code which does not directly use any GAE code? Br, Aravind. On Thursday, 13 June 2013 14:45:46 UTC+5:30, Aravindan Rs wrote: > > Hi, > > I get the following error stack on login / logout when session object is > attempted to be written to the database: > > Traceback (most recent call last): > File > "/base/data/home/apps/s~nittio-live/24.368055561930403768/gluon/main.py", > line 551, in wsgibase > session._try_store_in_db(request, response) > File > "/base/data/home/apps/s~nittio-live/24.368055561930403768/gluon/globals.py", > line 728, in _try_store_in_db > record_id = table.insert(**dd) > File > "/base/data/home/apps/s~nittio-live/24.368055561930403768/gluon/dal.py", line > 7806, in insert > ret = self._db._adapter.insert(self,self._listify(fields)) > File > "/base/data/home/apps/s~nittio-live/24.368055561930403768/gluon/dal.py", line > 4618, in insert > rid = Reference(tmp.key().id()) > OverflowError: Python int too large to convert to C long > > > > I'm using Google App Engine - with python 2.7 and web2py. > > I have one version of application which was deployed yesterday - this is > still working (i.e. no such errors during login/logout). I deploy the same > code today and it does not work. This morning google sent a release > announcement for google app engine 1.8.1. The change was related to > scattered auto ID (64 bits). I'm guessing my problem could be due app > engine change. > > Are others facing similar problem? Any known solutions? > > Warm Regards, > Aravind. > > > -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
