On Mon, Oct 11, 2004 at 08:54:46PM +0530, Mahadevan, Arun wrote: > Hi Tim, > > Just one more question. > > Can we modify the Oraperl.pm in DBD v1.15 and use it for our > application, and later migrate to the 1.16 version whenever that > happens?
Sure. > Will there be any licensing issues? Licensing, what licensing? :-) If you'd like a license you're welcome to send me a cheque and I'll send you a license by return of post ;-) Tim. > Also we are not able use the older DBD v 1.12 as it doesn't compile with > the Oracle 9i libraries. > > Thanks, > Arun > > -----Original Message----- > From: Tim Bunce [mailto:[EMAIL PROTECTED] > Sent: Monday, October 11, 2004 7:55 PM > To: Mahadevan, Arun > Cc: Tim Bunce; [EMAIL PROTECTED] > Subject: Re: Help needed - DBD::Oracle 1.15 > > On Mon, Oct 11, 2004 at 01:09:12PM +0530, Mahadevan, Arun wrote: > > Hi Tim, > > > > Thanks for the fix. > > > > When I went through the DBI documentation, it says "The AutoCommit and > > > PrintError attributes for each connection default to on". > > That doesn't (or rather shouldn't) apply to Oraperl. > > > Does this mean that we have to set both "AutoCommit" and "PrintError" > > to "off" explicitly in the new Oraperl.pm in order to get the old > behavior? > > Ah, I'd forgotten about AutoCommit. Yes, add AutoCommit=>0 to the fix > below. > > > Can we do this fix manually by directly modifying "Oraperl.pm" ? Is > > there any release with this fix already available? > > Not yet. It'll be in 1.16 whenever that's released. > > Tim. > > > -----Original Message----- > > From: Tim Bunce [mailto:[EMAIL PROTECTED] > > Sent: Saturday, October 09, 2004 2:02 AM > > To: Mahadevan, Arun > > Cc: [EMAIL PROTECTED] > > Subject: Re: Help needed - DBD::Oracle 1.15 > > > > On Fri, Oct 08, 2004 at 09:42:18PM +0530, Mahadevan, Arun wrote: > > > Hi, > > > > > > Recently we upgraded from DBD::Oracle v1.12 to DBD v1.15 as we had > > > to upgrade to Oracle 9i. > > > > > > But there is some functionality difference I observerd in ora_open() > > > > function. (We are using Oraperl emulation of Perl DBI). > > > > It's a bug in the Oraperl emulation. I changed it to not use the "old > > style" DBI connect arguments but in doing so forgot that the old-style > > > implicitly disabled PrintError. Sorry about that. > > > > I've appended the fix. > > > > Tim. > > > > --- Oraperl.pm (revision 442) > > +++ Oraperl.pm (working copy) > > @@ -94,7 +94,7 @@ > > local($SIG{'__WARN__'}) = sub { _warn($Oraperl::prev_warn, @_) }; > > # we now use the new style connect, since the old style is > > # deprecated > > - my $dbh = DBI->connect("dbi:Oracle:$system_id", $name, $password, > { > > }); > > + my $dbh = DBI->connect("dbi:Oracle:$system_id", $name, $password, > > > + { > > > > + PrintError => 0 }); > > return $dbh; > > } > > sub ora_logoff { > > > > > > >
