 |
 |
Archives of the TeradataForum
Message Posted: Tue, 10 Feb 2004 @ 14:38:05 GMT
Subj: | | Re: EXISTS predicate bug? |
|
From: | | Geoffrey Rommel |
| select * from n1 where EXISTS (select max(c1) from n1 where c1<0) | |
| and let's say all the values in c1 are > 0 | |
| Then Oracle/UDB will return TRUE, but TD will return FALSE for this. | |
I tried this on DB2 for z/OS (MVS), DB2/UDB for AIX, Informix, and Teradata. On all four platforms, the subquery ("select max(c1)...")
returns a single row with a null value in it. Since there is a row, EXISTS, as you say, should evaluate as true. This conclusion is borne out by
running the full query: on the other three platforms, it returns a number of rows, but on Teradata it returns an empty result. This is indeed a
bug, in my opinion.
| |