StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
2045335
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-01-11T22:12:14.167
FavoriteCount
0
LastActivityDate
2010-01-11T22:12:14.167
LastEditDate
LastEditorUserId
0
OwnerUserId
190807
ParentId
2044263
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
First of all, you need to use arrays for the top two levels of your data structure. Dictionaries are unordered so that makes it hard to use them as the data source for a table's format. It's fine to use them for the data for each record displayed in an individual cell. To use the dictionaries as table format data, you have to store their keys to an array so that every key has a specific numerical index that the table can use to find the key. You will need something like the following in your UITabelViewDataSource class: <pre><code>@property(nonatomic, retain) NSArray *sectionNames; ... NSArray *sectionNames=[teams allKeys]; </code></pre> In your UITabelViewDataSource class you would need these methods: <pre><code>- (NSInteger)numberOfSectionsInTableView:(UITableView *)tableView{ return [self.sectionNames count]; } </code></pre> This returns the number of sections in the table which in your case represents the number of objects in your top level dictionary. <pre><code>- (NSInteger)tableView:(UITableView *)table numberOfRowsInSection:(NSInteger)section{ return [[teams valueForKey:[self.sectionNames objectAtIndex:section] count]; } </code></pre> This returns the number of rows within each section which in your case means the number of objects in each second level dictionary returned for the key stored in each sectionName element. <pre><code>- (NSString *)tableView:(UITableView *)tableView titleForHeaderInSection:(NSInteger)section{ return [self.sectionNames objectAtIndex:section]; } </code></pre> This returns the name that will be displayed for each section header which in your case is the key for each first level dictionary value. Unless you have a specific need to reference the sections by key, you should think about storing everything except the team data in arrays instead of dictionaries. It will make you tables easier to implement. 
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POAdding sections to a plist for Xcode for use in Cocoa touch Table View
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USTechZen
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POAdding sections to a plist for Xcode for use in Cocoa touch Table View
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. This table or related slice is empty.

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.