I've been fooling with using Class::DBI and CGI::Application.

I'm puzzled by what is the best way to deal with the framework of an application.

For example, say tables Music::Artist and Music::CD.
In CGI:Application I have a run mode say page1, that has to do processing on both tables.
The question is where does the code go. More percisly say a join, or a routine that gathers info from both tables.
It doesn't make sense to me that I should have things like Music::Artist->do_something buried in the Music::CD class. Do I stick all the real work in the base class Music::DBI? Then have all my run modes look like 

sub page1 {
    my $self = shift;
    Music::DBI->do_all_the_real_work_that_page1_needs_done;
}

[download]

In reply to Best practices with Class::DBI by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.