Using LIMIT OFFSET for paging cursor results

[chauhan-abhi]

⚠️ Please describe your feature request

Is it like we are always fetching all records and then moving the cursor to our page limit and offset in the library..
Why are we not fetching only that many records using LIMIT and OFFSET?

💡 Describe the solution you'd like

📊 Describe alternatives you've considered

📄 Additional context

🙋 Do you want to develop this feature yourself?

• Yes
• No

[bojankoma]

@chauhan-abhi Hi, thank you for opening this issue and asking a very tricky question. :)
In short, a cursor implementation has been chosen over offset pagination in order to optimize for large data sets.
I can see that the logger showing SELECT * messages in console has been very misleading, so I will remove it in following release. Furthermore, this cursor implementation just creates a pointer to exact position and reads N fields from it, in comparison with offset pagination where you actually read rows and then truncate the output.

For more details about different pagination approaches, you can go here on this excellent Slack blog post.

Nevertheless, if you think a different approach would be a better one, a PR is most welcome and we can discuss it further.