Thanks for idea, it is the solution, but:

With catch and croak you have to take care of context (AFAIK), something like this:

    sub selectrow_array {
        my $this = shift();
        my ( @ret, $ret );
        eval {
            if (wantarray)
            {

                # list
                @ret = $this->SUPER::selectrow_array(@_);
            }
            elsif ( defined(wantarray) ) {

                # scalar
                $ret = $this->SUPER::selectrow_array(@_);
            }
            else {

                # void - nonsense
                $this->SUPER::selectrow_array(@_);

            }
        };
        croak $@ if $@;
        return   if !defined wantarray;
        return wantarray ? @ret : $ret;
    }

[download]

The original error line is still being reported. Of course you can strip it with RE. But with $dbh->{'PrintError'} set the line still appear. 

DBD::mysql::db selectrow_array failed: Table 'devel.no_such_table' doe
+sn't exist at simple.pl line 17.
DBD::mysql::db selectrow_array failed: Table 'devel.no_such_table' doe
+sn't exist at simple.pl line 17.
 at simple.pl line 43

[download]

DBI actually "croaks" for itself. The error is reported on the boundary of user and DBI code. What I want is to tell DBI: this code is safe, don't report errors from here, go up in stack. I dont' know whether DBI has some rules for telling whether a call shouldn't generate errors as Carp have (inheritance is one the rules).

Maybe that the elegant, DBI specific solution, doesn't exist.

In reply to Re^2: How to subclass DBI and still have the errors reported in user code by roman
in thread How to subclass DBI and still have the errors reported in user code by roman

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.