Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You should just pass "name" as the sectionNameKeyPath. See this <a href="https://stackoverflow.com/questions/1599204/core-data-backed-uitableview-with-indexing/1603428#1603428">answer</a> to the question "Core Data backed UITableView with indexing".</p> <p><strong>UPDATE</strong><br> That solution only works if you only care about having the fast index title scroller. In that case, you would NOT display the section headers. See below for sample code. </p> <p>Otherwise, I agree with refulgentis that a transient property is the best solution. Also, when creating the NSFetchedResultsController, the <a href="http://developer.apple.com/iPhone/library/documentation/CoreData/Reference/NSFetchedResultsController_Class/Reference/Reference.html#//apple_ref/doc/uid/TP40008227-CH1-SW1" rel="nofollow noreferrer">sectionNameKeyPath</a> has this limitation:</p> <blockquote> <p>If this key path is not the same as that specified by the first sort descriptor in fetchRequest, they must generate the same relative orderings. For example, the first sort descriptor in fetchRequest might specify the key for a persistent property; sectionNameKeyPath might specify a key for a transient property derived from the persistent property.</p> </blockquote> <p>Boilerplate UITableViewDataSource implementations using NSFetchedResultsController: </p> <pre><code>- (NSInteger)numberOfSectionsInTableView:(UITableView *)tableView { return [[fetchedResultsController sections] count]; } - (NSArray *)sectionIndexTitlesForTableView:(UITableView *)tableView { return [fetchedResultsController sectionIndexTitles]; } - (NSInteger)tableView:(UITableView *)tableView sectionForSectionIndexTitle:(NSString *)title atIndex:(NSInteger)index { return [fetchedResultsController sectionForSectionIndexTitle:title atIndex:index]; } - (NSInteger)tableView:(UITableView *)tableView numberOfRowsInSection:(NSInteger)section { id &lt;NSFetchedResultsSectionInfo&gt; sectionInfo = [[fetchedResultsController sections] objectAtIndex:section]; return [sectionInfo numberOfObjects]; } // Don't implement this since each "name" is its own section: //- (NSString *)tableView:(UITableView *)tableView titleForHeaderInSection:(NSInteger)section { // id &lt;NSFetchedResultsSectionInfo&gt; sectionInfo = [[fetchedResultsController sections] objectAtIndex:section]; // return [sectionInfo name]; //} </code></pre> <p><strong>UPDATE 2</strong> </p> <p>For the new 'uppercaseFirstLetterOfName' transient property, add a new string attribute to the applicable entity in the model and check the "transient" box.</p> <p>There are a few ways to implement the getter. If you are generating/creating subclasses, then you can add it in the subclass's implementation (.m) file.</p> <p>Otherwise, you can create a category on NSManagedObject (I put this right at the top of my view controller's implementation file, but you can split it between a proper header and implementation file of its own):</p> <pre><code>@interface NSManagedObject (FirstLetter) - (NSString *)uppercaseFirstLetterOfName; @end @implementation NSManagedObject (FirstLetter) - (NSString *)uppercaseFirstLetterOfName { [self willAccessValueForKey:@"uppercaseFirstLetterOfName"]; NSString *aString = [[self valueForKey:@"name"] uppercaseString]; // support UTF-16: NSString *stringToReturn = [aString substringWithRange:[aString rangeOfComposedCharacterSequenceAtIndex:0]]; // OR no UTF-16 support: //NSString *stringToReturn = [aString substringToIndex:1]; [self didAccessValueForKey:@"uppercaseFirstLetterOfName"]; return stringToReturn; } @end </code></pre> <p>Also, in this version, don't forget to pass 'uppercaseFirstLetterOfName' as the sectionNameKeyPath: </p> <pre><code>NSFetchedResultsController *aFetchedResultsController = [[NSFetchedResultsController alloc] initWithFetchRequest:fetchRequest managedObjectContext:managedObjectContext sectionNameKeyPath:@"uppercaseFirstLetterOfName" // this key defines the sections cacheName:@"Root"]; </code></pre> <p>And, to uncomment <code>tableView:titleForHeaderInSection:</code> in the UITableViewDataSource implementation: </p> <pre><code>- (NSString *)tableView:(UITableView *)tableView titleForHeaderInSection:(NSInteger)section { id &lt;NSFetchedResultsSectionInfo&gt; sectionInfo = [[fetchedResultsController sections] objectAtIndex:section]; return [sectionInfo name]; } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POHow to use the first character as a section name
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USgerry3
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow to use the first character as a section name
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI tried putting name in as the `sectionNameKeyPath` but ended up with a section for each name returned. I got as many sections as there were names, each section with only one entry (the name).
      singulars
      1. PO
      1. USnevan king
    2. COYou might not have things set up properly. Give the answer another read. It works as advertised.
      singulars
      1. PO
      1. USAlex Reynolds
    3. COI don't believe that answer 'works' per se, I don't know why the responder acted as if it was a miracle to use the first name as a key path.
      singulars
      1. PO
      1. USrefulgentis
 

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