Core Data document-based app design decision?
Core Data document-based app design decision?
- Subject: Core Data document-based app design decision?
- From: Jörgen Isaksson <email@hidden>
- Date: Fri, 25 Aug 2006 11:00:49 +0200
Hi all!
I'm working on a Core Data document-based application using
NSPersistentDocument.
I have a question regarding Core Data design and application related
data in a document-based application.
I need to store data that is common for all documents, so I created a
new data model for the application data. This model has it's own
persistent store, like a Core Data application. At startup I load the
application model from the bundle and create the managed object model
for the app. The persistent store coordinator is also created to save
it's data in the application support folder in a subfolder for this app.
I have not seen this setup in any Core Data example apps, but it
seems to work fine. I haven't found anything in the documentation
that tells me that this is wrong.
So the question is:
Is this the correct way to design a Core Data document based
application that needs to save some application related data?
--
Joergen Isaksson, Sweden
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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