On Mar 1, 2012, at 7:12 AM, Eric Giguere wrote: > I'm on the verge of loosing my sanity...
> I've been hitting this error for a long time now. > If I try deleting the C object before saving the new stuff, I get this error: > Domain=NSCocoaErrorDomain Code=134030 "The operation couldn’t be completed. > (Cocoa error 134030.) NSUnderlyingException = "Cannot update object that was > never inserted."; > > And if I save, then delete then save again I get back to the > NSObjectInaccessibleException. Take a deep breath and get a good nights sleep. Hillegass suggests 10 hours of sleep may be needed when learning a new topic. Generally it has been my experience with error messages that the frameworks are trying to tell you something. Often after the problem is solved the error message completely makes sense. Here are few links you could try. http://stackoverflow.com/questions/7109880/core-data-unresolved-error-on-save http://stackoverflow.com/questions/5591301/coredata-nsobjectinaccessibleexception-coredata-could-not-fulfill-a-fault > It does not make sense that such a library fails with such a trivial case. So far it has been my experience that Core Data works as advertised except for one case I found where the documentation was not updated and the actual functionality was more than advertised. I also learned the hard way that Core Data has a steep learning curve and required a lot of effort to understand what was going on. --Richard _______________________________________________ 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
