If an error did occur (maybe you don't have write permission for the current directory) most likely you will see the error message twice - once generated by the DBI/DBD code, and once from the die $@;
That can easily be prevented by doing:
$dbh->{PrintError} = 0;
The DBI manual recommends this:
If you turn "RaiseError" on then you'd normally turn "PrintError" off.
my $entries =
eval {
my $entries = 0;
my $sth = $dbh->prepare ($sql); #2
while (my ($name, $age) = each %people) { #3
++$entries if $sth->execute ($name, $age); #4
}
$dbh->commit (); #5
return $entries;
} or do {
my $err = $@;
eval {$dbh->rollback ()} or $err .= "\n Rollback processing
+failed!";
die $err;
};
That code will die if %people is empty. I'd write that as:
my $entries;
eval {
... stuff ...
$entries++ if $sth->execute($name, $age);
... more stuff ...
$dbh->commit;
1;
} or do {
... rollback and die ...
};
-
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.
|