We do use MEMDB with the memcache client for sessions. Do you know when this
bug was introduced? We are still running 2.5.1 in production, but were looking
to upgrade soon.
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
Does this only apply to GAE use? We use memcache for sessions but not GAE.
Thanks,
--Joel.
On Wednesday, November 13, 2013 6:19:14 PM UTC-6, Massimo Di Pierro wrote:
>
> A serious issue has been reported on web2y-developers. The issue has to do
> with the memdb module. You are using it if you u
That's too bad. Is there a reason for it, or just haven't found any use
for it yet?
On Wednesday, November 13, 2013 10:49:43 AM UTC-6, Niphlod wrote:
>
> nice shot, but scheduler isn't supported in MEMDB.
>
> On Wednesday, November 13, 2013 6:25:40 AM UTC+1, Joel
Hey all,
I was attempting to set up a scheduler using a memcache backed MEMDB as the
store, but I keep getting this error.
int() argument must be a string or a number,
not 'MemcacheClientObj'
Traceback:
Traceback (most recent call last):
File "/usr/home/jrathgaber/bunnyhugdev/web2py/gluon/
Submitted as #1685
On Thursday, September 19, 2013 12:47:09 PM UTC-6, Massimo Di Pierro wrote:
>
> Please open a ticket about this.
>
>
> On Thursday, 19 September 2013 13:07:38 UTC-5, Joel Rathgaber wrote:
>>
>> We are putting things in the session, so it shouldn'
f it is not saved there is no
> point in assigning a cookie.
>
> On Thursday, 19 September 2013 11:13:42 UTC-5, Joel Rathgaber wrote:
>>
>> Hey all,
>>
>> I've noticed that in the 2.5 and prior releases that the session id
>> cookie was sent back to th
Hey all,
I've noticed that in the 2.5 and prior releases that the session id cookie
was sent back to the client in every response, and it seems like in 2.6 it
doesn't do this anymore. Is this by design? If so, what's the reasoning?
Thanks!
--Joel.
--
Resources:
- http://web2py.com
- http://
7 matches
Mail list logo
