You can do that if after insert/update/delete you do db(...).select(cache=(cache.disk,0))
Massimo On Mar 9, 9:06 am, Praneeth <life...@gmail.com> wrote: > Would it be better to have a non time based caching? Say refresh cache > on DB update? > Time based caching requires guessing the cache time - which in my > opinion seems like a bad thing to do. > > Thoughts? > > -- > Praneeth > > On 03/09/2010 08:33 PM, mdipierro wrote: > > > It is there already. > > > values=db(...).select(cache=(cache.disk,3600)) > > > 3600 is the time. > > > On Mar 9, 5:23 am, Praneeth <life...@gmail.com> wrote: > > >> Hello all, > > >> I was wondering if DAL level caching could be added. I am aware of > >> cache.ram and cache.disk, but these require the usage of a decorator > >> over the functions. I feel that a cache option to cache at the DAL level > >> that could be enabled by flipping an option in db.py of an application > >> would be of great help. The cache can be a key value pair of sorts, > >> where the cache is flushed on each write/update and cached on the first > >> read - There are probably smarter ways of doing this. > > >> Thoughts? > > >> -- > >> Praneeth -- You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web...@googlegroups.com. To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/web2py?hl=en.
