Re^3: error catching

While I don't know what people normally do, the DBI default is for some unexplicable reason to not do that: (from the docs):

False. I was reading just above where you were reading.

By default, "DBI->connect" sets "PrintError" "on"

I agree that you still have to die() if your $sth fails, which I thought I had implied, but it will (by default) at least print the error on its own. The RaiseError is different and actually croak()s instead of just carp()ing.

Update, because it happens to be on my other monitor anyway, here's the relevant source [the comments are mine]:

        Carp::croak($msg) if $attr->{RaiseError}; # not default
        Carp::carp ($msg) if $attr->{PrintError}; # default
[download]

-Paul

Comment on Re^3: error catching Select or Download Code

Replies are listed 'Best First'.
Re^4: error catching by Joost (Canon) on Dec 20, 2006 at 01:02 UTC
You're right. I completely forgot about the difference between carp and croak, mainly because I personally only use croak (and also because I tend to think that exceptions are much more useful in this particular case). "What should it profit a man, if he should win a flame war, yet lose his cool?"	[reply]
Re^5: error catching by jettero (Monsignor) on Dec 20, 2006 at 01:05 UTC
I totally agree that raise error should be on by default... I'd rather have an `eval { $sth->execute }; if ($@) { ... }` where I don't want it to just die, ya know? But hey, I could just turn it on I suppose. I never remember is the main problem with that plan. -Paul	[reply] [d/l]