StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
682659
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-03-25T17:39:26.380
FavoriteCount
0
LastActivityDate
2014-02-12T21:19:47.823
LastEditDate
2014-02-12T21:19:47.823
LastEditorUserId
2688
OwnerUserId
2688
ParentId
682635
PostTypeId
2
Score
20
ViewCount
0
LastEditorDisplayName
bdukes
text
Body
<a href="http://msdn.microsoft.com/en-us/library/ms229012.aspx" rel="noreferrer">MSDN on naming events</a>: <blockquote> Events always refer to some action, either one that is happening or one that has occurred. Therefore, as with methods, events are named with verbs, and verb tense is used to indicate the time when the event is raised. √ DO name events with a verb or a verb phrase. Examples include <code>Clicked</code>, <code>Painting</code>, <code>DroppedDown</code>, and so on. √ DO give events names with a concept of before and after, using the present and past tenses. For example, a close event that is raised before a window is closed would be called <code>Closing</code>, and one that is raised after the window is closed would be called <code>Closed</code>. X DO NOT use "Before" or "After" prefixes or postfixes to indicate pre- and post-events. Use present and past tenses as just described. √ DO name event handlers (delegates used as types of events) with the "EventHandler" suffix, as shown in the following example: <pre><code>public delegate void ClickedEventHandler(object sender, ClickedEventArgs e); </code></pre> √ DO use two parameters named sender and e in event handlers. The sender parameter represents the object that raised the event. The sender parameter is typically of type <code>object</code>, even if it is possible to employ a more specific type. √ DO name event argument classes with the "EventArgs" suffix. </blockquote> So, events should be named with a verb or verb phrase. Instead of <code>OnSomething</code>, use <code>Something</code>, assuming that <code>Something</code> is actually a verb, like <code>Close</code>, <code>Click</code>, or <code>ManagedPiplelineAbandoning</code> and <code>ManagedPiplelineAbandoned</code>. The delegate for an event should be named with the <code>EventHandler</code> suffix, giving <code>CloseEventHandler</code>, <code>ClickEventHandler</code>, <code>ManagedPiplelineAbandoningHandler</code>, etc. For delegates that aren't related to an event, use a noun, like <code>EventProcessor</code> or <code>ItemRetriever</code>, while an instance of that delegate is a verb, like <code>processEvent</code> or <code>retrieveItem</code>. The casing of your delegate reference should be camel, unless the reference is not private. I can't think of a case where you'd have a non-private delegate field, though. However, since it is suggested to use the conventional event handler signature (i.e. <code>object sender, EventArgs e)</code>), you should <a href="http://msdn.microsoft.com/en-us/library/ms182178.aspx" rel="noreferrer">use a generic event handler</a> instead of defining your own. That is, your event would be defined as something like this: <pre><code>event EventHandler<SomethingEventArgs> Something; </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PONaming, declaring and defining delegates and events conventions
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USbdukes
UserOwnerUserId
1. USbdukes
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
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.