Core Data is a fantastic framework and I love using it. I agree that Core Data has a learning curve, but isn’t this true for many other frameworks? Because of Core Data’s learning curve, developers often turn to third party libraries that make working with the framework easier.
The types you can store in a Core Data persistent store are limited and it probably won’t surprise you that UIColor objects are not supported out of the box.
In Core Data Beyond the Basics, we work with an application that manages clients and their invoices. I named the application Invoices. What’s in a name? The application is similar to, for example, the mobile application of FreshBooks.
If you’re reading this, then I assume you are new to Core Data. You may have heard about Core Data and you’d like to find out whether it’s a good fit for you or the project you’re working on. If this description fits you, then take a seat. This Core Data tutorial teaches you everything you need to know to better understand what Core Data is and isn’t.
This tutorial has been updated for Xcode 8 and Swift 3. In the previous tutorial, we discussed Core Data in the light of concurrency. I hope that lesson has taught you that Core Data and concurrency can go hand in hand. As long as you remember the basic rules we discussed, you should be fine.
This tutorial has been updated for Xcode 8 and Swift 3. Up to now, we’ve used a single managed object context, which we created in the CoreDataManager class. This works fine, but there will be times when one managed object context won’t suffice.
This tutorial has been updated for Xcode 8 and Swift 3. The NSFetchedResultsController class is pretty nice, but you probably aren’t convinced yet by what you learned in the previous tutorial. In this tutorial, we explore the NSFetchedResultsControllerDelegate protocol. This protocol enables us to respond to changes in the managed object context the fetched results controller monitors. Let me show you what that means and how it works.
This tutorial has been updated for Xcode 8 and Swift 3. The NSFetchedResultsController class isn’t an essential component of a Core Data application, but it makes working with collections of managed objects much easier. This tutorial introduces you to the, almost magical, NSFetchedResultsController class.
This tutorial has been updated for Xcode 8 and Swift 3. Up until now, we’ve used NSManagedObject instances to represent and interact with records stored in the persistent store. This works fine, but the syntax is verbose, we lose autocompletion, and type safety is also an issue.
This tutorial has been updated for Xcode 8 and Swift 3. An application that grows and gains features also gains new requirements. The data model, for example, grows and changes. Core Data handles changes pretty well as long as you play by the rules of the framework.