StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
9352241
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-02-19T19:06:00.650
FavoriteCount
0
LastActivityDate
2012-02-19T19:06:00.650
LastEditDate
LastEditorUserId
0
OwnerUserId
97337
ParentId
9352070
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
The best solution usually is to move this kind of logic into a model object like <code>MYConfiguration</code>. That way you can query <code>MYConfiguration</code> with explicit methods, and never directly access the <code>NSDictionary</code>. Regarding the name of that file, there are many approaches to abstracting it, depending on how much reuse you really need (it is possible to go overboard here). First is the constant. In <code>MYConfiguration.m</code>, you can put a private constant like this: <pre><code>static NSString * const kConfigurationFileBaseName = @"Config"; </code></pre> You can also have a method that returns the path: <pre><code>- (NSString *)pathToConfigurationFile { return [[NSBundle mainBundle] pathForResource:kConfigurationFileBaseName ofType:@"plist"]; } </code></pre> It's not uncommon to hard-code the name of the file directly in <code>pathToConfigurationFile</code> rather than having a constant. Constants often are only needed in cases where the value is used more than once. If a given constant only appears one time, then moving the value elsewhere can sometimes make the code harder to understand. These are just guidelines, not rules. If you need the constant itself to be publicly available, then you declare it this way in <code>MYConfiguration.h</code>: <pre><code>extern NSString * const kMYConfigurationFileBaseName; </code></pre> and then define it in .m: <pre><code>NSString * const kMYConfigurationFileBaseName = @"Config"; </code></pre> But the key in all of this is that you define these constants in a header related to the use of the constant. You don't create some central "MYGlobals" dumping ground for everything.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POBest practice to store constants for file names and property list names
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USRob Napier
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POBest practice to store constants for file names and property list names
 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
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
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.