Re: Debugging Core Data unresolved keypath save error
Re: Debugging Core Data unresolved keypath save error
- Subject: Re: Debugging Core Data unresolved keypath save error
- From: Jim Correia <email@hidden>
- Date: Tue, 20 Mar 2007 20:15:36 -0400
On Mar 20, 2007, at 6:22 PM, Kevin Hoctor wrote:
It doesn't trace back to my code, but rather the NSDocument
saveToURL:ofType:forSaveOperation:delegate:didSaveSelector:contextInfo
: operation. That's why I'm having so much trouble debugging it. If
it started with my stuff, I'd probably be able to understand it,
but in this case I don't know the wiring for Core Data well enough
to help me figure out this problem. Here's a full stack trace:
[...]
#12 0x9383d5d8 in -[NSTreeController(NSManagedController)
_performFetchWithRequest:merge:error:]
#13 0x937e8106 in -[NSObjectController(NSManagedController)
fetchWithRequest:merge:error:]
#14 0x937e8fe0 in -[_NSManagedProxy _storesDidChange:]
An NSTreeController is fetching on your behalf.
As a next step, make sure that any tree controllers bound through
this context have valid (i.e. defined, and persistent properties) key
paths for child, count and leaf, and that the predicate is also correct.
Jim
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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