Tying up connections in the PaginatedArrayList would not be a desireable functionality to me. I would recommend you write a version of PaginatedArrayList for your own personal use. If you are handling large resultsets I would recommend against the use of PaginatedArrayList anyways. It is meant for small result scrolling.
Brandon On 9/13/05, Corneliu Rudeanu <[EMAIL PROTECTED]> wrote: > > > Hi! > > I made a patch for SQLMapClient which allows reusal of ResultSet's > while iterating through a paginated query list. How can I submit the > patch? > > A more detailed description: the current implementation is re-running > the query when user asks for some page, skipping the results > (resultSet.next()) until the requested page is read. This is a problem > while iterating through large results, and in my opinion that is the > exact purpose for having paginated queries. My patch keeps the > ResultSet cached in the PaginatedList, and invokes next()'s when user > asks for next page. When a page "from the past" (i.e. going to a page > with lower index than current - 1) the query runs again, with a > behaviour similar to current implementation. Note: the optimization > with next+previous pages being cached was kept in my patch. > > I have little experience with SVN. Please send some instructions on how > to submit the patch in order to be evaluated. > > Regards, > Corneliu Rudeanu > > > > > ______________________________________________________ > Yahoo! for Good > Donate to the Hurricane Katrina relief effort. > http://store.yahoo.com/redcross-donate3/ > >
