NSFetchedResultsController

Apple

 * NSFetchedResultsController
 * NSFetchedResultsControllerDelegate

Core Data and NSMutableArrays

 * http://stackoverflow.com/questions/1363525/how-to-properly-configure-nsfetchedresultscontroller
 * http://www.cimgf.com/2010/06/05/re-ordering-nsfetchedresultscontroller/

Section Header

 * http://stackoverflow.com/questions/1741093/how-to-use-the-first-character-as-a-section-name
 * http://stackoverflow.com/questions/1112521/nsfetchedresultscontroller-with-sections-created-by-first-letter-of-a-string

Sections and Core Data

 * http://forums.macrumors.com/showthread.php?t=794736

Reordering Results

 * http://www.cimgf.com/2010/06/05/re-ordering-nsfetchedresultscontroller/

Misc

 * http://tuts9.com/questions/27831/using-an-nsfetchedresultscontroller-without-a-uitableviewcontroller

Pitfalls
If you were to use a predicate that involves transversing a one-to-many relationship, the performance could be slowed down tremendously (as slow as 30 sec to run, or even crash!). Take for example a Template model that has a one-to-many relationship tags to Tag model: [request setPredicate:[NSPredicate predicateWithFormat:@"ANY tags.name = 'tagname'"]]; The predicate above would require transversing to each Tag to find ‘love’. This is computationally very expensive. The solution to this is to avoid transversing relationship. A faster way that CoreData could execute is to access the properties/attributes. For the above example, what I did is to add another attribute tagsAsAttribute to Template model. This property would store the tag names in a delimited format such as “;love;jokes;quotes;”. The predicate would then be changed to: [request setPredicate:[NSPredicate predicateWithFormat:@"tags CONTAINS ';tagname;'"]]; Note: This is not the best way to design the data model, as tagsAsAttribute has a dependency and is redundant.
 * http://just2us.com/2010/02/pitfalls-of-nsfetchedresultscontroller/
 * http://petersteinberger.com/2010/09/fixing-nsfetchedresultscontroller/
 * http://deusty.blogspot.com/2010/02/more-bugs-in-nsfetchedresultscontroller.html