There are lots of ways to solve the problem via caching of results
(either entire entities, ids, proxy objects that allow you to load by
id, etc), depending upon your tolerance for potential inaccuracy in
the page count. The reality for most tables, where the query isn't
that complex, is that iss
I am not sure if this is considered kosher . . .
The ITablePagingState and ITableSortingState will be up to date prior to
rendering - they encapsulate all of the data passed into the
getCurrentPageRows() method. I could provide these object directly to
my custom IBasicTableModel - it will invoke
