• 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: Core Data Merged Models
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Core Data Merged Models


  • Subject: Re: Core Data Merged Models
  • From: Jonathon Mah <email@hidden>
  • Date: Sun, 23 Apr 2006 22:58:26 +0930

Matthew and Malcolm,

On 2006-04-23, at 08:45, Matthew Firlik wrote:

What happens when frameworks change over time?
[...] So while accessing a merged model using the "allFrameworks" array from NSBundle might not return any "extra" entities today, it just might in the near future: this is a good reason to use the most explicit/specific/minimal array of bundles necessary to load your models if you use the mergedModelFromBundles API.

Yes, that's what I suspected. I was mainly wondering about the reason for using that in the template, but Matthew noted that they have been changed now.


Thanks,


Jonathon Mah email@hidden


_______________________________________________ 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
References: 
 >Core Data Merged Models (From: Jonathon Mah <email@hidden>)
 >Re: Core Data Merged Models (From: Matthew Firlik <email@hidden>)
 >Re: Core Data Merged Models (From: Matthew Firlik <email@hidden>)

  • Prev by Date: Re: Superimpose a NSTextField over NSImageView?
  • Next by Date: Re: Superimpose a NSTextField over NSImageView?
  • Previous by thread: Re: Core Data Merged Models
  • Next by thread: Re: Cocoa-dev Digest, Vol 3, Issue 521
  • Index(es):
    • Date
    • Thread