Check out http://www.mail-archive.com/displaytag-user%40lists.sourceforge.net/msg00849.html
On Wed, 2004-02-18 at 21:39, Adam Murray wrote: > Due to performance problems with DB queries that return large data sets > (10s of thousands), I need to switch over to lazy/pagination-aware > retrieval (i.e. I would only retrieve exactly the data I'm going to > display on a page). I'm wondering if I can somehow continue using > displaytag pagination. > > Say I'm dealing with a set of 50,000 elements, but I know I'm only > displaying 250 elements at once, so that's all I retrieve from the DB. > Displaytag expects a list of *all* the objects you are going to display > on the table, so it isn't going to know that there's really more than > 250 elements and I lose all the nice pagination features. I see two > workarounds: > 1) implement my own pagination > 2) wrap a list proxy around my data to somehow trick displaytag into > thinking the full dataset is in the list (not sure how/if this would > work, I'd have to examine the displaytag source). The list proxy could > even handle querying the DB when more items are needed for display. > > I'm wondering if there's a existing fix to this problem, or a better way > to go about solving it. It seems like a problem many other people must > have had to deal with, so I'm guessing there's a good solution. ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ displaytag-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/displaytag-user
