What I'm doing for paging my search results is an intensive use of methods Query.setStartAtIndex() and Query.setEndAtIndex() to get only portions of the results. Maybe you could check out them...
Thomas
At 22:05 21/07/2003, you wrote:
Hi, all,
My project has potentially huge result sets, so there is a question to use OJB.
Suppose a query returns thousands of objects, but the results are always presented in page to page navigation. How do I use OJB efficiently for this scenario?
FAQ mentions using getIteratorByQuery() to lazy materialize objects one by one. However, loading one object at a time is also poor in performance. Ideally, all the objects for the current page are loaded at one time, no more and no less. Do we have a way to configure the getIteratorByQuery() so to specify the beginning row number and total record number to load? If not, can I suggest it to be added next release?
Thank you for your insights.
Bill Zhao
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
