Re: Core Data - use of simple accessors vs. KVC
Re: Core Data - use of simple accessors vs. KVC
- Subject: Re: Core Data - use of simple accessors vs. KVC
- From: Negm-Awad Amin <email@hidden>
- Date: Wed, 27 Aug 2008 18:47:05 +0200
Am Mi,27.08.2008 um 18:22 schrieb Oleg Krupnov:
A simple newbie question:
Suppose I have a Core Data model object MyObject with property myProp
defined in the model editor's schema.
Can I use the simple accessors like this:
[myObj myProp]
[myObj setMyProp]
or am I forced to use the rather clunky valueForKey/setVakyeForKey
messages?
Managed objects automatically fake accessors for entities.
You can subclass NSManagedObject and add properties using @property
and @dynamic, which means, that the accessors will be generated
dynamically at run-time. (Without @dynamic you will get a compiler
warning: incomplete implementation blablabla)
There is documentation about @property and Core-Data esp. in relation
to retain/copy/assign. (The quintessence: Use retain!)
Cheers,
Amin
I thought that Core Data kind of auto-generates these standard
accessors for me and I don't have to write any manual code (if I don't
want anything special). However I've just got the compiler warning
that "MyObhect may not respond to '-myProp'"
Was I wrong or am I doing something wrong?
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden
Amin Negm-Awad
email@hidden
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden