> > On Wednesday, December 4, 2013 4:57:03 PM UTC+1, Anthony wrote: >> >> First, if you are using cache=..., you do not also need to set >> cacheable=True. Using the former, the DAL automatically handles caching for >> you. Setting cacheable=True is only for cases where you want to manually >> cache the Rows object, so you wouldn't be using cache=... in that case. >> > > Uhm... if I don't want auto-references, row.update_record() and > row.delete_record() I use cacheable=True AND cache=cache.ram (or > something). > cacheable=True brings a noticeable speedup for large datasets, however for > a small set, I completely agree >
Yes, good point. I just wanted to make it clear the cacheable=True is not *required* when using cache=, and in fact it reduces the functionality normally available when using cache=. For pure speed, cacheable=True is a good idea, though in that case, you can just directly cache the object if you like. Anthony -- 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 web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
