just to clarify: the fact that a query in pgadmin returns a somewhat ordered resultset "that you're good with", that you "test queries in raw postgresql before you implement" and that web2py shows the same result with auto_pagination=False is not in ANY scenario an assurance of the fact that your results will be paginated correctly.
auto_pagination=False is somewhat to be considered like "please do it wrongly, *hope for the best*". If you don't use a correct clause to order by with, your mileage may vary but an error will definitely pop up (wrong records in next page, or duplicate records in several pages). "*prepare for the worst*". That's database 101 (and Set Theory, the math on which relational databases are founded on).... repeat after me: a Query defines a Set, a Set is by design unordered, a Set is by design unordered, a Set is by design unordered ....... the result is the ordered Set. If you like your users to paginate wrongly instead of fixing the database, it's your choice to make, but its strongly advised against by "sane defaults" (read Set Theory, every best practice out there, etc etc etc) -- 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.
