5 ms·
I don’t like the term “cursor-based” pagination. Database cursors are different from this, have been around for decades, and can actually be used to implement p
by branko_d 4y ago
I don’t like the term “cursor-based” pagination. Database cursors are different from this, have been around for decades, and can actually be used to implement pagination (albeit with requiring the transaction to be kept alive between pages which can be… problematic).
Perhaps, “token-based” pagination would be a better term?
- deleted 4y ago[deleted]
- blurker 4y agoI agree. I was unsure if the author meant db cursors which would be keeping transactions alive. That has obvious scaling issues. But reading the comments here has me convinced they are talking about application generated cursors. I think this is a pretty reasonable confusion and it would benefit from added clarity, like naming them differently.
- deleted 4y ago[deleted]
- drdec 4y agoThank you, now I don't need to write this comment
- abraxas 4y agoThis is highly aggravating and confusing when hipsters try to coopt terms that had a defined meaning for decades. The ones that grate me are "retina display", "real time", "x-nanometer node".
- kortex 4y ago> Perhaps, “token-based” pagination would be a better term? Let's do it. When I was first learning about it, I wondered how the concept related to database cursors, if at all. It's really just a pointer to the next item at its most simple. But it really is just any opaque blob. Maybe you want it to be a jwt/encrypted blob with a request counter so you can track request usage by specific accounts (along with the pointer). jk that's probably a terrible idea (too entangled). Idk, just came up with it. Point is, you could do something like that, it's just a blob opaque to the client. So I like "token-based pagination".