On 8 October 2013 15:24, Niphlod <niph...@gmail.com> wrote: > the smartest thing to do would be to avoid orderby when there are less > records than paginate. > ... > > What we should orderby to then? The only assured field that has an implicit > index is the id (being a PK). Orderby(ing) a PK should definitely not > require a full scan. > > Why would it be necessary then to do add the id of all the tables involved in the query? My workaround is to specify the orderby using the id of one of the involved tables and that already makes a big difference measured against a query trying to use three or four fields when ordering.
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/groups/opt_out.
