Re: java.lang.OutOfMemoryError with WODisplayGroup
Re: java.lang.OutOfMemoryError with WODisplayGroup
- Subject: Re: java.lang.OutOfMemoryError with WODisplayGroup
- From: Denis Stanton <email@hidden>
- Date: Fri, 10 Oct 2003 09:28:53 +1300
Hi Jonathan
On Friday, October 10, 2003, at 04:41 AM, email@hidden
wrote:
Even though you said we dont' need to explain the fallacy, I'm going to
provide a few tips anyway, cause I think it'll help us come up with a
solution. ........... if you decide you need this, ask and I or
someone else will explain some ways to do it.
thanks for your interest. I had wondered a bit about the possibility
that WO/EOF could have implemented display group batches in a way that
didn't require the whole table in memory at once. I'm not familiar
with TOP in SQL but I rather assumed there was a way to set the maximum
number of rows to be returned. It gets tricky when there is a sort
sequence involved, or as you point out, some other selection criteria.
In my case all I wanted to do was inspect some representative values in
the old table. My users won't look here, so they won't have to scroll
through 300 batches. My initial need was to be able to see a few
records so that I could check that my import was working. That has now
been accomplished. If I need to go further I will just have to put an
intelligent selection section onto the page.
Denis
Denis Stanton
email@hidden
Home: (09) 533 0391
mobile: 021 1433622
_______________________________________________
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.