I appreciate what you say about seperating the two. Its the real work class thats causing me troubles. If I understand you, my stupid code example using the do_all_the_real_work_that_page1_needs_done method is OK.
The question then is when you say
I usually use data handling classes just for handling data related to their namesake.
What do you do if you need code that handles data from 2 data handling classes? I can use a has_a relation for simple things but when things get more complex, I'm at a loss as to how to lay it all out.

I'm guess my problem is with basic OO design issues, I'm just looking for some clues as to how to lay it out.

In reply to Re^2: Best practices with Class::DBI by Anonymous Monk
in thread 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.