I usually use RaiseError as it allows me not to check error condition after every DB operation. If I don't want script to die after error I always can catch exception. Compare these examples:

$dbh->do(...) or handle_error();
$dbh->do(...) or handle_error();
$dbh->do(...) or handle_error();
$dbh->do(...) or handle_error();
[download]

or

eval {
    $dbh->do(...);
    $dbh->do(...);
    $dbh->do(...);
    $dbh->do(...);
}
if($@) {
    handle_error();
}
[download]

But sometimes you have to mix db operations with others and you want to be able to distinct db errors from lets say IO errors. In this case RaiseError may be not so convenient. E.g.:

use Fatal qw(open);

eval {
    $dbh->do(...);
    open my $fd, "<", $file;
    # some other stuff
}
if($@) {
    # and here we can't say if it was DBI problem or open
}
[download]

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&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.