StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
4264327
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-11-24T07:20:52.930
FavoriteCount
0
LastActivityDate
2010-12-09T11:36:32.510
LastEditDate
2017-05-23T10:33:05.973
LastEditorUserId
-1
OwnerUserId
366904
ParentId
4264276
PostTypeId
2
Score
4
ViewCount
0
LastEditorDisplayName
text
Body
In general, you probably want to catch exceptions at the lowest possible level in your code. The closer they're handed relative to where the exception occurs, the better chance that you have to fix the problem that caused them. If you can't take any corrective action at this level that has a hope of fixing the problem causing the exception, you should not be handling it at all. Just let the exception bubble up, and handle it globally like you want. That being said, if you've have handled the exception at a lower level, the only way you're going to be able to catch it at a higher level is if you <a href="http://msdn.microsoft.com/en-us/library/1ah5wsex(v=VS.100).aspx" rel="nofollow noreferrer">rethrow it</a> from the <code>Catch</code> block at the lower level. So, for example: <pre><code>try { //your code } catch (SomeException e) { //take any relevant handling measures //rethrow the exception throw; } </code></pre> Of course, this would technically mean that the exception is unhandled by this Try/Catch block at the lower level, but that's the only way you're going to have anything to catch at a higher level. For more information on rethrowing exceptions, see: <ul> <li><a href="https://stackoverflow.com/questions/113565/why-re-throw-exceptions">Why Re-throw Exceptions?</a></li> <li><a href="http://weblogs.asp.net/fmarguerie/archive/2008/01/02/rethrowing-exceptions-and-preserving-the-full-call-stack-trace.aspx" rel="nofollow noreferrer">http://weblogs.asp.net/fmarguerie/archive/2008/01/02/rethrowing-exceptions-and-preserving-the-full-call-stack-trace.aspx</a></li> <li><a href="http://msdn.microsoft.com/en-us/library/xhcbs8fz.aspx" rel="nofollow noreferrer">http://msdn.microsoft.com/en-us/library/xhcbs8fz.aspx</a></li> </ul>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POCatching handled exceptions
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USCommunity
UserOwnerUserId
1. USCody Gray
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.