To the experienced user, RaiseError is a good thing, and as you say, it does force you to wrap things into eval loops to handle errors. However, newer programmers may forget to wrap the DBI calls in evals, or will write several lines of DBI code that don't fail to work, and then be completely confused when something small changes and their program dies, and they'll be wondering what went wrong. I'd rather see people not used to DBI or perl in general use the "or die" approach, such that they understand that every "prepare" and "execute" statment in DBI should be checked for errors. Once they've understood that, then moving them on to RaiseError and eval's are a good thing. But again, IMO as well.
Dr. Michael K. Neylon - firstname.lastname@example.org
"You've left the lens cap of your mind on again, Pinky" - The Brain
"I can see my house from here!"
It's not what you know, but knowing how to find it if you don't know that's important
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||