StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
13449982
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-11-19T08:23:10.080
FavoriteCount
0
LastActivityDate
2012-11-19T08:23:10.080
LastEditDate
LastEditorUserId
0
OwnerUserId
1700258
ParentId
13448355
PostTypeId
2
Score
-1
ViewCount
0
LastEditorDisplayName
text
Body
So after 1 hour of brainstorming..I have come to the conclusion that in the multi dimensional hashes, the dup generates the same object_id for each key which is in turn referring to the hash whereas in the single dimensional hash, the object_ids are similar initially but when we make any changes to the object the Ruby would assign new object_id to the hash keys.. Look at the following code <pre><code>h = { :a => "a", :b => "b" } # => {:a=>"a", :b=>"b"} h_clone = h.dup #=> {:a=>"a", :b=>"b"} h.object_id #=> 73436330 h_clone.object_id #=> 73295920 h[:a].object_id #=> 73436400 h_clone[:a].object_id #=> 73436400 h[:b].object_id #=> 73436380 h_clone[:b].object_id #=> 73436380 h_clone[:b] = "New B" #=> "New B" h_clone[:b].object_id #=> 74385280 h.object_id #=> 73436330 h_clone.object_id #=> 73295920 h[:a].object_id #=> 73436400 h_clone[:a].object_id #=> 73436400 </code></pre> Look the following code for the multidimensional array <pre><code>h = { :one => { :a => "a", :b => "b" } } #=> {:one=>{:a=>"a", :b=>"b"}} h_copy = h.dup #=> {:one=>{:a=>"a", :b=>"b"}} h_copy.object_id #=> 80410620 h.object_id #=> 80552610 h[:one].object_id #=> 80552620 h_copy[:one].object_id #=> 80552620 h[:one][:a].object_id #=> 80552740 h_copy[:one][:a].object_id #=> 80552740 h[:one][:b].object_id #=> 80552700 h_copy[:one][:b].object_id #=> 80552700 h_copy[:one][:b] = "New B" #=> "New B" h_copy #=> {:one=>{:a=>"a", :b=>"New B"}} h #=> {:one=>{:a=>"a", :b=>"New B"}} h.object_id #=> 80552610 h_copy.object_id #=> 80410620 h[:one].object_id #=> 80552620 h_copy[:one].object_id #=> 80552620 h[:one][:b].object_id #=> 81558770 h_copy[:one][:b].object_id #=> 81558770 </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POdup gives different results when hash is one vs. two dimensions
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USAditya Kapoor
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POdup gives different results when hash is one vs. two dimensions
 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
 VTAcceptedByOriginator
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTDownMod
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.