Andy, iBatis has the queryForPaginatedList() to handle this situation. Check the iBatis documentation.
queryForPaginatedList(): This very useful method returns a list that can manage a subset of data that can be navigated forward and back. This is commonly used in implementing user interfaces that only display a subset of all of the available records returned from a query. An example familiar to most would be a web search engine that finds 10,000 hits, but only displays 100 at a time. The PaginatedList interface includes methods for navigating through pages (nextPage(), previousPage(), gotoPage()) and also checking the status of the page (isFirstPage(), isMiddlePage(), isLastPage(), isNextPageAvailable(), isPreviousPageAvailable(), getPageIndex(), getPageSize()). Although the total number of records available is not accessible from the PaginatedList interface, this should be easily accomplished by simply executing a second statement that counts the expected results. Too much overhead would be associated with the PaginatedList otherwise. Regards, Richard --- Andy Engle <[EMAIL PROTECTED]> wrote: > Hi all, > > I am wondering if anybody has ever worked with a > huge amount of data > with iBatis and displaytag? I was showing off my > little Struts > application earlier to a buddy of mine here at work, > and he asked if it > would work well with 10,000 rows x 20-40 columns. > Anybody ever worked > with that much data with iBatis/displaytag before? > If so, how did it > work out for you? > > > Thanks, > Andy > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: > [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] > __________________________________ Do you Yahoo!? Yahoo! Search - Find what you’re looking for faster http://search.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
