1.create table t1 (f1 int, f2 int); create table t3 (f1 int, f2 int);
2.insert some rows into the 2 tables
3.select * from t1 where f1 > ANY (select f2 from t3);
Actual Results:
cardinality violation (11>1)
(SOME/ALL operator got the same result)
Expected Results:
return rows in t1 where f1 > any f2 column in t3;
Comment 21731
Date: 2016-01-14 06:02:45 +0100
From: Kaijiang <>
This case works well in other DB, such as PostgreSQL.
the parser already handled the any|more and all syntax. Now in the default branch also the semantics are properly handled. This (somewhat new feature) will be in the release after the Jun2016.
Date: 2016-01-14 05:55:12 +0100
From: Kaijiang <>
To: SQL devs <>
Version: 11.21.11 (Jul2015-SP1)
CC: @njnes
Last updated: 2016-04-11 11:16:08 +0200
Comment 21729
Date: 2016-01-14 05:55:12 +0100
From: Kaijiang <>
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.106 Safari/537.36
Build Identifier:
MonetDB doesn't handle ANY/SOME/ALL operator correctly
Reproducible: Always
Steps to Reproduce:
1.create table t1 (f1 int, f2 int); create table t3 (f1 int, f2 int);
2.insert some rows into the 2 tables
3.select * from t1 where f1 > ANY (select f2 from t3);
Actual Results:
cardinality violation (11>1)
(SOME/ALL operator got the same result)
Expected Results:
return rows in t1 where f1 > any f2 column in t3;
Comment 21731
Date: 2016-01-14 06:02:45 +0100
From: Kaijiang <>
This case works well in other DB, such as PostgreSQL.
Comment 21993
Date: 2016-03-30 21:20:01 +0200
From: @njnes
the parser already handled the any|more and all syntax. Now in the default branch also the semantics are properly handled. This (somewhat new feature) will be in the release after the Jun2016.
Comment 22026
Date: 2016-04-11 11:16:08 +0200
From: @sjoerdmullender
Jul2015-SP4 has been released.
The text was updated successfully, but these errors were encountered: