Core Data: Fundamentals

Heads up... You've reached locked video content where the transcript will be shown as obfuscated text.

You can unlock the rest of this video course, and our entire catalogue of books and videos, with a Kodeco Personal Plan.

Unlock now

In this part of the course, you learned about the different classes that play a role in creating the core data stack. Let's recap, what you've learned. You start with the object graph layer of the stack, represented by two main parts. The managed object model and the managed object context. One or more managed objects, each of which represents a data type in your app, make up the manage object model. You define an entity in a visual editor and core data creates a managed object for you that provides an interface for the underlying generic data container. You must register each of these managed objects with the managed object context. Its job is to keep track of all the changes to the managed object model. When the program saves the context, it hands off these changes to the persistent store coordinator. The coordinator facilitates communication between the context and the data store. It either creates the instances of the data based off of changes requested by the context or it fetches data from the store as requested by the context. The persistent store coordinator hides most of the implementation details away from the context, so that it doesn't know what the underlying data store is or how many there are. The final object, which is technically not part of the stack is the persistent container that handles the creation of the entire stack with minimal setup. Now that you're up to speed on the core data stack, it's time to use it. In the next part of the course, you'll store some launches.