Databases
StackOverflow2013
Postsdbo
POBest practices of using simple Fetch and Predicate or a Fetched Result Controller in Core Data with iOS Table View?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POBest practices of using simple Fetch and Predicate or a Fetched Result Controller in Core Data with iOS Table View?
    primarykey
    data
    text
    <p>After using Core Data in several cases I just wondering in which case which solution is the best? Even fetchedResultController is extensively used and popular especially in Apple documentations my guess that's not the best solution or fit well in other cases where the code have to fetch more then one managedObject etc.. Several times it pushes developers to use two or more fetchedResultControllers which is really complicate and rigid solution. I found several beautiful and brilliantly simple solution from Marcus Zarra for the Fetch/Predicate solution, and love Jeff LaMarche's <a href="http://iphonedevelopment.blogspot.hu/2010/01/navigation-based-core-data-application.html" rel="nofollow" title="Jeff LaMarche's Blog">polished navigation-based fetchedResultController</a>, but what's the real difference?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USBootMaker
    1. USBootMaker
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COCompare http://stackoverflow.com/questions/13335775/core-date-concept-nsfetchedresultscontroller-vs-nsmanagedobject-objectswithfet. Is that what you are asking?
      singulars
      1. POBest practices of using simple Fetch and Predicate or a Fetched Result Controller in Core Data with iOS Table View?
      1. USMartin R
    2. CO@Martin R Your linked answer is absolutely correct and good but it emphasizes the notification/modification as a difference which is just one aspect and replaceable with NSNotification for which Zarra offered a nice solution in another [answer](http://stackoverflow.com/questions/3147122/core-data-can-nsfetchedresultscontroller-fetch-two-different-entities). Just a kickoff question: If I have a tableView with 1000+ elements to populate, both solutions just fetch the visible cells and fault the others? Which is faster?
      singulars
      1. POBest practices of using simple Fetch and Predicate or a Fetched Result Controller in Core Data with iOS Table View?
      1. USBootMaker
    3. CO1) So your question is restricted to table views? If you don't need automatic updates then using a FRC does not make sense. - 2) A FRC is designed for driving table views and it should optimize batch sizes etc for this purpose. But I did not make performance checks yet so I cannot give a definite answer to "which is faster". If you test it yourself, add the "-com.apple.CoreData.SQLDebug 1" argument to the launch options to see what is happening on the SQLite level.
      singulars
      1. POBest practices of using simple Fetch and Predicate or a Fetched Result Controller in Core Data with iOS Table View?
      1. USMartin R
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload