StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
9315583
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
3
CommunityOwnedDate
CreationDate
2012-02-16T17:02:10.820
FavoriteCount
0
LastActivityDate
2012-02-16T18:57:07.960
LastEditDate
2012-02-16T18:57:07.960
LastEditorUserId
405017
OwnerUserId
405017
ParentId
9314941
PostTypeId
2
Score
9
ViewCount
0
LastEditorDisplayName
text
Body
Constant resolution always requires that you use <code>::</code>. Method invocation is idiomatically and usually a period (<code>.</code>), but <code>::</code> is also legal. This is not just true for so-called module methods, but for invoking any method on any object: <pre><code>class Foo def bar puts "hi" end end Foo.new::bar #=> hi </code></pre> It's not so much "syntax sugar" as it is simply alternative syntax, such as the ability to write <code>if</code> or <code>case</code> statements with either a newline, <code>then</code> and newline, or just <code>then</code>. It is specifically allowed because Ruby allows methods with the same name as a constant, and sometimes it makes sense to think that they are the same item: <pre><code>class Foo class Bar attr_accessor :x def initialize( x ) self.x = x end end def self.Bar( size ) Foo::Bar.new( size ) end end p Foo::Bar #=> Foo::Bar (the class) p Foo::Bar(42) #=> #<Foo::Bar:0x2d54fc0 @x=42> (instance result from method call) </code></pre> You see this commonly in Ruby in the <a href="http://nokogiri.org" rel="nofollow noreferrer">Nokogiri</a> library, which has (for example) the <a href="http://nokogiri.org/Nokogiri/XML.html" rel="nofollow noreferrer"><code>Nokogiri::XML</code></a> module as well as the <a href="http://nokogiri.org/Nokogiri.html#method-c-XML" rel="nofollow noreferrer"><code>Nokogiri.XML</code></a> method. When creating an XML document, many people choose to write <pre><code>@doc = Nokogiri::XML( my_xml ) </code></pre> You see this also in the <a href="http://sequel.rubyforge.org" rel="nofollow noreferrer">Sequel</a> library, where you can write either: <pre><code>class User < Sequel::Model # Simple class inheritance class User < Sequel::Model(DB[:regular_users]) # Set which table to use </code></pre> Again, we have a <a href="http://sequel.rubyforge.org/rdoc/classes/Sequel.html#method-c-Model" rel="nofollow noreferrer">method (Sequel.Model)</a> named the same as a <a href="http://sequel.rubyforge.org/rdoc/classes/Sequel/Model.html" rel="nofollow noreferrer">constant (Sequel::Model)</a>. The second line could also be written as <pre><code>class User < Sequel.Model(DB[:regular_users]) </code></pre> …but it doesn't look quite as nice.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POAccessing module methods with ::
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USPhrogz
UserOwnerUserId
1. USPhrogz
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POAccessing module methods with ::
 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
 VTUpMod
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.