• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: java.lang.OutOfMemoryError with WODisplayGroup
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: java.lang.OutOfMemoryError with WODisplayGroup


  • Subject: Re: java.lang.OutOfMemoryError with WODisplayGroup
  • From: Denis Stanton <email@hidden>
  • Date: Thu, 9 Oct 2003 15:21:16 +1300

Hi Art

thanks for clarifying my woolly thinking on this

On Thursday, October 9, 2003, at 02:10  PM, Art Isbell wrote:

... There's no batching capability in SQL as far as I know, so EOF behaves like SQL in this respect.

I guess what I was hoping for (without really reasoning it out) was that the DisplayGroup would automatically figure out the SQL required to fetch only the records required to display the current batch. You don't need to explain the fallacy in this, I'm getting it.


Is it really the case that a WODisplayGroup runs out of memory handling a table of between 3 and 6 thousand records?

Nope, the JVM does.

Fair enough

I guess the bottom line is that a Web application is generally used by humans. Humans don't process thousands of objects very well. So it's usually best to somehow limit the number of objects fetched rather than to try to deal with a huge number of objects. Maybe there's some sort of qualifier you can use to limit the number of objects fetched. That would seem to be the preferable solution rather than increasing the

From a simple-minded user point of view, that's what the batch controls on the web page appear to be doing. They limit the amount of data being presented to the human. As you have explained, they don't limited the amount of data being presented to / handled by the WebObjects App.


Darn

In my application it looks like the simple work-around is going to be to display the alphabet A-Z across the page and ask the user to select one letter at a time, where that letter will be matched against some characteristic that is spread across the file. Probably the first letter of the customer name will be enough to break the file into chunks. This screen was only going to be used on rare occasions to locate historic information. I'm going to have to provide some alternative search methods, rather than just a batched list with multiple sorts, as I hoped.

Thanks for your time

Denis
_______________________________________________
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.

  • Follow-Ups:
    • Re: java.lang.OutOfMemoryError with WODisplayGroup
      • From: Chuck Hill <email@hidden>
References: 
 >Re: java.lang.OutOfMemoryError with WODisplayGroup (From: Art Isbell <email@hidden>)

  • Prev by Date: Re: java.lang.OutOfMemoryError with WODisplayGroup
  • Next by Date: Re: java.lang.OutOfMemoryError with WODisplayGroup
  • Previous by thread: Re: java.lang.OutOfMemoryError with WODisplayGroup
  • Next by thread: Re: java.lang.OutOfMemoryError with WODisplayGroup
  • Index(es):
    • Date
    • Thread