Re: Where clause ordering
From: Jonathan Lewis <Jonathan_at_jlcomp.demon.co.uk>
Date: 1995/08/31
Message-ID: <809858072snz_at_jlcomp.demon.co.uk>#1/1
Date: 1995/08/31
Message-ID: <809858072snz_at_jlcomp.demon.co.uk>#1/1
In article <1995Aug24.085202.2268_at_figmnt.tayloru.edu>
dganderso_at_figmnt.tayloru.edu "Doug Anderson" writes:
: > Intersetingly, changing the query to:
: >
: > select count(*) from lookups
: > where
: > to_number(value) = 0;
: > and class in (123,456)
: >
: > was sufficient to change the predicate precedence and cause the
: > query to fail again.
:
: Sorry, I can't resist. Maybe the semi-colon BEFORE the 'and' might have
: something to do with it. ;-]
:
I'll bet you thought you were joking: I haven't had a chance to get back to the 7.1.6 on Sequent yet, but 7.0.16 and 7.1.3 on HP-UX do not change their behaviour when the 'class = ' is changed to 'class in'.
-- Jonathan LewisReceived on Thu Aug 31 1995 - 00:00:00 CEST