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 the model is in good shape,
deletion rules are what I expect (and I have no "No Action" anywhere).
Moreover, there is absolutely no problem with deletion except in the
given conditions (the remove action that causes the set of displayed
rows to fit in the table).
It's strange, but there you have it... that's what I'm seeing.
I can add and remove the objects in the table without any sign of a
problem until this boundary is involved.
I was _guessing_ that the CoreData error was likely to be the result
of the index out of bounds exceptions in the table binding code. That
might turn out not to be the case of course, but the latter exceptions
do occur before core data complains about not being able to fulfil a
fault (which seems to happen at the next "commitEditing" before a
periodic save). There are absolutely no examples of this error for
the majority of instances of remove (the CoreData faulting error ONLY
seems to occur after the array bounds exceptions has been induced).
-- lwe
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
