Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

API extension needed for result limitation and paging #120

Open
RickRainerLudwig opened this issue Jun 23, 2014 · 3 comments
Open

API extension needed for result limitation and paging #120

RickRainerLudwig opened this issue Jun 23, 2014 · 3 comments

Comments

@RickRainerLudwig
Copy link
Contributor

For queries with a large number of potential results a limit setting functionality is needed to limit the number of results. Additionally, a paging functionality would be a benefit.

@CrystalMethod
Copy link
Contributor

I'm not sure if this should be part of the API because most query languages provide support for pagination (skip) and limitation.

@RickRainerLudwig
Copy link
Contributor Author

The query languages may support it, but should we always use the query language to get pagination? It may be user friendly to hide the queries behind a nice API.

Another way could be a wrapper around the iterator and a cache on client site, but with millions of nodes, it is not suitable...

@CrystalMethod
Copy link
Contributor

Could this be an use case for basic repository operations like Springs PagingAndSortingRepository?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants