in reply to RE: Re: DBI dots
in thread DBI dots

well...

I do a bunch of stuff that is not really needed to succeed interms of what success is for the whole program. I don't know if I want every whine from the database to kill me off - especially if it's something as trivial as a disconnect or something like that.

"sometimes when you make a request for the head you don't
want the big, fat body...don't you go snickering."
                                         -- Nathan Torkington UoP2K a.k.a gnat

Replies are listed 'Best First'.
RE: RE: RE: Re: DBI dots
by lachoy (Parson) on Oct 23, 2000 at 21:00 UTC
    This may be true, but using {RaiseError} gets you into good habits, just like use strict does -- it might be painful at first, but after you get used to it you never have to worry about certain annoying little things again. This leaves your mind ready for certain annoying big things :)
[reply]
      Yes, and you can always use an eval {} block around a bunch of code, or a local value for RaiseError in a block.

      The default should still be die to require you to think about why something might break. Yes, it's like use strict.

      -- Randal L. Schwartz, Perl hacker

[reply]

        You're right, I was leaving too much unsaid. Even examples I post to the DBI list look like: 

         my ( $sth );
 eval {
   $sth = $dbh->prepare( qq/ select blech from blah / );
   $sth->execute;
 };
 if ( $@ ) {
   die "Something screwed up! Error: $@";
 }

 ...

        [download]

        That's how much I've drilled it into myself. I even dream in eval {} blocks! (Takes care of all those nasty nightmares...)

[reply]
[d/l]

In Section Seekers of Perl Wisdom