The Class::DBI docs aren't especially clear on this but
might_have relationships have to have identical primary keys in both tables. This makes a
has_a relationship your only option since the
Author table naturally doesn't have a primary key of
articleId.
If you'd like to have the functionality you're describing, you could do something like the following (quite untested):
package MPDatabase::Article;
# ... set up table ...
__PACKAGE__->has_a(authorId => 'MPDatabase::Author');
{
no strict 'refs';
foreach my $m(MPDatabase::Author->columns()){
# keep from overriding existing methods...
next if __PACKAGE__->can($m);
# deploy shortcut sub
*{$m} = sub {
my $obj = shift;
return $obj->authorId->$m(@_);
};
}
}
Incidentally, I've found
might_have relationships to be of rather limited use.
-- Brian
UPDATE: tweaked method detection
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.