Hi All,

In contrary to all documentation I was capable of, I wasn't able to catch a DBI error to replace it with another message.
I can get the error message into a varialbe, but cannot prevent DBI from displaying the error again.

Here's some sample code: 
use DBI;

my $dbh = DBI->connect("DBI:mysql:database=www;host=myhost.domain.com:
+3306;user=auser;password=apwd",
{RaiseError => 1, PrintError => 0});

my $sql = 'select wrong_col, correct_col from table limit 10';

my $hash_ref;

print "Trying HandleError (with RaiseError on):\n";
$hashref = $dbh->selectall_hashref($sql, 'filename', 
    {RaiseError => 1, PrintError => 1, HandleError => \&handle_error()
+}); 

print "Trying RaiseError and eval:\n";
eval{                    
    $hashref = $dbh->selectall_hashref($sql, 'filename', 
    {RaiseError => 1, PrintError => 0}); 
};
if ($@) {
        print "\tEval found: $@\n";
}

my $sth = $dbh->prepare($sql);

print "Trying Errstr:\n";
$sth->execute();
if ($dbh->errstr) {
    print "\tErrstr: " .$dbh->errstr . "\n";
}

sub handle_error { #
    my $error = shift;
    print "\tSub 'handle_error': $error\n";
    print "\tEnd sub\n";
}

[download]

As a result, I get: 

$ perl tester.pl
Trying HandleError (with RaiseError on):
        Sub 'handle_error':
        End sub
DBD::mysql::db selectall_hashref failed: Unknown column 'wrong_col' in
+ 'field list' at tester.pl line 11.
Trying RaiseError and eval:
DBD::mysql::db selectall_hashref failed: Unknown column 'wrong_col' in
+ 'field list' at tester.pl line 16.
Trying Errstr:
DBD::mysql::st execute failed: Unknown column 'wrong_col' in 'field li
+st' at tester.pl line 26.
        Errstr: Unknown column 'wrong_col' in 'field list'

- or - when redirecting STDERR:
$ perl tester.pl 2>/dev/null
Trying HandleError (with RaiseError on):
        Sub 'handle_error':
        End sub
Trying RaiseError and eval:
Trying Errstr:
        Errstr: Unknown column 'wrong_col' in 'field list'

[download]

Basically, the error message is printed to STDERR on all three tests, I was never able to prevent it.
Second, the error was caught by handle_error, but the error message was not handed over as it should be.
The third way worked OK, except that it did print the error message to STDERR...

What do I do/think wrong here?
Thanks for any hints,
Sven

In reply to DBI::mysql error handling by svenXY

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.