Re: CoreData: Using to-may relationships in fetch request predicates
Re: CoreData: Using to-may relationships in fetch request predicates
- Subject: Re: CoreData: Using to-may relationships in fetch request predicates
- From: Frank Illenberger <email@hidden>
- Date: Fri, 21 Aug 2009 18:10:57 +0200
Am 21.08.2009 um 17:49 schrieb I. Savant:
On Aug 21, 2009, at 11:31 AM, Frank Illenberger wrote:
Yes, I am using an sqlite store, but I tried it with the other
store types and it did not work either. What would a working
predicate look like for other store types?
I didn't catch this at first, but you said you're fetching
employees where "employee.salary ...". If the target entity for your
fetch is Employee, does Employee really have an attribute named
"employee"? Are you sure you don't mean where "salary ..."?
I am fetching against the Departments entity. I want all departments
whose employees (this is the to-many relationship) fulfill the two
conditions.
Sadly, in-memory filtering is not an option for it has to happen in
a single fetch.
That you said this without explaining why leads me to suspect this
isn't the case. Even if you have a hundred thousand employees, I
can't see how in-memory filtering is "not an option". Please explain.
Believe me. This is for a dynamic, customer extendable reporting
solution where this logic has to fit into a single predicate.
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden