• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: multiple inheritance equivalent in Core Data?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: multiple inheritance equivalent in Core Data?


  • Subject: Re: multiple inheritance equivalent in Core Data?
  • From: mmalcolm crawford <email@hidden>
  • Date: Mon, 9 May 2005 12:52:01 -0700


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?

mmalc

_______________________________________________
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


  • Follow-Ups:
    • Re: multiple inheritance equivalent in Core Data?
      • From: John Timmer <email@hidden>
References: 
 >Re: multiple inheritance equivalent in Core Data? (From: John Timmer <email@hidden>)

  • Prev by Date: Re: table column with <date value> null placeholder
  • Next by Date: User Date Formatter (was Re: table column with <date value> null placeholder)
  • Previous by thread: Re: multiple inheritance equivalent in Core Data?
  • Next by thread: Re: multiple inheritance equivalent in Core Data?
  • Index(es):
    • Date
    • Thread