Showing all 5 (Edit, Save, CSV, Feed) |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
42154 | 2009-01-16 11:17 | 2011-02-16 23:43 | MySQL Server: General | Verified (5750 days) | S3 | 5.0.67, 5.0.74, 5.1.30, 6.0.8 | Any | Any | PROCEDURE ANALYSE() recommends FLOAT for DOUBLE fields with very small values |
68864 | 2013-04-04 8:17 | 2013-04-04 8:37 | MySQL Server: Data Types | Verified (4211 days) | S2 | 5.6.10 | Any | Any | INTERVAL treats null values of text columns as float/int |
100985 | 2020-09-29 7:42 | 2020-09-29 9:18 | MySQL Server: Optimizer | Verified (1476 days) | S3 | 8.0.21, 5.7.31, 5.6.48 | Any | Any | Stored value for 0.001 is inconsistent, and casted to decimal is also different |
100270 | 2020-07-21 4:30 | 2020-07-21 6:34 | MySQL Server: Optimizer | Verified (1546 days) | S3 | 5.7.31, 5.6.48 | Any | Any | Use MOD result (float number) in HAVING/WHERE is not considered as TRUE |
43270 | 2009-02-27 18:10 | 2011-02-16 23:43 | MySQL Server: General | Verified (5707 days) | S3 | 5.0.51a, 5.0.67 | FreeBSD (FreeBSD 6.3, Linux) | Any | PROCEDURE ANALYZE returns wrong FLOAT(M,D) and doesn't honor max_elements |
Showing all 5 (Edit, Save, CSV, Feed) |