Use CoreData or SQLite on iPhone?

3 Solutions Collect From Internet About “Use CoreData or SQLite on iPhone?”

This is a common question here:

  • “Core Data vs. SQLite for SQL experienced developers”
  • “Core Data vs Sqlite and performance…”
  • “Core Data vs sqlite3”
  • “is it worth using core data for a simple sqlite app on the iphone with one table and no relationships or complicated subtable/views?”

In summary, Core Data can greatly simplify your code, particularly for complex object models. You get undo / redo support almost for free with it. It also provides some very significant performance benefits, particularly on the iPhone. Even though it seems counterintuitive, given how much overhead you’d think the framework has, in most cases you can beat the performance of hand-tuned SQLite using Core Data. On the iPhone, it does a great job of batching fetches to minimize memory usage.

The one downside, as pointed out, is that this limits you by requiring iPhone OS 3.0 for your end users. However, this has not been a problem at all for my users, and will only become less of one going forward.

This might be a lesser benefit, but SQLite is a lot more portable between platforms, since Core Data is part of Cocoa, and SQLite is pure C. This means that if you wanted to port your application to PC, for instance, you would have less code to rewrite in the event that you use pure SQLite.

Then if you wanted to develop anything else cross-platform using a local DB (not necessarily related to any iPhone apps), you would have already have some experience with SQLite.

If you want your application to run on iPhones not running OS 3.0, you will have to use SQLite.

However, using CoreData (which uses SQLite as a backend, I believe) means you don’t have to write your own database-interaction code which is quite a hassle to do, especially when you are doing relations etc.

I use CoreData myself…