พื้นฐาน Core Data

Hello! Today we're diving into Core Data, Apple's powerful framework for managing and persisting an application's object graph.

It helps you store your app's data on disk and retrieve it efficiently.

It's crucial to understand: Core Data itself is not a database. Instead, it's an object graph management framework.

• It helps you manage your data objects in memory.
• It provides tools to save these objects to a persistent store (which *can* be a database like SQLite).
• Think of it as an abstraction layer over the actual storage.

Core Data relies on a 'stack' of objects that work together. Understanding these components is key:

• Managed Object Model: Your app's data schema.
• Persistent Store Coordinator: Connects the model to the store.
• Persistent Store: The actual storage (e.g., SQLite file).
• Managed Object Context: Your scratchpad for data interaction.

The Managed Object Model (NSManagedObjectModel) defines your application's data structure.

• It's where you specify entities (like tables in a database).
• Each entity has attributes (properties, e.g., name, age).
• You can also define relationships between entities.

You typically create this visually in Xcode using the data model editor (a .xcdatamodeld file).

The Persistent Store Coordinator (NSPersistentStoreCoordinator) acts as a bridge.

• It takes your NSManagedObjectModel.
• It connects it to one or more persistent stores.
• Common store types include SQLite, XML, or binary files. SQLite is the most common for iOS apps.

The Persistent Store (NSPersistentStore) is where your data actually lives on disk.

When you choose an SQLite store, Core Data creates and manages an SQLite database file. You don't interact with SQL directly; Core Data handles it for you.

The Managed Object Context (NSManagedObjectContext) is your primary interface for interacting with Core Data.

• Think of it as a 'scratchpad' where you create, retrieve, update, and delete objects.
• Changes made here are temporary until you 'save' the context.
• It tracks all changes and reports them to the Persistent Store Coordinator when saved.

Data records in Core Data are represented by instances of NSManagedObject (or its subclasses).

They are similar to regular Objective-C objects, but their properties are managed by Core Data.

Here's how you'd typically create and set properties on such an object (assuming a context is ready):

After you create, modify, or delete NSManagedObject instances within a NSManagedObjectContext, these changes are only in memory.

To persist them to the Persistent Store, you must tell the context to save:

It's crucial to always check for errors when saving!

Which Core Data component is responsible for defining your application's data structure, including entities and their attributes?

We've covered the basics of Core Data, Apple's object graph management framework. Remember:

• It's not a database, but uses them for storage.
• The Core Data Stack includes Model, Coordinator, Store, and Context.
• Managed Object Model defines your data.
• Persistent Store Coordinator connects model to store.
• Persistent Store is the physical data location.
• Managed Object Context is your interaction point.
• You interact with NSManagedObject instances and must save the context to persist changes.

Next, we'll explore fetching data and more complex interactions!