Menu
G'day Folks
My CoreData driven app has a number of views of data from the same store & all using an NSFetchedResultsController. Currently they all have the same name for the NSFetchedResultsController cache, "Root". Users of my app can, & probably will, jump indiscriminately between views. Would it be better for user experience if I gave the cache for each NSFetchedResultsController a unique name?
TIA, Pedro :)
735
NSPersistentContainer simplifies the creation and management of the Core Data stack by handling the creation of the managed object model ( NSManagedObjectModel ), persistent store coordinator ( NSPersistentStoreCoordinator ), and the managed object context ( NSManagedObjectContext ).
NSFetchedResultsController is a very useful class provided by the CoreData framework. It solves many performance issues you frequently run into while reading a large amount of data from database and displaying that data using a UITableview, UICollectionView or MKMapView.
An object space to manipulate and track changes to managed objects.
The fetched results controller efficiently analyzes the result of the fetch request and computes all the information about sections in the result set. It also computes all the information for the index based on the result set.
Providing a different cache name for different fetches is advisable and will help with performance.
From Apple documentation at http://developer.apple.com/library/ios/documentation/CoreData/Reference/NSFetchedResultsController_Class/Reference/Reference.html#//apple_ref/doc/uid/TP40008227-CH1-SW24
If you have multiple fetched results controllers with different configurations (different sort descriptors and so on), you must give each a different cache name.
Cheers, Rog
152
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
