Comment 2 for bug 1000324

I think the LIMIT clause might actually be harder to code in then paging, if implemented in that manner.

Unless I am reading the code wrong, it looks like TPac currently requests an ordered ID List, then fetches holds from that list in batches (looks like of 8 currently). Which means that it already has access to the total number of holds in an ordered fashion.

The ID List appears to return fairly quickly, the fetching details is (I believe) the bottleneck.

Thus while a limit of 100 to start with could likely be implemented fairly quickly and easily (with knowledge of how many holds there are already there), I think paging could be implemented fairly easily as well by setting the batch index to the first hold of the "page" and adding in a max counter.

Having seen what the code already looks like I might take a shot at it myself.