in reply to DBI dots

update: hehehe I absent-mindedly fixed the dbh/sth error while reformatting this code and didn't even notice it : ) I also just dropped in the $sth = to make it reflect what it would really be like...

Should work. try running the code with some error checks to sniff out the real problem like:

$sth = $dbh->prepare('INSERT INTO tablename SET value=?') or die ("Couldn't prepare statement: ", $dbh->errstr); $sth->execute('hello.world') or die ("Couldn't execute statement: ", $sth->errstr);

"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: DBI dots
by merlyn (Sage) on Oct 23, 2000 at 20:32 UTC
    I find setting RaiseError should be nearly mandatory for DBI. Either during connect:
    $dhb = DBI->connect($dbi, $user, $pass, { RaiseError => 1 });
    Or after the fact with the magic tied hash interface:
    $dbh->{RaiseError} = 1;
    Then you get an automatic die for each error return from DBI. Very cool.

    -- Randal L. Schwartz, Perl hacker

      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

        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 :)