Bug #100852 ANY_VALUE gives unexpected type with GROUP BY
| Submitted: | 15 Sep 2020 9:40 | Modified: | 15 Sep 2020 11:43 |
|---|---|---|---|
| Reporter: | Craig Archer | Email Updates: | |
| Status: | Verified | Impact on me: | |
| Category: | MySQL Server: Optimizer | Severity: | S3 (Non-critical) |
| Version: | 8.0.20, 8.0.21 | OS: | Windows |
| Assigned to: | CPU Architecture: | Any |
[15 Sep 2020 9:40]
Craig Archer
[15 Sep 2020 11:43]
MySQL Verification Team
Hello Craig Archer, Thank you for the report and test case. regards, Umesh
[26 Nov 2022 0:26]
Filipe Silva
Posted by developer: This is not a Connector/J bug. Connector/J simply maps whatever MySQL types it gets to Java types or objects. In this case MySQL is actually sending a different metadata information when ANY_VALUE is used, which is not supposed to happen, as explicitly said in the documentation (https://dev.mysql.com/doc/refman/8.0/en/miscellaneous-functions.html#function_any-value). This behavior was still observed in latest MySQL version, 8.0.31. Moving to a server bug category.
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.041 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.