StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
9227893
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-02-10T12:37:24.183
FavoriteCount
0
LastActivityDate
2012-02-10T13:12:42.543
LastEditDate
2012-02-10T13:12:42.543
LastEditorUserId
955617
OwnerUserId
955617
ParentId
9227856
PostTypeId
2
Score
4
ViewCount
0
LastEditorDisplayName
text
Body
In order to understand the order of operations you need to remember that the cast will be applied to the object to the right but the rules that affect WHEN it is applied depends on MSDN's <a href="http://msdn.microsoft.com/en-us/library/aa691323%28v=vs.71%29.aspx" rel="nofollow">Operator precedence and associativity</a> <pre><code>(Dictionary<String, String>)((Object[])e.Result)[1]; </code></pre> Becomes <pre><code>Object[] cast1 = (Object[]) e.Result; </code></pre> The cast operation is grouped into the "Unary Operators" category which is a lower priority than the indexer - [] which is in the "Primary expressions" category. In the original line - The ()'s are necessary around the cast: ((Object[])e.Result) because the indexer - [] is applied immediately to the object on the left as the first priority. Without the surrounding ()'s the cast would be applied AFTER the indexer and since e.Result is (likely?) of type object this will fail at compile time. Without the ()'s the line would look like: <pre><code>(Object[])e.Result[1] </code></pre> Which would not be valid. <pre><code>((Object[])e.Result)[1] </code></pre> ensures that e.Result is cast to type Object[] first, and then the indexer is used to access the first element. The second cast turns the first element of the casted object[] (in my example cast 1) into a Dictionary <pre><code>Dictionary<String, String> cast2 = (Dictionary<String, String>) cast1[1]; </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POC# multi casting example
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USrobowahoo
UserOwnerUserId
1. USrobowahoo
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.