AFAIK - cached row set has a limitation of 3-hundred records.
One potential way around the problem is to count the sum of all the
records then read up as many records as your willing and when you start
to near the end of the set go back to the database.
I'm sure if there's a better way someone on the list will chime in.
----- Original Message -----
From: Mailing Lists <[EMAIL PROTECTED]>
Date: Friday, March 23, 2001 11:06 am
Subject: Re: Paging through result sets
> between 300-500 rows, 20 + columns
>
> > -----Original Message-----
> > From: A mailing list for discussion about Sun Microsystem's Java
> Servlet> API Technology. [mailto:[EMAIL PROTECTED]]On
> Behalf Of T A
> > Flores
> > Sent: 23 March 2001 18:11
> > To: [EMAIL PROTECTED]
> > Subject: Re: Paging through result sets
> >
> >
> > How large of a resultSet are you talking about?
> >
> > ----- Original Message -----
> > From: Mailing Lists <[EMAIL PROTECTED]>
> > Date: Friday, March 23, 2001 9:41 am
> > Subject: Re: Paging through result sets
> >
> > > I have looked at the info at the link you gave and the technique
> > > they show
> > > is to use a cached rowset that reads all the data in from a given
> > > query (I
> > > described this in option 2 of my original posting). They state
> > > that the
> > > cached rowset is "not suitable for very large data sets". Ie. all
> > > the data
> > > is read in from the query.
> > >
> > > My original question still stands: what other techniques have you
> > > used to
> > > implement paging strategies?
> > >
> > > By the way, I cannot find the CachedRowset object anywhere in the
> > > java.sqlnor javax.sql packages - where is it?
> > >
> > > Myles
> > >
> > > > -----Original Message-----
> > > > From: A mailing list for discussion about Sun Microsystem's Java
> > > Servlet> API Technology. [mailto:[EMAIL PROTECTED]]On
> > > Behalf Of T A
> > > > Flores
> > > > Sent: 23 March 2001 17:07
> > > > To: [EMAIL PROTECTED]
> > > > Subject: Re: Paging through result sets
> > > >
> > > >
> > > > Why not take a look at the information available at the
> > > following link?
> > > >
> > > >
> > >
> >
>
http://developer.java.sun.com/developer/Books/JDBCTutorial/chapter5.html
> >
> > > > ----- Original Message -----
> > > > From: Mailing Lists <[EMAIL PROTECTED]>
> > > > Date: Friday, March 23, 2001 8:35 am
> > > > Subject: Paging through result sets
> > > >
> > > > > Hi,
> > > > >
> > > > > I am interested to hear what your approaches have been to
> paging> > > > throughquery result sets using a 'next'/'previous'
> hotlink> > > > mechanism from the
> > > > > browser. I have listed a few strategies below:
> > > > >
> > > > > 1) Retain a database connection per-user to page through
> the query
> > > > > resultsusing JDBC 2.0 cursor functionality. Major
> downside is
> > > > > that connection is
> > > > > used soley for given client.
> > > > > 2) Read all the results in from the database and cache in the
> > > > > server - only
> > > > > give out those results that the user is currently looking at.
> > > > > Downside is
> > > > > that the results are stored in the server for as long as
> the user
> > > > > is looking
> > > > > at them, taking up memory.
> > > > > 3) Read all the results in to a temporary table in the
> > > database, then
> > > > > returning only the subset of results that the user is
> currently> > > > looking at.
> > > > > Downside is that the database will fill up with result
> data - will
> > > > > need a
> > > > > process to clean up this data regularly.
> > > > > 4) Rerun the query against the database each time the user
> looks> > > > at a given
> > > > > subset of results. Downside is that the query must be
> rerun and
> > > > > that the
> > > > > results may change between execution (though fine for static
> > > data).> >
> > > > > Myles
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
