Join Simon Allardice for an in-depth discussion in this video Introduction to data modeling in Core Data, part of Core Data for iOS and OS X.
So we've seen that the idea with Core Data is that we'll be able to take a group of objects…and just say save, that could be one object, two, or a hundred interrelated ones.…But I did mention that we don't need to save every single instantiated object, so that would…be a waste of time and resources that there are many objects in a running application…we'll never need to persist, temporary variables,…user interface objects that are already defined in our storyboard, or NIB files, so we can ignore those.…Really, it's about our own custom classes that we've written that will become our model objects, our data.…
Whatever that data is, simple text objects, complex binary objects,…but the objects we want Core Data to save.…Or you know, the best word here is not save or even persist, but manage.…These are the objects we want Core Data to manage, to manage their saving and loading,…to manage their undo and redo, to manage their lifetime.…So these are what we will call our managed objects.…There are still Objective-C objects with methods and properties.…
- Understanding Core Data and object persistence frameworks
- Creating a Core Data project
- Exploring data modeling
- Creating entities, attributes, and relationships
- Creating managed objects
- Fetching in Core Data
- Implementing undo and redo support
- Creating a Core Data Cocoa app without code
- Responding to validation issues
- Converting store types
- Preloading default data
Skill Level Intermediate
Q: In the CoursesViewController.m file, I receive a message that the method dismissModalViewControllerAnimated is no longer supported by Apple. Is there a newer method to use?
A: You may have received the warning that a call to the dismissModalViewControllerAnimated: method is now deprecated.
This is a recently deprecated method, so the code _will_ continue to work using that call, but to remove the warning, change the code from:
to the current recommended version:
[self dismissViewControllerAnimated:YES completion:nil];
It should take care of that message.