+1
Phew, somebody got to this. I'm not touching on generic pagination objects until this is done. :P
Ok, I'll help do it if need be. I've dug into that part of the framework lots by now.
Just FYI, I coded a somewhat similar entity framework in PHP last year, and it does have
provisions for SQL "Limit" (ranges). Yeah, it's mainly used for pagination, nothing else, I believe.
Jonathon
Leon Torres wrote:
Hi folks,
I think we really need to be able to specify the size of the list we
want and the index to start at for the GenericDelegator.findByAnd and
findByCondition methods.
The idea is to support pagination in the form widgets and similar
systems for lists of data that cannot be supported by <view-entity>.
For example, if the inventory QOH and ATP are required for a form-widget
list, we need to call the getInventoryAvailableByFacility service and
add the results to each list row. Another example would be a union of
various entities together, some of which need heuristics to select the
data.
It should be relatively simple: Create a method that wraps a call to
findListIteratorByCondition, then grab the desired range of results. It
should also return the size of the table.
Then, as an example, we can call these methods with our viewSize and
viewIndex parameters, build our complex list of data based on the
results, and use the form-widget's override-list-size to make pagination
work with it.
Thoughts?
- Leon
