Re: Order of where clause matters!

In article <8jgki7$3ep$1_at_nnrp1.deja.com>, dave_wotton_at_my-deja.com writes <snipped>

Agreed.

We were clobbered by another variation on this today with "invalid number" being returned - this happened joining to a config table with a variable lookup something like this:
where config_variable='A NUMBER' and config value > 100. Of course some of our config variables are not numbers but since the > test was done before the = 'A NUMBER' test, it caused an error.
This is becoming a pain!
The only safe way appears to be a set of select from selects... Steve
P.S
Don't even mention the CBO in 8.0.5...
8.1.6 makes some painful decisions too.
Wishlist: rather than hint, how about "don't ignore me, do it this way" The CBO may assume that the hint is wrong and ignore it, but that doesn't help if the CBO is wrong in making the decision about whether the hint is wrong. Ho hum. Received on Fri Jun 30 2000 - 00:00:00 CDT