StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
737902
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2009-04-10T14:59:08.427
FavoriteCount
0
LastActivityDate
2009-04-10T16:38:11.683
LastEditDate
2009-04-10T16:38:11.683
LastEditorUserId
66372
OwnerUserId
66372
ParentId
737835
PostTypeId
2
Score
16
ViewCount
0
LastEditorDisplayName
text
Body
You don't need to have the type in the line to make it more readable, its a matter of personal preference. I do like the var variation: <pre><code>var currentTab = tabCaseNotes.TabPages[e.Index]; var itemRect = tabCaseNotes.GetTabRect(e.Index); var fillBrush = new SolidBrush(Color.Linen); var textBrush = new SolidBrush(Color.Black); var sf = new StringFormat { Alignment = StringAlignment.Center, LineAlignment = StringAlignment.Center }; </code></pre> Update: I will add a controversial view on it. Unless I am reading code from a book, I don't usually care what's the specific type for understanding some lines of code I am reading. Consider the .GetTableRectangle(e.Index), for which you are not showing the code that operates on it: <pre><code>var itemRect = tabCaseNotes.GetTableRectangle(e.Index); //do some operations on itemRect </code></pre> While reading that specific code I will get more to understand it from the operations on itemRect than from its type. It can be IRectangle, Rectangle, CustomRectangle, and still won't say much on what the code is doing with it. Instead I care more for the itemRect.Height, itemRect.Width or itemRect.GetArea() along with the logic involved. Update 2: As others have pointed out you can turn it off. Make sure to keep the team with the same practices, or you will probably end up with making changes one way or the other each time a different person touches the code. See: <a href="http://www.jetbrains.com/resharper/features/codeTemplate.html" rel="noreferrer">http://www.jetbrains.com/resharper/features/codeTemplate.html</a>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POReSharper and var
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USeglasius
UserOwnerUserId
1. USeglasius
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POReSharper and var
 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
 VTUpMod
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.