Hi Cory, Thanks for contributing. There's a couple of proposed patches already on this topic. See
http://sourceforge.net/tracker/index.php?func=detail&aid=1013526&group_id=73068&atid=536616 and https://sourceforge.net/tracker/index.php?func=detail&aid=872183&group_id=73068&atid=536616 for example. None address sorting. The primary developers have been discussing making this feature a priority for release 1.1, most likely involving refactoring of the paging/sorting modules. You might want to scan some of the discussion on this topic. WILL ----- Original Message ----- From: "Cory Hubert" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Saturday, August 28, 2004 5:07 AM Subject: [displaytag-user] Resolution to using displaytag with Large RecordSets > The problem with using large recordsets is when you click next or > previous it goes through the entire collection to find the start and > end index of the page it's about to display. > > Maybe it was done this way to help support the sorting functionality. > If you have sorting enabled it will sort your results across all the > pages. Obviously this is bad if you have a huge collection. > > Attached is some code that a fellow coder I work with put together. > If you put the elements in your collection in the PaginatedList it > will take care of giving display tag the start and end index only for > that page. > > Unfortunately you cannot have sortable columns with this solution. > > I would recommend adding this into the displaytag source code. > ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click _______________________________________________ displaytag-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/displaytag-user
