> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of James Cook > Sent: Friday, July 23, 2004 3:36 PM > To: [EMAIL PROTECTED] > Subject: RE: [displaytag-devel] Access to ResultSet when > using paged results > > > If the results aren't stored in the session, you are saying > that each page navigation results in another query against > the database?
It depends on how you configure your JSP. You can configure it to pull the list from the session if you like. It's the developer's choice. > > If they are stored in the session (which seems like the > logical choice for everything but very, very large results), > then there's certainly an attribute name that I can look them > up by. I suppose I could also leverage the SmartListHelper > class to narrow down the rows that will be displayed as long > as the results are sorted correctly. Yeah, the displaytag has performance issues with large resultsets (as expected). I'd recommend the Value List Handler if they're really that big (http://valuelist.sf.net). Of course, limiting your queries is probably a good option too. Hopefully someday we can add something that will allow you to grab the first/last parameters from the request. If I were you, I'd make sure you add what you're looking for to the bug tracker. Fabrizio does most of the work on this tag b/c it's his architecture. I'm hesitant about digging in and fixing bugs b/c I'm afraid I'll break something - and it'd probably take me a few hours/days to dig in and understand everything. Matt > > > > -----Original Message----- > > From: [EMAIL PROTECTED] > [mailto:displaytag- > > [EMAIL PROTECTED] On Behalf Of Matt Raible > > Sent: Friday, July 23, 2004 2:54 PM > > To: [EMAIL PROTECTED] > > Subject: Re: [displaytag-devel] Access to ResultSet when > using paged > > results > > > > > > On Jul 23, 2004, at 12:02 PM, James Cook wrote: > > > > > Sorry, I just realized I have been posting this user > comment to the > > > development list. > > > > > > Just to finish it up... > > > > > > I could dig into the source to find out what session > attribute the > > > result set is stored under, and what row is currently being > > > displayed, and how many > > > rows will be rendered, etc. > > > > What source? The display tag's? AFAIK, there is no > session attribute > > created by the displaytag. It just uses some funky > algorithm based on > > a parameter passed in. You could likely re-use the "decryption" > > algorithm for that parameter and get the information you're looking > > for. > > > > Matt > > > > > > > > ------------------------------------------------------- > > 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=4721&alloc_id=10040&op=click > > _______________________________________________ > > displaytag-devel mailing list [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/displaytag-devel > > > > > ------------------------------------------------------- > 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=4721&alloc_id=10040&op=click > _______________________________________________ > displaytag-devel mailing list [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/displaytag-devel > ------------------------------------------------------- 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=4721&alloc_id=10040&op=click _______________________________________________ displaytag-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/displaytag-devel
