There are two attributes of the database handle which control how DBI handles errors. RaiseError causes DBI to die on an error. PrintError causes DBI to warn on an error. The default has PrintError on and requires checking each call for errors. To save checking each call, it is common to turn RaiseError on and PrintError off.

It is possible to turn of both of them off. This is dangerous because it is easy to forget to check a database call and wonder why your code is not working. I suggest turning off error reporting only for the statements you know might fail: 

{
   local $dbh->{RaiseError} = 0;
   local $dbh->{PrintError} = 0;
   $dbh->do($sql_that_might_fail);
}

[download]

In reply to Re: Keeping Perl DBI Quiet by iburrell
in thread Keeping Perl DBI Quiet by cditty

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.