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
Currently, we include the element at KeysetScrollPosition in the query via gte/lte. Using these operators with non-unique keys (e.g. firstName=John, age=41, id=1, firstName=John, age=41, id=2) with a query (firstName > John || firstName == John && age >= 41) includes potential duplicates that we're not able to remove from the final result.
We should resort to gt/lt instead of gte/lte.
The text was updated successfully, but these errors were encountered:
Currently, we include the element at
KeysetScrollPosition
in the query viagte
/lte
. Using these operators with non-unique keys (e.g.firstName=John, age=41, id=1
,firstName=John, age=41, id=2
) with a query(firstName > John || firstName == John && age >= 41)
includes potential duplicates that we're not able to remove from the final result.We should resort to
gt
/lt
instead ofgte
/lte
.The text was updated successfully, but these errors were encountered: