Re: PL/SQL functions in SQL where clauses - how to evaluate them as a late as possible

<finely-grained permissioning with exepensive PL/SQL function evaluated in a SQL statement's where clause >
> 1. Native dynamic SQL

What would that help?

> 2. Get rid of the = 't' and replace it with a bind variable

What would the the bind variable help here? I always and only want the ones that get evaluated for true? Or would I be able to "fool" the optimizer here, so that it evaluates later? Received on Thu Feb 21 2002 - 01:26:28 CST