The cleanest way is to NOT do any explicit error handling. It may be better to handle your exceptions in one place, using "eval" and Exception::Class::DBI. So when you connect, you can pass this: 
...
RaiseError  => 1,
HandleError => Exception::Class::DBI->handler,
...

[download]
Now, if any error occurs, an exception will be thrown, and you can catch that via: 
eval {
  # if I fail, I will let you know
  $dbh->do("evil query"); 
};

my $ex = undef;

if ( $ex = Exception::Class::DBI->caught() ) {
   # log error in $ex->errstr
   # show users a general error screen
}

[download]
This should also take care of any "connect" trouble.
In general, and totally IMHO, checking for return of every db statement is evil ;)

In reply to Re: error catching by DreyT
in thread error catching 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.