On 1 June 2015 at 20:22, Anthony <abasta...@gmail.com> wrote: > Thanks Anthony. Correct. I do not want it in all cases. After reading up >> on it I came accross this link ( >> http://chrisdone.com/posts/postgresql-pagination) where the author >> illustrates just how slow PostgreSQL's "OFFSET" can be which is probably >> part of my problem in this case. I will just have to develop alternative >> methods to work with cases where one queries millions of rows. One of my >> tables has more than 500 million records. >> > > The difference between your two cases wasn't whether OFFSET was used (both > involved pagination) but rather whether the "id" field was used for > sorting. Does the difference between the two queries go away if you remove > the OFFSET? > > Apologies for my unclear "in this case". I actually meant the situation of working with such large datasets. No in the case of the original question I was not moving away of OFFSET 0.
Thanks for your attention. 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.