• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Database Application?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Database Application?


  • Subject: Re: Database Application?
  • From: Bill Bumgarner <email@hidden>
  • Date: Wed, 13 Dec 2006 16:03:14 -0800

On Dec 13, 2006, at 3:30 PM, Nick Zitzmann wrote:
On Dec 13, 2006, at 3:59 PM, Ferhat Ayaz wrote:
Thank you for your answer. CoreData was my first stop where I started to research. But in the documentation is written that CoreData is definitly not a database. How should I understand this?

CoreData is not a database. CoreData is a wrapper for Sqlite, although you can also use XML if you'd like.

Core Data is not a wrapper for SQLite. That Core Data can use SQLite as particular store type is an implementation detail that offers a very specific set of benefits, but it really isn't more than an implementation detail.


From Apple's site:

...
Core Data is as an object-graph management and persistence framework. In down-to-earth terms, this means that Core Data organizes the application's model layer into a set of defined in-memory data objects. Core Data tracks changes to these objects and can reverse those changes on demand, such as when a user performs an undo command. Then, when it is time to save changes to your application's data, Core Data takes care of archiving the objects to a persistent store. And, it saves data into regular files that users can manage with the Finder, search with Spotlight, backup to CD, and email to friends, family, and coworkers.


...

So, in other words, if you need:

- to support undo / redo, but don't really want to roll your own solution (which is very hard to get right)

- can model your apps data into an object model that kinda sorta looks like a database model

- don't need to connect to a database via client / server

- don't see a competitive advantage in re-inventing the storage wheel

- want to leverage the technology of Mac OS X fully

- don't gain personal satisfaction from hand tuning SQL

- ... etc (go read the intro to Core Data docs carefully) ...

Then you should use Core Data.

b.bum
_______________________________________________

Cocoa-dev mailing list (email@hidden)

Do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


References: 
 >Database Application? (From: Ferhat Ayaz <email@hidden>)
 >Re: Database Application? (From: Andrew Farmer <email@hidden>)
 >Re: Database Application? (From: Ferhat Ayaz <email@hidden>)
 >Re: Database Application? (From: Nick Zitzmann <email@hidden>)

  • Prev by Date: RE: Database Application?
  • Next by Date: Re: NSSplitView
  • Previous by thread: Re: Database Application?
  • Next by thread: Re: Database Application?
  • Index(es):
    • Date
    • Thread