The reason removing your delete code makes it work is because you are removing the data in the persistent store without updating the other view that still has managed object instances tied to that data still in memory. Remember, while Core Data deals with objects, each object has to have a row in the database … Read more
You will need to change %@ for %i and remove the extra parenthesis: Main problem here is that you are putting an Int where it’s expecting an String. Here’s an example based on this post: class Person: NSObject { let firstName: String let lastName: String let age: Int init(firstName: String, lastName: String, age: Int) { … Read more
I had the same problem and my solution was to delete the application and install it again because of modifications in database.
CoreDataEditor is $20 and doesn’t make it quick and easy to browse the relationships of the managed object context. There was also some insanity about having to have the MOM use exactly the same name as your application (??!), or somesuch. I’m not about to go in and start renaming stuff just to browse my … Read more
You can definitely use that approach. From Apple’s Core Data Programming guide: Entity inheritance works in a similar way to class inheritance; and is useful for the same reasons. If you have a number of entities that are similar, you can factor the common properties into a superentity, also known as a parent entity. Rather … Read more
The NSFetchedResultsController is only designed to watch one entity at a time. Your setup, while it makes sense, it a bit beyond what the NSFetchedResultsController is currently capable of watching on its own. My recommendation would be to set up your own watcher. You can base it off the ZSContextWatcher I have set up on … Read more