You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The example paging provider in the source repository does an offset/limit query on each page. According to ex the PostgreSQL documentation it's not recommended to do that without an order by. https://www.postgresql.org/docs/current/queries-limit.html . Is it even possible to make reliable server-side paging when the order is not guaranteed?
The text was updated successfully, but these errors were encountered:
Actually, also server driven paging shall by default create an ORDER BY primary key, as it is done for client driven paging with $top and $skip. This is a bug.
The example paging provider in the source repository does an offset/limit query on each page. According to ex the PostgreSQL documentation it's not recommended to do that without an order by. https://www.postgresql.org/docs/current/queries-limit.html . Is it even possible to make reliable server-side paging when the order is not guaranteed?
The text was updated successfully, but these errors were encountered: