RE: RaiseError sticks with statement handle??

2002-10-24 Thread Mark Dedlow
$sth4->execute or die $DBI::err; $sth5->execute or die $DBI::err; }; Thanks again all, Mark > -Original Message- > From: Stephen Clouse [mailto:stephenc@;theiqgroup.com] > Sent: Wednesday, October 23, 2002 9:56 PM > To: Mark Dedlow > Cc: Dbi-Users > Subject: Re:

RaiseError sticks with statement handle??

2002-10-23 Thread Mark Dedlow
RaiseError appears to be saved per statement handle and not changeable for the execution of a given statement once the statement has been prepared. Here's an example: $dbh = DBI->connect("dbi:Oracle:$db", $user, $pw, {PrintError=>0}); # before prepare, set RaiseError "off" $dbh->{RaiseErro

RE: Two Oracle parse calls for each execute

2002-10-16 Thread Mark Dedlow
Scott, Something about your setup. Don't know what. Here's what I get on Oracle 8.1.7.1. $c = $dbh->prepare('select 1 from dual', { ora_check_sql => 0}); for (1..10) { $c->execute } SQL>select parse_calls, EXECUTIONS from v$sqlarea where SQL_TEXT = 'select 1 from dual' PARSE_CALLS EXECUTIONS

RE: bind var trailing blanks chopped on insert w/Oracle

2002-08-26 Thread Mark Dedlow
> >$c = $dbh->prepare( 'insert into ct (COL) values (?)'); > >$c->execute('bind '); > > > > The trailing blank doesn't make it to the db. Doing the functional > > equivalent using native oracle tools works correctly. > > > > Anyone know where this problem lies? > > It's because DBD:

bind var trailing blanks chopped on insert w/Oracle

2002-08-26 Thread Mark Dedlow
Using oracle 8.1.7, perl 5.6.1, DBD::Oracle 1.12. When I do an insert like this below on CT.COL, a varchar2(10): $c = $dbh->prepare( 'insert into ct (COL) values (?)'); $c->execute('bind '); The trailing blank doesn't make it to the db. Doing the functional equivalent using native oracl