Do you want an efficient bulk insert process, while also using a performant process with easy to merge child contexts. Although this model can easily be abused, it could be a good fit for your app if you understand the process and maintain it properly. This video covers a simple example with multiple coordinators, and child contexts.
- Let's go ahead and look at our mixed-architecture example.…In here we're going to have two different coordinators;…it's like the third architecture that we talked about.…But we're going to have separate coordinators,…so that we can both import a certain amount of records…and also still use the UI at the same time.…In the example, I pattern this after…the original child example, so we have a child context…and then we'll start building out the extra coordinator.…When you click plus, you can see that changes happen first…to all the records that were in here…for the first coordinator, and then we can see that data…has loaded from the second coordinator at a later time.…
So the first thing we need to do,…is to come to the core-data stack,…and add our second coordinator.…Right here, and we're just making…our second persistent store coordinator…the same way that we would create a normal coordinator.…We're going to base this off the standard object model.…We're going to go and give it the correct path…of the database to load into,…
This course is meant for the enterprise developer who wants to get up to speed with the latest methods with Core Data. Instructor Jon Bott starts with a review of the basics, explaining the different architectural data models currently in use, the issues that can arise from these different models, and how the latest changes in Core Data 2016 simplify these models. He wraps up with hands-on migration to the new APIs and further tips on leveraging them in iOS 10 and macOS 10.12 apps.
- Fetching data
- Working with objects, queues, and threads
- Understanding the architectural models
- Managing local and server-side data
- Understanding iOS 10 and macOS 10.12 updates to Core Data
- Migrating to the new core data