btrott mentioned that RaiseError is the recommended way to
check for errors but that you could alternatively check the
error return value for each DBI method call. Here's subtle
case where not using RaiseError can bite you:
while ($sth->fetch) {
print join("\t", $id, $name, $phone), "\n";
}
On the face of it, this will repeatedly call fetch until
there is nothing more to fetch. In fact, fetch will return
undef either when all rows have been fetched
or when there was an error. Here's a couple of
cases where fetch might successfully return a number of
rows then return undef for an error:
- you selected a calculated value (eg: total/count) which
caused a divide by zero error
- one of your columns is a long text field that exceeds
the default buffer size (LongReadLen) and because you left
the LongTruncOK option at default, it throws an error
In each case, you might see some output and mistakenly
believe you'd seen all matching rows. The moral - always
set RaiseError and wrap DBI calls using eval
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.