StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
20641808
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-12-17T18:21:56.667
FavoriteCount
0
LastActivityDate
2013-12-17T18:21:56.667
LastEditDate
LastEditorUserId
0
OwnerUserId
2316200
ParentId
20641511
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
Naming is pretty subjective, but in my opinion there's 2 things to follow to have "good names". <ol> <li>Be precise. </li> <li>Follow the <a href="http://en.wikipedia.org/wiki/Principle_of_least_astonishment" rel="nofollow">principle of least astonishment</a>.</li> </ol> These two principles are important for maintenance; if you have a bunch of methods named <code>GetData</code>, people won't know what to expect and will waste time reading the doc to find the appropriate overload. You also want to have names representing the level of abstraction you're at. So let's say you want to get some entities named <code>Page</code>. At the DAO level it could easily be <code>public DataTable GetPagesTable();</code>, because you're dealing with tables. At a higher level of abstraction, with the List, you could change it to <code>public List GetPages();</code> (Removed Table from the name). You're far from the database, so the names should reflect that. If you're passing an object or ID, say it clearly in the method name to avoid any surprises, like <code>public DataTable GetPagesFromId(int id);</code> From your examples, I would probably end up with something like that : <pre><code>public DataTable Get<TableName>Table() - returns the data from a given table public List Get<ObjectName>s() - returns the data in the form of List of objects public DataSet Get<ComposedObjectName>() - returns the data when there are multiple data tables associated with queries public objectx Get<ObjectName>(objecty) - returns selected object public DataSet Get<ObjectName>AsMasterChild(objecty) - returns selected object (ex: in case of master-child) </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PONaming Convention - Method name for getting data
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USPierre-Luc Pineault
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
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
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.