4

I'm currently in the process of deciding whether or not to use Core Data for managing the data in my iphone application.

The application involves putting together a fairly sizeable library of content which needs to be localised and has a fair few relationships. One benefit I thought of using core data would be that I could perhaps build a desktop client for managing the data of the application, then package the resulting file with the iPhone app to use as its content database.

With my fairly limited knowledge of Core Data I wanted to know if this is possible? Are their any best-practices people can point me in the direction of?

Chris Hanson
  • 54,380
  • 8
  • 73
  • 102
Tricky
  • 7,025
  • 5
  • 33
  • 43
  • 3
    Keep in mind that Core Data on the iPhone is still under NDA, so you shouldn't ask too-specific questions about it here. – Alex Jun 01 '09 at 18:20

3 Answers3

1

This is basically a dupe of this question:

Provide Base Data for Core Data Application?

Short answer is - YES. I've done it, Apple does it. Works well.

Community
  • 1
  • 1
Hunter
  • 4,343
  • 5
  • 42
  • 44
0

Core Data defines the interface for interacting with the database, not the storage itself. You can use XML, Binary, or SQLite as the storage file. If you want a quick-and-dirty solution, you could use a basic SQLite application such as Menial's Bases to create a database. You can then add this to your XCode project for use by the iPhone. If you intend for the desktop client to be used by your iPhone customers, you can can use much of the same Core Data code from your iPhone project.

-1

Core Data is now included starting a SDK 3.0.

gonso
  • 2,065
  • 5
  • 27
  • 35