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

ENH: Support findPagingList() ... that uses firstRow & maxRows (rather than pageIndex, pageSize) #494

Closed
rbygrave opened this issue Dec 9, 2015 · 0 comments
Assignees
Milestone

Comments

@rbygrave
Copy link
Member

rbygrave commented Dec 9, 2015

Currently there is:

query.findPagingList(pageIndex, pageSize)

This is ok but there is a desire/need to support using firstRow, maxRows instead. For example, in the case of continuous scrolling/paging ... the first 50 rows are fetched and then 20 rows after that as the user scrolls the UI (so maxRows is different from the first request to subsequent requests).

This enhancement will add support for writing:

// so this findPagingList() method with no arguments implies that 
// the firstRow and maxRows has been set on the query.

PagedList<..> pagedList = 
  query.where()
  ...
  .setFirstRow(50)
  .setMaxRows(20)
  .findPagingList();
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant