IIRC, you can stop this by setting the ora_check_sql statement
handle attribute to 0.
eg. my $sth = $dbh->prepare($sql,{ora_check_sql => 0 });
Jared
On Wed, 2003-07-30 at 05:52, Mark Buckle wrote:
>
>
> I've noticed that using a prepare/execute/fetch_xxxx cycle of operations
> appear to result in 2 parses happening. ( results obtained
> from tkprof ) Is this correct ? ie the parse count for the statement will
> be 2, the execute count 1, and the fetch count n.
>
> A second querstion is :-
> Is it possible to combine the parse and execute steps within the dbi ? So
> as to avoid 2 network round-trips. ( Yes I know
> we should parse once execute many but I'm trying to model a particular
> scenario here. )
>
> Thanks, Mark.
>
> And, I haven't been able to find anything in the docs that answers these
> questions.
>
>
>
>
>
> **************************************************************************************
> This e-mail may contain information that is privileged, confidential
> or otherwise protected from disclosure. It must not be used by, or
> its contents copied or disclosed to, persons other than the intended
> recipient. However, the contents of this e-mail may be intercepted,
> monitored or recorded by Insurance Technology Solutions Limited
> for the purposes of ensuring compliance with its policies and
> procedures. Any liability (in negligence or otherwise) arising from any
> third party acting, or refraining from acting, on any information
> contained in this e-mail is excluded.
>
> If you have received this e-mail by mistake please notify our System
> Administrators at [EMAIL PROTECTED] and delete this e-mail.
>
> It is the responsibility of the recipient to ensure that the onward
> transmission, opening or use of this message and any attachments will
> not adversely affect its systems or data. Please carry out such virus and
> other checks as you consider appropriate. No responsibility is accepted
> by Insurance Technology Solutions Limited in this regard.
> **************************************************************************************
>
