You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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();
The text was updated successfully, but these errors were encountered:
Currently there is:
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:
The text was updated successfully, but these errors were encountered: