Re: Fetching Raw Rows
Re: Fetching Raw Rows
- Subject: Re: Fetching Raw Rows
- From: Art Isbell <email@hidden>
- Date: Fri, 25 Apr 2003 10:48:45 -1000
On Friday, April 25, 2003, at 07:17 AM, Jevon Hills wrote:
I have build up my qualifier and can fetch my data as entities, but the
problem is that the query I need to run will normally return between
150,000 and 250,000 objects. This of course causes an out of memory
error. I don't actually need the data as entities, and it seems like
Raw Rows is a good answer for me.
A raw row dictionary will require almost as much memory as an EO, so
you probably won't solve your memory problem by fetching raw rows, but
your fetch performance will likely be much better. If you really need
to fetch that many objects into your WO app, you'll likely need to
increase the maximum size of the Java VM
(http://docs.info.apple.com/article2.html?artnum=75496).
Can someone explain and perhaps provide an example of how to fetch raw
rows and then how to use the fetched data, or is there another way to
deal with such an abundance of information other than raw rows that I
have not considered yet.
It could be much faster to implement some of the processing on the DB
server using stored procedures to avoid fetching everything into the WO
app.
Aloha,
Art
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.