Re: NSDictionary and FetchSpecificationNamed usage
Re: NSDictionary and FetchSpecificationNamed usage
- Subject: Re: NSDictionary and FetchSpecificationNamed usage
- From: Chuck Hill <email@hidden>
- Date: Wed, 19 Oct 2005 15:13:37 -0700
On Oct 19, 2005, at 2:44 PM, Arturo Perez wrote:
<snip>
I don't fully understand what you're doing. But if you have a
path from your Provision object to your Item object you can
write a fetchspec that acts something like
Provision.orders.items.quantity = 0
that will get all the Provisions that include unfulfilled items.
I don't think that will work against the database, only in
memory. You can still use it in a qualifier to filter an NSArray
in memory. Pierre Bernard has a number of qualifier extensions
that provide more advanced SQL generation on his page:
http://homepage.mac.com/i_love_my/code.html
I _think_ that ExistsInRelationshipQualifier is what you need.
A big THANKS! to Pierre for all these useful qualifiers. Highly
recommended!
Chuck
I thought if you used the FetchSpec editor in EOModeller you could
create the above? I did not mean to imply that using
qualifierWithFormat (or whatever it is) can do it. My bad. I
never use that.
Well, I never use the EOModller thingy. In either case, the
EOQualfiier generated is the same. Unless it has changed and I
failed to notice it (possible), qualifiers across a to-many
relationship don't generate correct SQL.
Chuck
--
Coming in 2006 - an introduction to web applications using WebObjects
and Xcode http://www.global-village.net/wointro
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