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
As I understand it currently queries don't really paginate, the query limit is just continuously increased and any duplicate ids are ignored.
i.e. it queries for 20 items, then 40, 60, 80, etc.
In some cases this can cause a lot of document reads.
I don't think this would cause an issue, startAt requires a orderBy but so does limit.
I was thinking something like:
stepLimit + 1 because I choose to use startAt rather than startAfter in case there are multiple items with the same order key and I want stepLimit extra items.
As I understand it currently queries don't really paginate, the query limit is just continuously increased and any duplicate ids are ignored.
i.e. it queries for 20 items, then 40, 60, 80, etc.
In some cases this can cause a lot of document reads.
Would a PR be welcome that uses the firestore pagination methods Paginate data with query cursors ?
I don't think this would cause an issue,
startAt
requires aorderBy
but so doeslimit
.I was thinking something like:
stepLimit + 1
because I choose to usestartAt
rather thanstartAfter
in case there are multiple items with the same order key and I want stepLimit extra items.The text was updated successfully, but these errors were encountered: