Pre-populated database. Now I want to add more data without messing the pre-existing data?

If you change the managed object model itself e.g. Add a new entity or change an existing attribute, then you need to use migration to update the existing persistent store. See the Core Data docs for details on migration If you just want to add new data, then you don't have any choice but to do so "manually Remember, Core Data is an object graph management system, not a database.An object "graph" is a "web" of interrelated objects so the only way to add data to the graph is to create new objects and set their relationships. It's not inefficient, it just the way it works.

If you change the managed object model itself e.g. Add a new entity or change an existing attribute, then you need to use migration to update the existing persistent store. See the Core Data docs for details on migration. If you just want to add new data, then you don't have any choice but to do so "manually.

" Remember, Core Data is an object graph management system, not a database. An object "graph" is a "web" of interrelated objects so the only way to add data to the graph is to create new objects and set their relationships.It's not inefficient, it just the way it works.

– jyap Jun 4 at 23:23 It depends. Do you want to just replace the existing data and/or persistent store? Are you going to update the model itself?

Do you want to merge the data with the users existing data? – TechZen Jun 5 at 19:49 I'm going to mark this as answered.At first I was thinking of merging the new data but then I thought this would get really complicated to track and require more code. Instead I'm going to backup the user created data, delete the existing persistent store and copy a new pre-populated data store to the app's persistent store.

– jyap Jun 6 at 8:30.

Add a new entity or change an existing attribute, then you need to use migration to update the existing persistent store. See the Core Data docs for details on migration. Remember, Core Data is an object graph management system, not a database.

An object "graph" is a "web" of interrelated objects so the only way to add data to the graph is to create new objects and set their relationships. It's not inefficient, it just the way it works.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.

Related Questions