I can use the main queue context in UI and don't need to worry about anything going on in the background.When a data import finishes the changes become visible in the UI immediately.
When you need to update a large set of data, this new API allows you to accomplish the task more quickly and efficiently.
I know this will become an invaluable tool in my Core Data repertoire! He will be joined by Nerds discussing Interactive Playgrounds and Functional Programming, Asynchronous Testing, Extensions, Cloud Kit, Home Kit, Health Kit and Handoff, along with Adaptive UI and what i OS 8 means for design.
It makes initializing objects easier and more predictable. What if we undeprecate I think Data Kit has settled on the preferred set up for the majority of cases people will likely encounter.
Everywhere in Data Kit, you can override the context. But I think ambiguity lies in which context (Main or Private) "should" serve as the parent to a a new private context thats been created for some batch of operations we don't want to interfere with saving and/or UI updates.
By monitoring the heap size in Xcode, we can observe a batch update increasing the memory footprint by only a few MBs during the fetch.
Contrast that with an update that iterated over each object, which resulted in a sharp increase of memory load close to 200 MBs!
The SO post and article described bugs with nested MOC.
So I to a quick fix: This setup works really well for me.
An often-cited shortcoming of Core Data is its inability to efficiently update a large number of objects with a new value for one or more of its properties.