Re: CoreData faulting - does it rely on #self?
Re: CoreData faulting - does it rely on #self?
- Subject: Re: CoreData faulting - does it rely on #self?
- From: mmalcolm crawford <email@hidden>
- Date: Fri, 14 Apr 2006 14:23:49 -0700
On Apr 14, 2006, at 1:35 PM, Todd Blanchard wrote:
Which leaves me wondering how to explicitly trigger faults in a
generic way.
This is stated, explicitly, in the documentation, both in the class
documentation:
<http://developer.apple.com/documentation/Cocoa/Reference/
CoreData_ObjC/Classes/NSManagedObject.html#//apple_ref/occ/instm/
NSManagedObject/willAccessValueForKey:>
and in the article on Faulting and Uniquing:
<http://developer.apple.com/documentation/Cocoa/Conceptual/CoreData/
Articles/cdFaultingUniquing.html>
The precise semantics of faulting behavior matter a lot in my case
and they are not well documented.
Given that you didn't find the references above, it's not clear just
how much of the documentation you have actually read. Note:
<http://developer.apple.com/documentation/Cocoa/Conceptual/CoreData/
Articles/cdManagedObjects.html#//apple_ref/doc/uid/TP40003397>
"It is important to appreciate that Core Data "owns" the life-cycle
of managed objects. With faulting and undo, you cannot make the same
assumptions about the life-cycle of a managed object as you would of
a standard Cocoa object—managed objects can be instantiated,
destroyed, and resurrected by the framework as it requires."
You appear to want Core Data to be EOF. It's not.
<http://developer.apple.com/documentation/Cocoa/Conceptual/CoreData/
Articles/cdFAQ.html>
Wishing it were and trying to program as if it were is pointless, as
is complaining here that it doesn't behave as EOF did. If you want
different features, please submit an enhancement request.
mmalc
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden