Merge changes from newBatchOperationContext about coredatastack HOT 2 CLOSED

Changes that occur in abatchOperationContext are not ever merged into the main context by the CoreDataStack. This is also intentional. You can read more about this in our blog post introducing the stack: Introducing the Big Nerd Ranch Core Data Stack Here is the relevant excerpt regarding this.

The changes could be propagated across contexts using the same pattern described in shared persistent store coordinator pattern using mergeChangesFromContextDidSaveNotification(). However, since this pattern is built for performance, it’s preferable to simply listen for the NSManagedObjectContextDidSaveNotification and re-perform your fetch request on the main queue context stack. This will be considerably faster than trying to merge thousands of objects between the two stacks.

You can see an example of inserting objects in a batchOperationContext and then refetching them in our unit tests. BatchOperationContextTests

from coredatastack.

Thanks for the quick reply @rcedwards , my issue was that I was downloading some data on main queue and after that some big import with duplicated data. That data already in memory didn't refresh from disk. Removed data duplication and not works as expected. Again, thanks.

from coredatastack.