[web2py] Re: The odd behavior of cacheable selects. Bug?

2013-12-06 Thread Leonel Câmara
Issue submitted https://code.google.com/p/web2py/issues/detail?id=1803 Sorry for the delay. Quinta-feira, 5 de Dezembro de 2013 20:05:38 UTC, Leonel Câmara escreveu: > > If I have this in my DB: > > db = DAL('sqlite://storage.sqlite', check_reserved=[]) > > db.define_table('test_table', > Fi

[web2py] Re: The odd behavior of cacheable selects. Bug?

2013-12-05 Thread Leonel Câmara
Sure, I will open the bug later today. Quinta-feira, 5 de Dezembro de 2013 20:05:38 UTC, Leonel Câmara escreveu: > > If I have this in my DB: > > db = DAL('sqlite://storage.sqlite', check_reserved=[]) > > db.define_table('test_table', > Field('value'), > ) > > if db(db.test_table.id > 0).count

[web2py] Re: The odd behavior of cacheable selects. Bug?

2013-12-05 Thread Niphlod
BTW: in my fast trial I get the same behaviour even with cacheable=True. This may be due to the fact that cache.ram stores a "pointer" of the rows. If you try with cache.disk or any other cache backend, it's ok. -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http:/

[web2py] Re: The odd behavior of cacheable selects. Bug?

2013-12-05 Thread Niphlod
it surely counts for a bug. Would you mind opening an issue on google code so it gets tracked ? On Thursday, December 5, 2013 9:05:38 PM UTC+1, Leonel Câmara wrote: > > If I have this in my DB: > > db = DAL('sqlite://storage.sqlite', check_reserved=[]) > > db.define_table('test_table', > Fiel