StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
17328601
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2013-06-26T19:15:18.973
FavoriteCount
0
LastActivityDate
2013-06-26T19:15:18.973
LastEditDate
LastEditorUserId
0
OwnerUserId
1521179
ParentId
17327636
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
What you want is very much like a trait (or in Perl: a role). Traits are a relatively recent addition to object oriented systems. They are like interfaces in that they can require an inheriting class to implement certain methods, but they are like a abstract superclass in that they can provide certain methods themselves. The Moose object system allows roles. A class can be declared <code>with</code> a certain role. Here your example written with <code>MooseX::Declare</code>: <pre><code>use MooseX::Declare; role Story::StoryTeller{ requires 'specifics'; method tellStory() { print "Once upon a time "; $self->specifics(); } } class Story::Story1 with Story::StoryTeller { method specifics() { print " there was a dragon\n"; } } class Story::Story2 with Story::StoryTeller { method specifics() { print " there was a house\n"; } } my $story1 = Story::Story1->new(); my $story2 = Story::Story2->new(); #Once upon a time there was a dragon. $story1->tellStory(); #Once upon a time there was a house. $story2->tellStory(); </code></pre> This isn't inheritance: <code>$story1->isa("Story::StoryTeller")</code> is false, but it does this role: <code>$story1->DOES("Story::StoryTeller")</code> is true. For every class that <code>DOES</code> a certain role, an instance of that class <code>can</code> all methods of the role. Therefore, <code>$story1->can("tellStory")</code> is true, and in reverse for every <code>Story::StoryTeller</code> instance, <code>$instance->can("specifics")</code> will be true. A role cannot be instantiated on its own.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POCalling a known subclass function from superclass?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USamon
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. This table or related slice is empty.
CommentsPostId
1. COThanks for the info.
 singulars
 PostPostId
 PO
 UserUserId
 USjohn doe

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.