What I'm doing is a step beyond that. I'm using Error (which implements a try-catch type system) and have the following code: 
   my $dbh = try {
      DBI->connect(
         $conn_string,
         $props{USER},
         $props{PWD},
         {
            PrintError => 0,
            RaiseError => 1,
         },
      )
   } otherwise {
      throw Error::Database -text => (
         $DBI::errstr
         || $@
         || "Unknown Error: '$conn_string'"
      );
   };

   $dbh->{HandleError} = sub { throw Error::Database -text => $DBI::er
+rstr };

   return $dbh;

[download]
I've defined Error::Database as such: 
package Error::Database;

######################################################################
+##########

use 5.6.0;

use strict;
use warnings;

######################################################################
+##########

# This is a baseclass I use for extending the standard Error class in 
+ways that don't matter here.
use Error::Base;
our @ISA = qw(Error::Base);

######################################################################
+##########

sub new
{
   my $class = shift;
   my $self = $class->SUPER::new(@_) || return undef;

   my $txt = $self->text;

   if ($txt =~ /text=([^=]+)./)
   {
      $self->{-text} = $1;
   }
   elsif ($txt =~ /Message String: (.*?)$/)
   {
      $self->{-text} = $1;
   }

   return $self;
}

1;

[download]
The reason for the regexes is I wanted to strip off meaningless guck to me and only giv eme the good stuff.

------
We are the carpenters and bricklayers of the Information Age.

Don't go borrowing trouble. For programmers, this means Worry only about what you need to implement.

Please remember that I'm crufty and crochety. All opinions are purely mine and all code is untested, unless otherwise specified.

In reply to Re4: DBI perpare_cached and statment handle gone bad by dragonchild
in thread DBI perpare_cached and statment handle gone bad by lhoward

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.