Comment 6 for bug 592473

Hi. I took a look at this / did some initial testing and it looks like subselect.test has broken.

The subquery below should return 1 per http://dev.mysql.com/doc/refman/5.1/en/all-subqueries.html (Postgres docs agree).
The case is that the subquery is returning an empty set (not NULL), which should evaluate to TRUE on comparison here (t1 contains the value 1).

Could you take a look at this and I'll retest when you're ready?

main.subselect [ fail ]
--- /patched/tests/r/subselect.result 2010-06-26 20:41:50.616221000 +0300
+++ /patched/tests/r/subselect.reject 2010-06-27 00:14:26.775425019 +0300
@@ -2804,7 +2804,6 @@
 1
 SELECT * FROM t1 WHERE f1 > ALL (SELECT f2 FROM t2 WHERE 1=0);
 f1
-1
 INSERT INTO t2 VALUES (1);
 INSERT INTO t2 VALUES (2);
 SELECT * FROM t1 WHERE f1 > ALL (SELECT f2 FROM t2 WHERE f2=0);

drizzletest: Result content mismatch