Open RonnenPodolsky opened 1 year ago
@RonnenPodolsky I'm with you 100% on this one. I'm trying to use this from the backend with Node. At the very least .select()
should give us the full response, not limit to just records and the effectively-useless-outside-of-the-browser fetchNextPage
. We might need to fork this repo and make it more Node.js friendly.
there is no offset in what .select() returns like in curl. .all() returns all records, i saw use cases for .eachPage() returning all pages just doing something async with every page. Is there no way to get specific page of results? let's say i have a table with 1200 records and pageSize is 100, i want to create pagination of scrolling where each time you get 100 more - why is there no way to get 101-200, 201-300? How do I use fetchNextPage in this scenario for every new request remembering the last page without an offset value that is not availble here? HOW CAN THIS BE DONE?! please I've been looking at these for days.