Geek asks and answers

Ios-coredata: what's the difference between in-memory tracking and full permanent tracking?

The document is too simple for me to get a full understanding.

Thus, the controller has three operating modes, determined by whether it has a delegate and whether the cache file name is set.

Lack of tracking: the delegate is set to zero. The controller simply provides access to the data, as it was when sampling.

Tracking only memory: the delegate is not zero and the file cache name is set to zero. The controller controls the objects in its result set and update the section and organize the information in response to the corresponding changes.

Full persistent tracking: delegate and file cache name non-zero. The controller monitors the objects in its resulting set and updates the section and order information in response to the corresponding changes. the controller maintains a constant cache of calculation results.

what is what the documents said, so what does the "permanent cache" do? What is the "result of its calculation"? Is cache just a performance issue?

+3
source share
2 answers

In the NSFetchedResultsController documentation:

If possible, the controller uses the cache to avoid the need to repeat the work performed when setting up any partitions and organizing the contents.

NSFetchResultsController UITableView, . , , , .

, , .

0

information about sections in the result set, and for the index., , UITableView , . , , .

0

More articles:


All Articles