Bug #103494 ALL quantifier doesn't work with subqueries of degree > 1
| Submitted: | 27 Apr 2021 7:33 | Modified: | 27 Apr 2021 9:14 |
|---|---|---|---|
| Reporter: | Lukas Eder | Email Updates: | |
| Status: | Verified | Impact on me: | |
| Category: | MySQL Server: Documentation | Severity: | S3 (Non-critical) |
| Version: | 8.0.24, 5.7.34 | OS: | Any |
| Assigned to: | CPU Architecture: | Any |
[27 Apr 2021 7:33]
Lukas Eder
[27 Apr 2021 7:38]
MySQL Verification Team
Hello Lukas Eder, Thank you for the report and test case. regards, Umesh
[27 Apr 2021 7:44]
Lukas Eder
This also doesn't work: -- select (1, 1) < any (select 1 as `a`, 1 as `b`) as a; --
[27 Apr 2021 7:46]
Lukas Eder
But this does: -- select (1, 1) != all (select 1 as `a`, 1 as `b`) as a; -- It seems like the operands that map to IN or NOT IN are implemented, but not the others. If the correct implementation of the feature is not a high priority, I would at least suggest a fix in the error message, to hint at a missing implementation, rather than a syntax error.
[27 Apr 2021 8:20]
Roy Lyseng
Posted by developer: Not a bug, this functionality is not implemented. However, I do not find it documented as a limitation. It should be part of "Subqueries with ANY, IN, or SOME" and "Subqueries with ALL".
[27 Apr 2021 9:14]
Lukas Eder
I'll try my luck again :) The error message was quite misleading to me. Try this query, for example: -- select 1 in (select 1 limit 1) -- The error message is much more helpful: > SQL Error [1235] [42000]: This version of MySQL doesn't yet support 'LIMIT & IN/ALL/ANY/SOME subquery' Now, I don't have much of an opinion whether to label things as bugs or feature requests, but I think that the current error message could be improved, not just the documentation.
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.055 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.