RE: Operator and condition precedence

Hi guys,

Thanks for the answer, but where is this documented?  The 10.1 docs seem to
contradict that statement:

> I presume that the database is using CPU COST based optimization.  The
> predicates are not evaluated in reverse order. The CPU COST model will
> rearrange the predicates into the order it thinks is easiest to
> evaluate.



p.s.  Michael, if you check my post carefully you'll see the space in
between the quotes.  So it's really "and aa.col_2a > '[space]'".


Other related posts: