Re: setValue:forKey: and to-many relationships
Re: setValue:forKey: and to-many relationships
- Subject: Re: setValue:forKey: and to-many relationships
- From: Mike Abdullah <email@hidden>
- Date: Fri, 23 Apr 2010 12:01:09 +0100
ah, good point. Seems pretty ugly though as you start suggesting that all managed objects support those methods. It only takes a moment to generate a subclass that does this.
On 23 Apr 2010, at 11:28, Roland King wrote:
> yes there is - and it's in the documentation too
>
> http://developer.apple.com/mac/library/documentation/cocoa/conceptual/CoreData/Articles/cdAccessorMethods.html
>
> "If you are not using a custom class, to suppress compiler warnings you can declare the properties in a category of NSManagedObject:"
>
> and it gives you an example there as well.
>
>
> On 23-Apr-2010, at 6:21 PM, Mike Abdullah wrote:
>
>>
>> On 23 Apr 2010, at 10:46, Christian Ziegler wrote:
>>
>>> Hi all!
>>>
>>> I would like to step in here for a related question. Is there any way to get rid of the compiler warnings if you use the generated accessors without writing a subclass of NSManagedObject and adding properties and method declarations?
>>
>> No there isn't. But the xcode modeller can easily generate those method declarations for you when writing a new class.
>>
>> _______________________________________________
>>
>> 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
>
_______________________________________________
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