A number of data providers to egGrid don't currently report on the total result set size. For example, the patron search API accepts a limit and offset and returns a set of records, but the underlying database query doesn't return the total number of hits. It would be possible to have it first count, then return the records in the selected window, but the usability improvement from doing that would have to be balanced against the cost of the additional database query.
Agreed that it would be useful.
A number of data providers to egGrid don't currently report on the total result set size. For example, the patron search API accepts a limit and offset and returns a set of records, but the underlying database query doesn't return the total number of hits. It would be possible to have it first count, then return the records in the selected window, but the usability improvement from doing that would have to be balanced against the cost of the additional database query.