given you can pass whatever you want to cache_count, I'd say you can use whatever technique you'd like. Of course "approximation" won't never land to "perfectness" ;-P
On Wednesday, October 8, 2014 12:45:28 PM UTC+2, Johann Spies wrote: > > This thread triggered a thought regarding very large tables: Would it be > practical to use the estimates from the backend's query planner to > determine cache_count? If a whole table is selected then one could use the > stats from the backend to estimate the total number of rows, but if you > execute a query that limits the number of records, the query planner might > be of help. > > Regards > Johann > -- > Because experiencing your loyal love is better than life itself, > my lips will praise you. (Psalm 63:3) > -- 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/d/optout.
