Theocacao
Leopard
Design Element
Comment on "A Quick Overview of Basic CoreData Concepts"
by Bagelturf — Jun 12
The Core Data API is effectively split up into schema classes and runtime classes. On the schema side, the NSManagedObjectModel is at the top of the object graph. It contains the complete representation of the schema (though you can have multiple models in your application bundle).

I think I see what the big documentation issue is for Core Data. Stated as a problem:

Describe Core Data in terms of the problems it solves. But do so using only terms familiar to and understood by those trying to solve those problems, not using terms familiar to and understood by those who already know alternative solutions.

What is a schema? Why does it exist? What problem does it solve? What's so bad about re-mapping it in code? What is object-relational mapping? Why do I need it? What problem does it solve? Why are there two types of classes used? Why would I want multiple models?

Core Data is hard for those not familiar with typical solutions because they don't understand their problem in terms of the language in use. Increasingly that is the kind of person trying to use it -- someone tackling a problem they are familiar with but using tools with which they are not.
Back to "A Quick Overview of Basic CoreData Concepts"
Design Element

Copyright © Scott Stevenson 2004-2015