|
|
If I need the entire resultset in the memory what would be the best
approach? It seems that broker.getCollectionByQuery(q) stuck with huge
records.
On Tue, 12 Oct 2004 16:09:11 -0400, WHIRLYCOTT <phil@xxxxxxxxxxxxxx> wrote:
> You probably are doing something like this:
>
> Collection c = broker.getCollectionByQuery(q);
>
> ... and ought to be doing something like this:
>
> Iterator i = broker.getIteratorByQuery(q);
>
> Unless you need the entire result set in memory, this should be your
> preferred approach. Just iterate through the results and do what you
> need to do to each of them.
>
> phil.
>
> [ Muliawan Sjarif ] wrote:
>
> > Hi,
> >
> > I was doing a quick test for OJB particularly using PersistenceBroker
> > on one table that consists of 352544 records. No matter how many times
> > I tried, in the end all I got was the browser not responding (no
> > result displayed on the page) and tomcat throwed java.lang.OutOfMemory
> > exception. For this test, dynamic proxy was utilized.
> >
> > Pertaining to this problem, I wonder if anyone has encountered similar
> > problem. Or is there somewhere in the OJB's properties that need to be
> > tweaked?
> >
> > Many thanks.
> >
> > Regards,
> > Muliawan
>
> --
> Whirlycott
> Philip Jacob
> phil@xxxxxxxxxxxxxx
> http://www.whirlycott.com/phil/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ojb-user-unsubscribe@xxxxxxxxxxxxx
> For additional commands, e-mail: ojb-user-help@xxxxxxxxxxxxx
>
>
--
"It is your attitude, and not your aptitude, that determines your altitude"
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-user-unsubscribe@xxxxxxxxxxxxx
For additional commands, e-mail: ojb-user-help@xxxxxxxxxxxxx
|
|