• 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: Another rookie core data question
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Another rookie core data question


  • Subject: Re: Another rookie core data question
  • From: Charilaos Skiadas <email@hidden>
  • Date: Wed, 27 Jul 2005 17:15:26 -0500

On Jul 27, 2005, at 5:01 PM, Andy Shamel wrote:

Is it possible to have more than one data model in a project?  I.e.
could i have one data model and persistant store for the application
itself, and another for documents?  And further, would it be possible
to communicate between these two stores, etc.  If anyone could either
provide some tips or point me towards some documentation, i would very
much appreciate it!

So you mean you'd have a standard model handled by NSPersistentDocument, and then you want another one that's sort of unique for you application? I don't see why you wouldn't be able to do it, at worst programmatically. The documentation for NSManagedObjectModel seems to indicate you can create one using initWithContentsOfURL.
So maybe you could create a second model with the XCode model tool, and in your code load it at the appropriate location (maybe appdelegate or something) and then go for there.
As usual, not tried it, just brainstorming, sounds doable etc...
thanks so much!

--andy

Haris


_______________________________________________ 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: 
 >Another rookie core data question (From: Andy Shamel <email@hidden>)

  • Prev by Date: Re: Developing for Tiger and Panther;
  • Next by Date: Re: Developing for Tiger and Panther;
  • Previous by thread: Another rookie core data question
  • Next by thread: Re: Another rookie core data question
  • Index(es):
    • Date
    • Thread