I started adding @cache on my functions without thinking the consequences.
For example, I have a function that returns that grid. So caching that
function would be a bad idea. =/
Em domingo, 4 de maio de 2014 15h59min11s UTC-3, Niphlod escreveu:
>
> what do you mean by "a wrong implementation o
what do you mean by "a wrong implementation of cache" ?
On Sunday, May 4, 2014 2:14:40 PM UTC+2, Elcimar wrote:
>
> I will keep testing it for sure.
> I also was wondering if a wrong implementation of cache would cause this.
>
>
--
Resources:
- http://web2py.com
- http://web2py.com/book (Docu
I will keep testing it for sure.
I also was wondering if a wrong implementation of cache would cause this.
--
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)
-
the redis backend usues the same "logic" as session files, so a "bug" in
the code would show anyway...
to make a grid A go to page # means that you left another grid B at page #
if you're using defaults without specifying the formname argument. I don't
think there's another "hole" that makes gr
Well...
- It happens when the app is in production.
- It magically happens SOME(random)TIMES simply by opening the page and
hitting F5.
- It doesn't happen when I'm testing it in my development virtualbox vm.
- Nope, I'm not using reserved keywords, I prefer using im my native
language.
I sus
does this "magically" happens when you just left another grid at page #
1000 ? because that would be expected, since all grids share the same
session values to "remember" what the page # is. Also, please make sure
you're not using "reserved" request.vars (i.e. page=x) because then you're
tricki
6 matches
Mail list logo
