StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
5241196
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
5
CommunityOwnedDate
CreationDate
2011-03-09T04:06:15.630
FavoriteCount
0
LastActivityDate
2011-03-09T04:06:15.630
LastEditDate
LastEditorUserId
0
OwnerUserId
242321
ParentId
4649423
PostTypeId
2
Score
218
ViewCount
0
LastEditorDisplayName
text
Body
Switch cases should almost always have a <code>default</code> case. Reasons to use a <code>default</code> 1.To 'catch' an unexpected value <pre><code>switch(type) { case 1: //something case 2: //something else default: // unknown type! based on the language, // there should probably be some error-handling // here, maybe an exception } </code></pre> 2. To handle 'default' actions, where the cases are for special behavior. You see this a LOT in menu-driven programs and bash shell scripts. You might also see this when a variable is declared outside the switch-case but not initialized, and each case initializes it to something different. Here the default needs to initialize it too so that down the line code that accesses the variable doesn't raise an error. 3. To show someone reading your code that you've covered that case. <pre><code>variable = (variable == "value") ? 1 : 2; switch(variable) { case 1: // something case 2: // something else default: // will NOT execute because of the line preceding the switch. } </code></pre> This was an over-simplified example, but the point is that someone reading the code shouldn't wonder why <code>variable</code> cannot be something other than 1 or 2. <hr> The only case I can think of to NOT use <code>default</code> is when the switch is checking something where its rather obvious every other alternative can be happily ignored <pre><code>switch(keystroke) { case 'w': // move up case 'a': // move left case 's': // move down case 'd': // move right // no default really required here } </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POShould switch statements always contain a default clause?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USVanwaril
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POShould switch statements always contain a default clause?
 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.