Bug #79628 | Result type for max(float column) is FLOAT, while expecting DOUBLE | ||
---|---|---|---|
Submitted: | 14 Dec 2015 9:28 | Modified: | 13 Nov 2018 13:00 |
Reporter: | Su Dylan | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server: Data Types | Severity: | S3 (Non-critical) |
Version: | 5.7.8 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[14 Dec 2015 9:28]
Su Dylan
[12 Oct 2018 15:59]
MySQL Verification Team
Hi, Thank you for your bug report. However, I fail to see where is the problem. If you have a column of the type FLOAT, then its maximum value can not be larger then the maximum value that a FLOAT type can hold, according to IEEE standard. The range for that type is: 1.175494*10^-38 - 3.402823*10^38 You also have zero and the same range for the negative numbers. Length is totally irrelevant in this respect. What is relevant is a number of significant digits. For FLOATs is 8 digits, for DOUBLE it is 16 digits and for LONG DOUBLE is 20 digits. Hence, FLOAT can not be converted into DOUBLE at all, except by a typecast.
[13 Nov 2018 1:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".