We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
1 parent 1839934 commit 4795264Copy full SHA for 4795264
website/pages/docs/cursor-based-pagination.mdx
@@ -285,7 +285,7 @@ datasets.
285
286
The above is just an example to aid understanding; in a production application,
287
for most databases it is better to use `WHERE` clauses to implement cursor
288
-pagination rather than using `OFFSET`. Using `WHERE` can leverage indicies
+pagination rather than using `OFFSET`. Using `WHERE` can leverage indices
289
(indexes) to jump directly to the relevant records, whereas `OFFSET` typically
290
must scan over and discard that number of records. When paginating very large
291
datasets, `OFFSET` can become more expensive as the value grows, whereas using
0 commit comments