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: Caleb Strockbine <email@hidden>
- Date: Thu, 28 Aug 2008 00:43:53 -0400
On Aug 27, 2008, at 2:43 PM, Negm-Awad Amin and mmalc crawford argued:
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 no need to create a subclass,
"You *can* subclass NSManagedObject
"
you can use a category instead.
There is no need to create a category. You can use a subclass
instead.
It's not clear what your point is.
There is no need to create a custom class if all you're doing is
declaring accessor methods. Your reply did not state that.
Perhaps I'm being dense here, but why would you use a category on
NSManagedObject to declare accessors that only actually apply to a
single entity? Managed object models typically contain more than one
entity, and each of those entities necessarily has a different set of
properties (otherwise, you wouldn't need more than one entity). If
you use a category on NSManagedObject to add accessors for each
entity in your model, don't you end up with a situation where all
your entities have declared accessors for other entities' properties?
On the other hand, if you subclass NSManagedObject where necessary,
each subclass' accessors will be specific to it's corresponding entity.
Am I missing something?
-Caleb
_______________________________________________
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