Re: Behaviour of objectsWithFetchSpecification()
Re: Behaviour of objectsWithFetchSpecification()
- Subject: Re: Behaviour of objectsWithFetchSpecification()
- From: Ken Anderson <email@hidden>
- Date: Thu, 22 Jan 2009 10:52:13 -0500
Nice... one day I'm going to have to get into this Wonder stuff... :)
On Jan 22, 2009, at 10:46 AM, Mike Schrag wrote:
I guess I'm just asking for a sanity check. This can't be an
uncommon use case---what do people do next? Use
EOQualifier.filteredArrayWithQualifier() on the result? Am I
overlooking something basic?
You use ERXFetchSpecification and
setIncludeEditingContextChanges(true). It will automagically
process your results to remove deleted objects and add inserted
objects that would have matched the qualifier you provided (with the
expection of doing things like limits, etc where it wouldn't really
know not to add objects).
ms
_______________________________________________
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
_______________________________________________
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