Without order, pagination will be inconsistent, especially when you have lots of rows in the underlying DB table. For example two pages (as determined by the offset and limit params) may wind up having some rows in common:
Thus, using different LIMIT/OFFSET values to select different subsets of a query result will
give inconsistent results unless you enforce a predictable result ordering with ORDER BY
Describe the bug It looks like result sets aren't ordered when using pagination params, e.g.
Without order, pagination will be inconsistent, especially when you have lots of rows in the underlying DB table. For example two pages (as determined by the offset and limit params) may wind up having some rows in common:
To Reproduce N/A
Expected behavior All queries involving pagination should also have an order by clause.
Additional context See e.g.