[DocumentDB] Allow Paging (skip/take)
Allowing paging would be huge. Btw, Thank You for rolling out this feature at all! It looks wonderful! Can't wait to try it! However, I won't be able to use it for actual work projects until it supports paging and sorting.
Support for SKIP is under review; we will provide an update once we have a confirmed schedule. As previously announced, TOP is supported, and the LINQ provider supports TAKE.
It's been 3.25 years. How long does it take to implement this? We want to switch from RavenDB, but CosmosDB just has too many limitations.
Rob Teixeira commented
Seriously? Still no update to this in over a year? Lack of Skip just torpedoed Cosmos DB for my project. Back to SQL Azure...
Justin Staffer commented
Skip is a big deal for us. LINQ is too slow and we would need to pull a ton of data. Please correct me if I'm wrong.
william lee commented
Will you tell us where you guys are on this? thanks much
Bryce Godfrey commented
Not only skip/take but also the total count in the result set would be beneficial. The example of a list of records where I need to show the total count and let the user page through them.
Now that the Microsoft Build event has ended, can we get an update on this?
Sibin S commented
Its been 3 years :) Common this would be a great addition to it.
Where is this at? What are we supposed to do until this point? Pull the entire data set back and page it in code?
WE NEED THIS NOW! GET IT DONE.
Steve Haran commented
Really need to implement paging - it seems like the most basic of requirements. Please - any updates?
Why is this taking so long? This has been kicking around for ages now.
Question: What is the utility of DocDb if you can't page through results in large datasets?
Any ETA or Update, DoumentDB is a great product. Although without proper paging support (Page forward and Back, get specific page etc) its use in web applications is limited.
So, how far is this?
The link by Henrik Ebbeskog shows how to iterate, but not how to page. (Paging is when the user can go to the previous or next page in a view.)
Furthermore, for a collection to use min/max requires some unique sortable property, which many collections don't have.
(Many have either unique or sortable, but not both.)
Hey folks, this has been in the planned state for almost a year now. Can we please get an update on what that means? Our teams are using DocumentDB in a limited capacity right now and having this feature would be a significant win. I know there are alternatives, but they are messy at best compared to a clean skip implementation. - M@
Amit Chaudhary commented
Any update on the support for advance paging via skip/take?
Henrik Ebbeskog commented
Michael Rajesh commented
skip/take? Currently you can go with TOP at select and use WHERE with c._ts and an ID field (/ what you use in ORDER BY) of the previous page least or maximum values..
really needs to work with partitions too
Ian Moores commented
Any update on this??