StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
19464623
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-10-19T09:44:36.237
FavoriteCount
0
LastActivityDate
2013-10-19T09:56:31.137
LastEditDate
2013-10-19T09:56:31.137
LastEditorUserId
691409
OwnerUserId
691409
ParentId
19464559
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
If you have an object of the class, it is only the information for one shop. The object describes one shop info. It is common use to write a class name that way, that it makes sense when using an object. Especially in method names and declaring variables it is clearer <pre><code>// CORRECT WAY - (UIAlertView *)calcualteSomething:(UIView I)view { UIView *newView = view; ... return [UIAlertView alertWith...]; } </code></pre> It would be very odd to use the plural form in my opinion (it seems like the single object is more than one!): <pre><code>// BAD IDEA - (UIAlertViews *)calcualteSomething:(UIViews *)view { UIViews *newView = view; ... return [UIAlertViews alertWith...]; } </code></pre> You can then easily use the object or test for the class and it makes sense too: <pre><code>[myObject isKindOfClass:[NSString class]] </code></pre> Here is the official link how you should write a name: <a href="https://developer.apple.com/library/mac/documentation/Cocoa/Conceptual/CodingGuidelines/Articles/NamingBasics.html#//apple_ref/doc/uid/20001281-BBCHBFAH" rel="nofollow">https://developer.apple.com/library/mac/documentation/Cocoa/Conceptual/CodingGuidelines/Articles/NamingBasics.html#//apple_ref/doc/uid/20001281-BBCHBFAH</a> And there you see, Apple always avoids using the plural form (NSString, NSArray, etc.). Of course the other way around it also makes sense, but then more for class methods etc. . Other popular languages also use singular form for classes. <hr> Some other good coding guidelines is from CocoaDevCentral <a href="http://cocoadevcentral.com/articles/000082.php" rel="nofollow">http://cocoadevcentral.com/articles/000082.php</a> <a href="http://cocoadevcentral.com/articles/000083.php" rel="nofollow">http://cocoadevcentral.com/articles/000083.php</a>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PONaming convention (Singular or plural name class)
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USBinarian
UserOwnerUserId
1. USBinarian
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. PONaming convention (Singular or plural name class)
 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
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
3. 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.