Re: multiple inheritance equivalent in Core Data?
Re: multiple inheritance equivalent in Core Data?
- Subject: Re: multiple inheritance equivalent in Core Data?
- From: John Timmer <email@hidden>
- Date: Mon, 09 May 2005 16:11:44 -0400
>
> On May 9, 2005, at 12:26 PM, John Timmer wrote:
>
>>> The overhead of adding what are effectively unused attributes to a
>>> model should not exactly over-tax the system, however I'm not sure in
>>> what sense you're wanting to "simplify the object graph"? What
>>> problem is there with adding the attributes to just those entities
>>> that need them?
>>
>> The original issue is that I was adding three keys to the base
>> class, when
>> most of the subclasses only needed to use two of them.
>
> Just to clarify, do you mean base class or base entity?
Sorry - both, really (I think). I defined an entity and I'm making it an
NSManagedObject subclass, because I'm deriving a 4th key from one of the 3
that I'm letting Core Data manage (this is the "searchableNotes" string vs.
the notes RTF data I had brought up a couple of days ago). In addition to
the notes, i'm also defining a name and ID there, and most of the objects
that inherit from this will need 2 or 3 of the name/notes/ID combination,
but in the cases where it's 2, it's never the same 2.
I also apologize if I seem to keep asking questions where I seem to already
know the answer in terms of how best to handle things with Core Data. I'm a
self taught programmer, and I'm doing it in my spare time while trying to be
a full time biologist, so I tend not to trust the answers I've come up with.
Thanks for your patience,
'John
_______________________________________________
This mind intentionally left blank
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden