I would second the Singleton approach suggested by others - the dbh isn't really an attribute of your objects, your just stashing it to pass around. You might as well provide a global point of access for objects if and when they need it.

It would also give you a logical place to put other generic DB related code, and could be quite easily integrated with your DBIx::Handy module: 

package DBIx::Handy;

my $dbh = undef;

sub get_instance
{
    my $class = shift;
    if($dbh == undef){
        $dbh = ...
    }
    return $dbh;
}

...etc

[download]



time was, I could move my arms like a bird and...

In reply to Re: OOP design related question. by Ctrl-z
in thread OOP design related question. by techcode

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.