Bug #30524 | CAST(0 AS Double) needed | ||
---|---|---|---|
Submitted: | 20 Aug 2007 22:24 | Modified: | 19 May 2019 23:42 |
Reporter: | Mark Callaghan | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Data Types | Severity: | S4 (Feature request) |
Version: | 5.0 | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | cast, double, literal, numeric |
[20 Aug 2007 22:24]
Mark Callaghan
[20 Aug 2007 22:45]
MySQL Verification Team
Thank you for the bug report.
[19 May 2019 23:42]
Jon Stephens
Fixed in MySQL 8.0.17 by WL#529. Changelog entry as follows: MySQL now supports explicits casts to DOUBLE, FLOAT, and REAL using either of the functions CAST() or CONVERT(). For more information, see "Cast Functions and Operators" [https://dev.mysql.com/doc/refman/8.0/en/cast-functions.html]. Closed. Note that the CREATE statement shown initially yields a DECIMAL(3,2) column. In order for the subsequent INSERT to work, use CREATE TABLE t AS SELECT 00.00 which produces a DECOMAL(4,2) column or CREATE TABLE AS SELECT CAST(0 AS DOUBLE) which makes the column explicitly DOUBLE.