Skip to content

Fix reverse keyset scrolling #4343

Closed
Closed
@mp911de

Description

@mp911de

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.

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions