Core data transient attributes and object life cycle
Core data transient attributes and object life cycle
- Subject: Core data transient attributes and object life cycle
- From: "Paulo F. Andrade" <email@hidden>
- Date: Mon, 23 Apr 2007 16:37:57 +0100
Hi,
I'm currently migrating my application to core data. And one of my
domain objects that was transformed in an NSManagedObject makes use
of a delegate.
I think I could I set this delegate attributed has transient and I
move on.
However I'm not sure how the Core Data framework handles the NMO life
cycle.
Scenario:
Imagine another object outside Core Data retains the NMO (let's call
it ObjX) and sets a delegate.
Later on the context is saved or there's a call to refreshObject:ObjX
mergeChanges:NO.
Will ObjX properties be flushed to disk? And then re-fetched when the
object retaining it dereferences one of it's properties?
What will happen to the transient property?
On a side note and to clarify my mental model of Core Data, is it
feasible to have ivars in NMOs subclassed not declared in the Managed
Object Model?
What would happen to them in the scenario above (imagine the delegate
isn't declared in the MOM).
Thank you for your help,
Paulo F. Andrade 52439@IST
mailto: email@hidden
_______________________________________________
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