• 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: Cocoa based Data Model dilemna
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Cocoa based Data Model dilemna


  • Subject: Re: Cocoa based Data Model dilemna
  • From: Jerry Krinock <email@hidden>
  • Date: Wed, 26 Jan 2011 10:03:37 -0800

On 2011 Jan 26, at 08:21,  David DelMonte wrote:

> Are either of these scenarios possible?

I didn't really comprehend all of your description, but in computer programming, the answer to "Is it possible?" is almost always "Yes".  To determine whether or not it's "smart" usually requires lengthy consideration of your app and where it's headed, and only you can do that.

I noticed that you didn't mention using an Abstract Entity with Child Entities.  You might consider these, although when I did used them, and later had to add a migration policy, this caused a crash in Mac OS 10.5, and the workaround causes warnings whenever I build.  So, be advised that Abstract Entities are a little off the beaten path.

_______________________________________________

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

References: 
 >Cocoa based Data Model dilemna (From:  David DelMonte <email@hidden>)

  • Prev by Date: Re: Redisplaying a NSTableColumn NSTableHeaderCell
  • Next by Date: Re: CoreData: Crash in NSManagedObjectContext#existingObjectWithID:error:
  • Previous by thread: Cocoa based Data Model dilemna
  • Next by thread: Re: Cocoa based Data Model dilemna
  • Index(es):
    • Date
    • Thread