I believe you have misunderstood the advice: you combine the approaches, you don't replace one with the other.

You have to set $@ yourself by calling die in the normal way:

eval {
    $db->do($sql) or die $db->errstr();
    $db->commit();
}

if ($@) {
    warn "DB error: $@\n";
}
[download]

I believe this is what the RaiseError argument is designed to do: check to be sure each DBI call succeeds, or die.

In addition to what the anonymous monk has to say (I'll admit it, it was me, not logged in), take a look at the code that creates the DB handle in that example, where RaiseError is set to 1 (i.e. true). That means the die is automatically called on a DB error, so it's functionally equivalent to the code "AM" provided.

HTH

I mistrust all systematizers and avoid them. The will to a system shows a lack of integrity -- F. Nietzsche

I have RaiseError set to 1 so like you say, die is called automatically, which should set $@. Is that incorrect? If so, why do the examples not use a explicit die statement with the errstr method -- they, from what I can tell, are just using $@ .. the errstr method is not used at all.

--
notsoevil
--
Jeremiah 49:32 - And their camels shall be a booty. . .