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
Note: The offset-based pagination approach used above has some disadvantages. If the data changes (records added/modified/removed) such that the ordering changes, the user may see duplicated results as they paginate through the data.
Additionally, the query contains the total number of records, which entails doing a COUNT(*), to derive the total number of pages. In large datasets, this may be expensive.
We could also include an infinite-scroller style of pagination to avoid page numbering:
For paginated queries, we should return a result type that contains the page info. E.g.
Note: The offset-based pagination approach used above has some disadvantages. If the data changes (records added/modified/removed) such that the ordering changes, the user may see duplicated results as they paginate through the data.
Additionally, the query contains the total number of records, which entails doing a
COUNT(*)
, to derive the total number of pages. In large datasets, this may be expensive.We could also include an infinite-scroller style of pagination to avoid page numbering:
And use cursor-based pagination to prevent the other issues.
The text was updated successfully, but these errors were encountered: