The approach I take is to limit the number of rows returned and "page the results".
This can be acheived by setting startAt and endAt indexes on the Query object, then you just have to keep track of the page you're on and work out the start and end index depending on how many you'er displaying on each page also means that you don't have to pass iterators etc to the jsp page keeping you're architecture simpler - you just return the 20 long collection of materialised objects HTH Jin ----- Original Message ----- From: "Alexander Prozor" <[EMAIL PROTECTED]> To: "OJB Users List" <[EMAIL PROTECTED]>; "Mykola Ostapchuk" <[EMAIL PROTECTED]> Sent: Wednesday, July 02, 2003 3:39 PM Subject: Re[2]: RsIterator question > Hello Mykola, > > Wednesday, July 2, 2003, 5:27:39 PM, you wrote: > > MO> The main reason I'm using getIteratorByQuery is because my DB table is > MO> pritty big (~100 000 records). Putting all the records into Collection is > MO> too memory expensive. > > MO> I'll very appreciate any help of dealing with big DB tables. > you can use Proxy for your collection. > > > -- > Best regards, > Alexander mailto:[EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
