StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
14565250
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-01-28T15:24:40.820
FavoriteCount
0
LastActivityDate
2013-01-28T15:31:35.327
LastEditDate
2013-01-28T15:31:35.327
LastEditorUserId
263681
OwnerUserId
263681
ParentId
14565072
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
If the error codes can change from version to version, then no amount of work (or lack of it) is going to save you trouble of having to remap these somehow at some point. If you have exceptions for codes (or code ranges) then it's hardly going to be much more work than if you didn't have, when error codes do change (you're going to be rearranging what exceptions are thrown, just as you would have to be jiggling the messages around for one exception if you didn't have dedicated classes). Besides, in general practice, by .NET convention, you should create a dedicated exception class for specific exceptions that aren't aptly covered by BCL-provided exceptions (excluding use of the some in there that are meant for abstraction only). For some Microsoft input, consider <a href="http://msdn.microsoft.com/en-gb/library/vstudio/ms229014%28v=vs.100%29.aspx" rel="nofollow">this</a>: <blockquote> Applications and libraries should not use return codes to communicate errors. </blockquote> And <a href="http://msdn.microsoft.com/en-gb/library/vstudio/ms229021%28v=vs.100%29.aspx" rel="nofollow">this</a>: <blockquote> Consider throwing existing exceptions residing in the System namespaces instead of creating custom exception types. </blockquote> But, following the <a href="http://msdn.microsoft.com/en-us/library/vstudio/ms229014%28v=vs.100%29.aspx" rel="nofollow">Exception Design Guidelines</a>, <blockquote> [will] help ensure that you use the existing exceptions, where appropriate, and create new exceptions where they add value to your library. </blockquote> Stick to your guns.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POUsing more than one special exception class
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USGrant Thomas
UserOwnerUserId
1. USGrant Thomas
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POUsing more than one special exception class
 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
 VTAcceptedByOriginator
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.