On Tue, Oct 15, 2002 at 04:50:35PM -0700, Scott wrote:
When I use DBD::Oracle 1.12 with DBI 1.30 (I also saw this on
1.06/1.15) I see two parse_calls for every execute on all selects.
Update/insert/delete just have 1 parse/execute. I have a simple test
script.
#!/usr/local/bin/perl -w
--- --
1 10
Mark
-Original Message-
From: Tim Bunce [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, October 16, 2002 3:51 AM
To: Scott
Cc: [EMAIL PROTECTED]
Subject: Re: Two Oracle parse calls for each execute
On Tue, Oct 15, 2002 at 04:50:35PM -0700
Message-
From: Mark Dedlow [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, October 16, 2002 11:45 AM
To: Tim Bunce; Scott
Cc: [EMAIL PROTECTED]
Subject: RE: Two Oracle parse calls for each execute
Scott,
Something about your setup. Don't know what. Here's what I get
on Oracle 8.1.7.1
On Wed, October 16 11:51 +0100, Tim Bunce wrote:
Try:
my $sth = $dbh-prepare(SELECT 1 FROM dual, { ora_check_sql = 0 });
Thanks, that did the trick. Thanks also for the detailed explanation
and links.
I believe the parse at execute time is fundamentally an Oracle bug
(and/or isn't a full
When I use DBD::Oracle 1.12 with DBI 1.30 (I also saw this on
1.06/1.15) I see two parse_calls for every execute on all selects.
Update/insert/delete just have 1 parse/execute. I have a simple test
script.
#!/usr/local/bin/perl -w
use strict;
use DBI;
my $dbh = DBI-connect(dbi:Oracle:db,
