Re: Core Data design patterns
Re: Core Data design patterns
- Subject: Re: Core Data design patterns
- From: mmalc Crawford <email@hidden>
- Date: Sun, 19 Jul 2009 17:12:47 -0700
On Jul 19, 2009, at 1:59 PM, Squ Aire wrote:
* Finally an unrelated and basic Core Data question: Where do you
paste the code you copy using the "Copy Method Declarations/
Implementations" feature in the data modeling tool? I really want to
use those things because it is, according to docs, faster than
valueForKey, setValueForKey, etc. Up until now, I have tended to
make a subclass of each of my managed objects and pasted the
declarations/implementations in there. Do you think this is a good
idea?
Yes, this is fine.
If you really want to avoid multiple NSManagedObject subclasses, you
may also create categories of NSManagedObject that declare the various
properties, but in general I find that using custom classes "feels
better".
mmalc
_______________________________________________
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