we stand on the shoulders of giants documenting web2py ;-P On Wednesday, August 6, 2014 5:29:00 PM UTC+2, LoveWeb2py wrote: > > That is the best answer. Sorry about the question. I swear I searched > through the book before asking, but this really does a nice job of > explaining it. > > Thanks, Niphlod! > > On Wednesday, August 6, 2014 10:51:05 AM UTC-4, Niphlod wrote: >> >> >> http://web2py.com/books/default/chapter/29/06/the-database-abstraction-layer?search=cacheable#Caching-selects >> >> On Wednesday, August 6, 2014 4:19:12 PM UTC+2, LoveWeb2py wrote: >>> >>> Hello, >>> >>> I'm trying to understand the cacheable=True option. Does this just make >>> the database cacheable or does it actually cache it. When I check web2py's >>> cache status it says nothing is in the cache so I'm guessing it doesn't >>> actually cache anything. >>> >>> Is it possible to cache a SQLFORM? I'm hoping this will take a load off >>> my httpd resources which seem to spike when users access the SQLFORM. >>> >>> Also, what is the proper way to cache. I've been looking at the web2py >>> cheat sheet but its a little confusing for me. >>> >>> Do I need to put >>> @cache('key',3600,cache.ram) >>> @cache('key',3600,cache.disk) >>> >>> On top of the function? >>> >>> What is the most memory efficient way of displaying large databases? >>> >>
-- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
