Re: CoreData and Shared Data
Re: CoreData and Shared Data
- Subject: Re: CoreData and Shared Data
- From: Lucas Haley <email@hidden>
- Date: Wed, 28 Dec 2005 15:10:53 -0800
mmalc, thanks for the reply. I'll try to clarify a bit:
Each individual document has its own data model. In addition, every
document shares a data model; like a library that each document will
refer to, using to-one relationships. I would rather not store the
large library in each document, it seems a terrible waste. So I was
thinking that the app as a whole could store the library, and each
document could connect to it. What I do not know how to do is how to
model it -- if there is a way to represent the library in the
document model, maintaining the relationships but without storing the
data. Or if I need to model the document and the library separately,
and connect the relationships in code.
Thanks for the help!
-Lucas
I'll be using a NSPersistentDocument for the documents. The issue I
have is that I have an additional central data structure that is
referenced by each document across relationships. Can I model the
whole thing using the UI, or will I have to create a separate model
for the application, and in code define the relationships from the
documents?
It's not clear what this means. You can create the whole managed
object model using the Xcode data modeling tool. If you want, you
can create a single model for the whole schema and use configurations
for the different stores. If you want to create cross-store
relationships, then that will require additional coding for
relationship maintenance, but not for the modeling per se.
mmalc
________________
Lucas Haley
email@hidden
http://www.pnca.edu/
503.821.8906
_______________________________________________
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