I can only provide assistance for the "unique key error": line 883: https://github.com/web2py/web2py/blame/master/gluon/globals.py: dee4e6a9<https://github.com/web2py/web2py/commit/dee4e6a980713f0a3a5bbd350e4b367c4c410327> »<https://github.com/web2py/web2py/blame/dee4e6a980713f0a3a5bbd350e4b367c4c410327/gluon/globals.py> mdipierro <https://github.com/mdipierro> 2013-08-20 new session logic
I don't know how the "int64 too big" error was introduced Am Dienstag, 4. März 2014 22:29:56 UTC+1 schrieb Massimo Di Pierro: > > can you provide a patch or a revision number that broke it? > > On Saturday, 1 March 2014 12:25:14 UTC-6, Bas Ti wrote: >> >> The current trunk does not support using memcache as session store on GAE: >> session.connect calls memdb.Table.__call__(recordid, >> unique_key=unique_key) >> >> however unique_key is not supported by memdb.Table, it is only supported >> by dal.Table >> > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- 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.
