NSFetchedResultsController does not support both change tracking and fetch request's with NSDictionaryResultType?

The error is referring to the fact that you are trying to obtain NSDictionary results, but then also expecting the fetched results controller to watch for changes. Since changes will only propagate through NSManagedObjects the fetched results controller can no longer perform its job Using NSManagedObjectResultType does not work because then setPropertiesToFetch: is no longer applicable. Instead, you would have to perform some coalescing of your own after the result set is known, which will make use with a fetched results controller rather difficult The best answer is to not set a cache name or a delegate for the fetched results controller, in which case it will not perform any change tracking.

The error is referring to the fact that you are trying to obtain NSDictionary results, but then also expecting the fetched results controller to watch for changes. Since changes will only propagate through NSManagedObjects, the fetched results controller can no longer perform its job. Using NSManagedObjectResultType does not work because then setPropertiesToFetch: is no longer applicable.

Instead, you would have to perform some coalescing of your own after the result set is known, which will make use with a fetched results controller rather difficult. The best answer is to not set a cache name or a delegate for the fetched results controller, in which case it will not perform any change tracking.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.