Cursor Pagination
A pagination approach that marks the continuation position with an opaque cursor; compared with offset/limit pagination, it is more stable when data changes dynamically and is suited to large result sets.
Timeline (last 90 days)
Cursor pagination uses an opaque cursor to mark the end position of the previous page, distinct from offset/limit or page-number-based pagination.
Cursor pagination uses the next_cursor returned by the server to precisely locate the continuation position, is more stable when data changes dynamically, and usually has better query performance, making it especially suitable for large result sets.
Cursors generally can only advance sequentially and cannot jump to arbitrary pages, and cursors usually cannot be cached long-term or reused across sessions.
When the data corresponding to a cursor is deleted, some implementations return an error rather than an empty result.
Batch list APIs typically use cursor-based pagination rather than offset-based pagination, because offset-based pagination has performance issues with large data volumes.
All Facts (5)
Cursor pagination uses an opaque cursor to mark the end position of the previous page, distinct from offset/limit or page-number-based pagination.
50%UnverifiedCursor pagination uses the next_cursor returned by the server to precisely locate the continuation position, is more stable when data changes dynamically, and usually has better query performance, making it especially suitable for large result sets.
50%UnverifiedCursors generally can only advance sequentially and cannot jump to arbitrary pages, and cursors usually cannot be cached long-term or reused across sessions.
50%UnverifiedWhen the data corresponding to a cursor is deleted, some implementations return an error rather than an empty result.
50%UnverifiedBatch list APIs typically use cursor-based pagination rather than offset-based pagination, because offset-based pagination has performance issues with large data volumes.
50%