PostgreSQL has a nifty bit of functionality for bringing back just pieces of a result set. You could build something around this functionality.
I think the pieces of the SELECT you want are: LIMIT START COUNT Check out their web site. Regards, Eddie (There are other DBMSs that provide this functionality too. Of course, using something like Jakarta OJB, you could use proxy objects which would only contain keys and materialize the full objects as you need them. For a very large result set, however, it may be wiser to go "database-dependant". Testing both approaches in your application would be the only way I'm aware of to determine which suits your needs the best) Bryan Hilterbrand wrote: >There are many potential solutions to this, but one is to figure out what >the end result of iterating through your result set is, then create a stored >procedure to do the same thing. > >Bryan > >----- Original Message ----- >From: "Michael Lee" <[EMAIL PROTECTED]> >To: "Struts Users Mailing List" <[EMAIL PROTECTED]> >Sent: Friday, September 06, 2002 9:42 AM >Subject: Re: [FRIDAY] Out of control ... again [OT] [HELP] [LOTS OF POSTINGS >LITTLE HELP] > > >Hey, do any of you [FRIDAY] guys know how to handle iterating through >enourmously large result sets without storing the ResultSet object in >memory? I use JDBC cursors now but have to do the query upon each 'next' or >'previous'. > >I always ask the tough questions that get few responses! >:) >Mike Lee > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
