Re: PL/SQL functions in SQL where clauses

yes, afaik I agree with Michael - avoid 'thrownaways' i.e too many rows selected at the 'button' - and try to avoid function calls in where clauses, which will result in a full table scan if the function call is the first argument of the where clause (that's at least what I have been told - and seen - Oracle can't use the index - however, you may use hints)

"Michael Bialik" <bialik_at_isdn.net.il> wrote in message news:969f8022.0202171131.5df971aa_at_posting.google.com...
> AFAIK the "AND" conditions are processed Bottom-Up (right to left).
> Can you try changing the order in WHERE:
> select <something>
> from <some tables>
> where permission_p(:current_user_id, object_id, 'access')='t' AND
> <some where clauses>;
>
> HTH. Michael
Received on Sun Feb 17 2002 - 22:13:34 CET