Re: Fetching objects 1 by 1
Re: Fetching objects 1 by 1
- Subject: Re: Fetching objects 1 by 1
- From: Miguel Arroz <email@hidden>
- Date: Mon, 22 Mar 2010 21:59:49 +0000
Hi!
If you can separate between already processed objects and objects yet to be processed by using the same query you use to fetch the objects, you can set a balance point between performance (ie, number of DB hits) and memory footprint, by fetching a batch (of, say, 100 objects) at a time and process them, and repeat this until there's no further objects to process.
Yours
Miguel Arroz
On 2010/03/22, at 21:23, 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?
>
> Thanks,
>
> Lon
> _______________________________________________
> 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
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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