I managed a tableview with NSFetchedResultsController whose fetch request uses a simple sort on a date attribute. It sorts properly when it first loads but when I refresh or call the loadMore method (
I have a UITableView with a lot of rows and a lot of sections (over 500 sections). Having a lot of rows is not so bad, because only the visible rows are loaded using the dequeueReusableCellWithIdentif
I have a couple of UIViewControllers that show a table view of my \'User\' objects as the section, and \'Site\' objects as rows under each section. The Site to User relationship is one-to-many.
Hi I do have a problem with my Core Data storage! I delete it the following way like I found it here an stack overflow:
i generate a tableview using core-data and a NSFetchedResultsController with sectionNameKeyPath. My Core-Data entities look fine, also in the SQL-Database the Data looks good.
This is the template code given in the doc of NSFetchedResultsControllerDelegate: - (void)controllerWillChangeContent:(NSFetchedResultsController *)controller {
I\'m having problem how to formulate NSPredicate to get correct data. I have three entities (Offer, List, Item) and an entity OfferMatch wchich matches an offer for each pair (List, Item).
I am presenting an NSManagedObject hierarchy (basically three levels) with different view controllers on iOS. The issue I don\'t completely understand is that if there is need for NSFetchedResultsCont
I have set a string (which is in fact a string) as the sectionNameKeyPath. It\'s sorts fine, but for example 16 september 2011, is in an earlier section than 2 september 2011. What is the best way to
My program does work like link below: Update results of NSFetchedResultsController without a new fetch
加载中,请稍侯......