Home/ Questions/Q 3691186
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-19T04:07:09+00:00

I’m studying using Core Data. After I create the entity in Xcode, I want

  • 0

I’m studying using Core Data.
After I create the entity in Xcode, I want to insert some data, which is master data, what is the common way or should I say best-practice to achieve this?

I googled a little and found out where the real sqlite file that generated by xcode located. It looks like /Users/<Username>/Library/Application Support/iPhone Simulator/User/Application/<Application GUID>/Documents/<database name.sqlite>
Now I’m wondering if I edit the sqlite (just to insert data) file directly is a proper way?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    If what you mean is a preset database setup for all new database instances, there’s a couple of ways to do this.

    1. Programmatically , you can insert Entities into the managedObjectContext with a bunch of code. This will get be slightly painful for anything other than a fairly trivial dataset but the advantage is that you can use all of NSPersistantDocument for virtually free.

    2. Use your app to create the dataset and then save it in the apps bundle as a read-only copy which you can clone as needed when a user creates a new database. A bit messier if you are using the NSPersistantDocument architecture.

    3. Do what you said in the first place . Use an sqlite3 client to inject data into the database to create a read-only copy like 2, but the risk is that there is more to the database structure that CoreData inserts which you dont know about so you might put a bit of work in to find that CoreData cannot read the db after you mess with it in sqlite3. I haven’t tried but it might work.

    IMHO 1 is the best practice as you get a bunch of free behavior from NSPersistantDocument

    • 0