----- Original Message -----
>
> lets execute another query
> SQL> select count(*) from dpr70_gl_acct_balance_f;
>
> COUNT(*)
> ----------
> 2974
>
>
> from v$SQL
>
> SQL_TEXT
> --------------------------------------------------------------------------------
> PARSE_CALLS EXECUTIONS FIRST_LOAD_TIME LOADS LAST_LOAD_TIME
> ----------- ---------- ------------------- ---------- -------------------
> SELECT text from dp_security_text where object_name = :b1
> and
> comp_group_id = sys_context('dp_comp_group_id_ctx','comp_group_id')
> 7 24 2003-08-20/09:29:34 2 2003-08-20/10:39:44
>
> Notice again parse_calls does not change
>
> The above SQL is the predicate clause being generated every time
>
I don't think this is the issue at all. The SQL in the function
that generates the predicate WILL use bind variables and that
is perfectly expected. That's why you don't see an increase in parses
on the SQL INSIDE the function.
What will not use bind variables is this bit:
> SQL> select count(*) from dpr70_gl_acct_balance_f;
because the added predicate is a string without bind syntax.
However, I think if the added predicate string contains a reference
to a context variable, which is what Tom is talking about, it might
well be the case this will act as a kind of bind variable
even though the syntax is not the correct one. Anyone found if that
is the case?
Cheers
Nuno Souto
[EMAIL PROTECTED]
--
Please see the official ORACLE-L FAQ: http://www.orafaq.net
--
Author: Nuno Souto
INET: [EMAIL PROTECTED]
Fat City Network Services -- 858-538-5051 http://www.fatcity.com
San Diego, California -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing).
