Should I use the basic data for a simple sqlite application on iphone with one table and without links or complex subtitles / views?

Question

From now on, should you use kernel data as a shell for a small iphone application using the sqlite database for a single table?

Does this unnecessarily complicate the situation or is it good practice to use from now on?

Answer 1

Yes, I think this is Core Data, not a complex API, and it provides access to many powerful features.

I had to face the same solution as you - I spent half a day in Core Data and was very happy.

An application that runs as a single table is useful, it can quickly become larger, and if you are not building on solid foundations, you may find that you have a huge headache in the future - just to save some time.

Yes, this is good practice - you will be so grateful for taking the master data route.

Answer 2

It's worth it.

• Your model with 1 table may become more complex in a future version. CoreData has some features for handling migration when the base model has changed.
• This allows you to use NSFetchedResultsController if you are using a UITableView. You almost don't have to encode anything related to saving, and this ensures that you never have more objects in memory than you really need to display.
• This will help you cancel. Is free.

It takes a couple of hours to read the textbook and the link, IMHO.

Answer 3

If I was building an application from scratch or doing a major revision anyway, I would look at Core Data at the same time.

Otherwise, if it did not break ...

Answer 4

I have already spoken about this. See how easy it is to save data to a simple PLIST file. I know several applications that do this today in the application store, and there is nothing wrong with this method.

Basically, you can take an NSDictionary object and save it as PLIST in a few lines or reload its contents from PLIST.

CoreData is great, and I use it in a more complex application, but there is a LOT to find out, and I think it is more than 3 projects than half a day.

Answer 5

Core Data is the foundation for creating the model component of the model-view-controller (MVC) architecture. Thus, its goal is to manage the schedule of object instances and, possibly, the best object graph management structure available on any platform. It so happened that Core Data can also transfer this object graph to disk. If you do not need the exact database schema (or exactly how your object model is stored on disk), you should carefully consider using Core Data.