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
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|