Adding
RaiseError => 1 to the
connect call might also work for you in which case you won't have to add
|| die ... after each call.
You also have the ability to change the behavior of die by installing a custom $SIG{__DIE__} handler:
$SIG{__DIE__} = sub {
print STDERR @_;
print STDOUT ...; # whatever you want
exit(1);
};
Just throwing some out some ideas/options.
Update: if RC-E represents some sort of context or scope that you want to report via STDOUT, you could use a localize global variable to remember what the current context is.
our $::error_context;
{
local $::error_context = "RC-E";
$dbh->prepare(...); # dbh call in the RC-E context
{
local $::error_context = "RC-F";
$dbh->whatever(...); # dbh call in the RC-F context
}
# back to context "RC-E"
...
}
Then the
SIG{__DIE__} handler can determine the context by inspecting
$::error_context.
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.