Coredata - populating initial data on app load - best practices
Coredata - populating initial data on app load - best practices
- Subject: Coredata - populating initial data on app load - best practices
- From: "Jason Kravitz" <email@hidden>
- Date: Mon, 3 Mar 2008 16:48:05 +0100
I am writing my first coredata application and am wondering what the
recommended way is to populate initial data. Most coredata examples do
a good job explaining binding and getting data from the UI but fail to
refer to populating the initial data set.
I was looking at the background fetching example and would like to do
something similar to the DataGenerator portion of this project but
only the first time my application runs on a new installation. After
that, the initial data should be populated and a new user can use the
application normally each time they load it.
Is there a recommended way to do this? It is only about 5mb of data or
less. I was thinking I could even create an initial store myself and
store it as a resource and then on load, check if the store exists and
if not, copy from resource dir to Application Support dir so that it
is there for all the next runs of the application. Would this be
correct in Cocoa dev terms or is there a better way?
thanks!
_______________________________________________
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