StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
10286295
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
5
CommunityOwnedDate
CreationDate
2012-04-23T18:39:57.830
FavoriteCount
0
LastActivityDate
2012-04-23T18:39:57.830
LastEditDate
LastEditorUserId
0
OwnerUserId
8003
ParentId
10216256
PostTypeId
2
Score
7
ViewCount
0
LastEditorDisplayName
text
Body
I might get raked over the coals for this, but when in doubt, lie :) <pre><code>package MyMoose; use strict; use warnings; use Carp 'confess'; sub import { my $caller = caller; eval <<"END" or confess("Loading MyMoose failed: $@"); package $caller; use Moose; use MooseX::StrictConstructor; use MooseX::FollowPBP; 1; END } 1; </code></pre> By doing that, you're evaling the use statements into the calling package. In other words, you're lying to them about what class they are used in. And here you declare your person: <pre><code>package MyPerson; use MyMoose; has first_name => ( is => 'ro', required => 1 ); has last_name => ( is => 'rw', required => 1 ); 1; </code></pre> And tests! <pre><code>use lib 'lib'; use MyPerson; use Test::Most; throws_ok { MyPerson->new( first_name => 'Bob' ) } qr/\QAttribute (last_name) is required/, 'Required attributes should be required'; throws_ok { MyPerson->new( first_name => 'Billy', last_name => 'Bob', what => '?', ); } qr/\Qunknown attribute(s) init_arg passed to the constructor: what/, '... and unknown keys should throw an error'; my $person; lives_ok { $person = MyPerson->new( first_name => 'Billy', last_name => 'Bob' ) } 'Calling the constructor with valid arguments should succeed'; isa_ok $person, 'MyPerson'; can_ok $person, qw/get_first_name get_last_name set_last_name/; ok !$person->can("set_first_name"), '... but we should not be able to set the first name'; done_testing; </code></pre> And the test results: <pre><code>ok 1 - Required attributes should be required ok 2 - ... and unknown keys should throw an error ok 3 - Calling the constructor with valid arguments should succeed ok 4 - The object isa MyPerson ok 5 - MyPerson->can(...) ok 6 - ... but we should not be able to set the first name 1..6 </code></pre> Let's keep this our little secret, shall we? :)
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POUse a single module and get Moose plus several MooseX extensions
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USOvid
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

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.