Re: Fetching objects 1 by 1
Re: Fetching objects 1 by 1
- Subject: Re: Fetching objects 1 by 1
- From: Chuck Hill <email@hidden>
- Date: Mon, 22 Mar 2010 14:55:48 -0700
You could fetch them in batches like ERXBatchingDisplayGroup does.
That uses a LIMIT fetch, so you would need to be sure that objects
don't get inserted during processing that affect previously processed
batches. Otherwise... JDBC or low, low level EOF it is.
Chuck
On Mar 22, 2010, at 2:47 PM, Lon Varscsak wrote:
I was trying to keep the memory footprint as small as possible and
fetching all of the PKs seemed to be "too much". I'm thinking more
along the lines of when you'd fetch stuff directly from JDBC and
just process one result at a time after having executed a sql
statement.
-Lon
On Mon, Mar 22, 2010 at 2:42 PM, Chuck Hill <chill@global-
village.net> wrote:
On Mar 22, 2010, at 2:23 PM, Lon Varscsak wrote:
I have a bunch of rows I need to do processing on and it would be
create to fetch EOs one by one from the result set instead of all of
them at once. I know this is possible at the EOAccess level, but I
didn't know if there was a better/simpler way to do it (including
something in WOnder).
Any thoughts?
Fetch the PK as raw rows and then make faults from them one by one?
Is that what you are after?
Chuck
--
Chuck Hill Senior Consultant / VP Development
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
--
Chuck Hill Senior Consultant / VP Development
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden