Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Mailing Lists -> Oracle-L -> RE: ora_check_sql in DBD::oracle
Figures. I thought I learned something new today. Turns out that I just
re-learned something I forgot:
http://www.mail-archive.com/dbi-users@perl.org/msg13613.html
Thanks for the reminder! :) But now I have to find something else new to learn today...
Rich
Rich Jesse System/Database Administrator rich.jesse_at_qtiworld.com Quad/Tech International, Sussex, WI USA
-----Original Message-----
From: Mladen Gogala [mailto:mladen_at_wangtrading.com]
Sent: Thursday, February 05, 2004 12:51 PM
To: Multiple recipients of list ORACLE-L
Subject: ora_check_sql in DBD::oracle
In private communication with Cary Millsap, I was warned about the undocumented DBI handle attribute called "ora_check_sql" which was defaults to "1" and, oracle versions 8 and above, causes oracle to parse each statement twice ($sth=$dbh->prepare() is the first parse and 4sth->execute() was the second). On 1/27/2004. Tim Bunce delivered the new DBD::Oracle v1.15 and in the documentation one can find the following text:
If 1 (default), force SELECT statements to be described in prepare (). If 0, allow SELECT statements to defer describe until execute(). (OCI8 and later only.)
See "Prepare postponed till execute" for more information.
When I did the unthinkable and read the documentation (I know, real DBA is not supposed to read the documentation, but learn by osmosis) I remembered the correspondence with Cary and decided to publish it for the rest of the good, hard hacking, perl folks.
-- Archives are at http://www.freelists.org/archives/oracle-l/ FAQ is at http://www.freelists.org/help/fom-serve/cache/1.htmlReceived on Thu Feb 05 2004 - 14:01:02 CST
-----------------------------------------------------------------
![]() |
![]() |