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 13:23:25 -0400
On Mar 20, 2007, at 12:14 PM, Kevin Hoctor wrote:
#0 0x90a63365 in objc_exception_throw
#1 0x93cd01bb in -[NSSQLGenerator
appendClause:forKeyPath:allowToMany:]
#2 0x93ccfca7 in -[NSSQLGenerator _preparePredicateExpression:]
#3 0x93ccfb16 in -[NSSQLGenerator prepareComparisonPredicate:]
#4 0x93ccb57e in -[NSSQLGenerator
prepareSelectStatementWithFetchRequest:]
#5 0x93ccb00f in -[NSSQLAdapter newSelectStatementWithFetchRequest:]
#6 0x93ccae40 in -[NSSQLChannel selectRowsWithFetchRequest:]
#7 0x93d04bc9 in -[NSSQLCore
_newRowsForSelector:withArgument:andLimit:]
#8 0x93cca83b in -[NSSQLCore newRowsForFetchRequest:]
#9 0x93cca4ea in -[NSSQLCore objectsForFetchRequest:inContext:]
I'm still not sure why a save process is failing on building a
predicate. I'd love some feedback on this if anyone has experience
with this kind of error.
What is the complete backtrace, starting with your code?
The next step is to figure out who is generated the fetch request and
the predicate, and to examine them in the debugger and see why the
are referencing keys that aren't part of your persistent model.
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