StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
11406309
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
3
CommunityOwnedDate
CreationDate
2012-07-10T03:44:55.797
FavoriteCount
0
LastActivityDate
2012-07-10T12:17:22.847
LastEditDate
2012-07-10T12:17:22.847
LastEditorUserId
8279
OwnerUserId
8279
ParentId
11402796
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
You can get a hint by inspecting the method: <pre><code>Decorator.instance_method(:class) # => #<UnboundMethod: Decorator(#<Module:0x00000102137498>)#class> </code></pre> The method's owner is <code>Decorator</code> but actually defined in <code>#<Module:0x00000102137498></code>. So there is an anonymous module that defines it. Interesting... let's look at: <pre><code>Decorator.ancestors # => [Decorator, Delegator, #<Module:0x00000102137498>, BasicObject] </code></pre> There's that module again, between <code>Delegator</code> and <code>BasicObject</code>. So <code>Delegator</code> doesn't directly derive from <code>BasicObject</code>. If you look at the source code in <code>lib/delegate.rb</code> you find: <pre><code>class Delegator < BasicObject kernel = ::Kernel.dup kernel.class_eval do [:to_s,:inspect,:=~,:!~,:===,:<=>,:eql?,:hash].each do |m| undef_method m end end include kernel # ... </code></pre> So a copy of the <code>Kernel</code> module is made, which doesn't have <code>to_s</code>, <code>inspect</code>, etc... but still has <code>class</code> and <code>instance_of?</code>. It's included in <code>Delegator</code> and that's where they come from. Note that <code>Object</code> inherits the same methods by including the <code>Kernel</code> module (but it includes the full module, of course): <pre><code>42.method(:class) # => #<Method: Fixnum(Kernel)#class> </code></pre> This is stated in the <a href="http://www.ruby-doc.org/core-1.9.3/Object.html" rel="nofollow"><code>Object</code> doc</a>: <blockquote> Object mixes in the Kernel module, making the built-in kernel functions globally accessible. Although the instance methods of Object are defined by the Kernel module, we have chosen to document them here for clarity. </blockquote>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PODelegator through BasicObject transparency
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USMarc-André Lafortune
UserOwnerUserId
1. USMarc-André Lafortune
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. PODelegator through BasicObject transparency
 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
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId

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.