Re: Row restriction in WebObjects?
Re: Row restriction in WebObjects?
- Subject: Re: Row restriction in WebObjects?
- From: Art Isbell <email@hidden>
- Date: Wed, 16 Apr 2003 13:45:34 -1000
On Tuesday, April 15, 2003, at 01:28 PM, Sharon Lui wrote:
Recently we encounter a problem with downloading data from our
WebObjects 5.1 application. The applications hangs whenever it happens
(after we tried to fetch pass, say, 7000 rows). Is there a restriction
on the number of rows fetched in the database or number of rows that
can be displayed through a WORepetition in WO 5.1? Is there a fix in
later versions of WO?
There is no hard-coded fetch limit in EOF or in a WORepetition.
However, you may be running out of Java VM memory. JVM memory can be
increased as outlined in
http://docs.info.apple.com/article2.html?artnum=75496.
But does it really make sense to display 7,000 rows to a user? Humans
can't generally deal with so much information. EOF supports setting a
fetch limit to prevent overlarge fetches from completing.
WODisplayGroup supports displaying fetched objects in batches, but the
displayed objects have already been fetched.
So a better solution might be to limit the number of objects fetched.
Or if possible, fetch small sets of objects, process them, and discard
them before fetching the next set. This would reduce the memory
footprint of the app which is a good thing.
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.