Re: Core Data dog-slow when using first time after boot
Re: Core Data dog-slow when using first time after boot
- Subject: Re: Core Data dog-slow when using first time after boot
- From: Ben Trumbull <email@hidden>
- Date: Mon, 24 Aug 2009 14:13:41 -0700
On Aug 24, 2009, at 3:20 AM, Ruotger Skupin wrote:
Am 20.08.2009 um 22:28 schrieb Ben Trumbull:
setRelationshipKeyPathsForPrefetching
When I use setRelationshipKeyPathsForPrefetching the fetch throws:
-[NSSQLAttribute inverseRelationship]: unrecognized selector sent to
instance 0x10ee150
Can you provide the entire stack trace at this point ? gdb use future-
break objc_exception_throw
For the record: I do use one-way relationships
That should be okay as long as you're not pretending to use a no
inverse to-many relationship as a de facto many to many relationship.
No inverse relationships can only behave as if the inverse were to-
one. Specifically, each row in the destination entity may only be
associated with a single row in the source entity if the relationship
on the source entity does not have an inverse. (e.g. you only get
join tables in fully modeled bi-directional relationships)
Since it's not a many to many, you can perform the prefetching
effectively by hand using a fetch request to preload the relevant
destination rows with an IN query based on the data you initially
fetched for the source entity. You shouldn't have to, but if you've
run into a bug, that's how you could workaround it.
You still haven't described the NSPredicate you were using with
filteredArrayUsingPredicate. Being more forthcoming about the context
and details of your problem will help us get you answers more quickly.
- Ben
_______________________________________________
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