On Mar 24, 2009, at 01:56, Luke Evans wrote:
Mmm... well, I'm coming around to the idea that something about my
model might be getting screwed before the index out of range
exceptions (though these still happen under the specific conditions
noted).
The "boundary condition" you referred to
Mmm... well, I'm coming around to the idea that something about my
model might be getting screwed before the index out of range
exceptions (though these still happen under the specific conditions
noted).
However, I can reproduce the Core Data fault error when the managed
objects in the tabl
Did you try googling the CoreData error message you pasted? One
result comes from this very list's archives:
Check your Managed Object Model. You most likely have a relationship
problem. Specifically, scrutinize your deletion rules on all
relationships.
Thanks. Well, as far as I can tell
On Mar 23, 2009, at 7:52 PM, Luke Evans wrote:
*** -[NSCFArray objectAtIndex:]: index (8) beyond bounds (8)
2009-03-23 16:17:46.118 App[17940:817] *** -[NSCFArray
objectAtIndex:]: index (8) beyond bounds (8)
2009-03-23 16:17:46.132 App[17940:817] CoreData could not fulfill a
fault for '0x1a5
I have a table bound to an NSArrayController that provides content
from Core Data.
This has been pretty trouble-free except that the hook up that removes
the selected object/row (currently a 'minus' button under the table
that uses the "remove" action on the controller) appears to cause an
