Showing all 29 (Edit, Save, CSV, Feed) |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
21034 | 2006-07-13 13:39 | 2006-08-08 15:35 | MySQL Migration Toolkit | Closed (6468 days) | S3 | 1.1.1 beta | Any | Mysql 4.1 -> MySQL 5.1: FLOAT becomes FLOAT(0,0) | |
48526 | 2009-11-04 9:13 | 2011-02-16 23:44 | MySQL Server: InnoDB storage engine | Closed (5056 days) | S3 | 5.1.40 | Any | Any | Data type for float and double is incorrectly reported in InnoDB table monitor |
111477 | 2023-06-18 15:14 | 2023-06-19 11:59 | MySQL Server: Federated storage engine | Unsupported (309 days) | S2 | 8.0.33 | Any | Any | If Table contains Floating Point with limited digits, UPDATE may silently fail |
109119 | 2022-11-17 10:44 | 2022-11-17 13:00 | MySQL Server: JSON | Not a Bug (523 days) | S3 | 8.0.20 | Any | Any | "CAST AS JSON" casts numeric values with big precision incorrectly |
104632 | 2021-08-16 6:04 | 2021-08-16 19:44 | MySQL Server | Not a Bug (981 days) | S2 | 8.0.21 | Any | Any | Floating point overflow |
100270 | 2020-07-21 4:30 | 2020-07-21 6:34 | MySQL Server: Optimizer | Verified (1372 days) | S3 | 5.7.31, 5.6.48 | Any | Any | Use MOD result (float number) in HAVING/WHERE is not considered as TRUE |
97880 | 2019-12-04 15:57 | 2019-12-05 22:24 | MySQL Server: Document Store: X Plugin | Not a Bug (1601 days) | S3 | 8.0 | Any | Any | Precision loss when using float & double arguments |
100985 | 2020-09-29 7:42 | 2020-09-29 9:18 | MySQL Server: Optimizer | Verified (1302 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 |
88812 | 2017-12-07 12:16 | 2017-12-08 8:49 | MySQL Server: JSON | Duplicate (2328 days) | S3 | 8.0.3 | Any | Any | JSON does not preserve zero fraction floats when manipulated |
87794 | 2017-09-18 15:10 | 2017-09-19 15:33 | MySQL Server: DML | Not a Bug (2408 days) | S3 | 5.7.17 | Any | Any | MySQL gives invalid value for float column type. |
84363 | 2016-12-28 23:04 | 2019-04-28 0:45 | MySQL Server: Documentation | Closed (1822 days) | S3 | all | Any | Any | Deprecate or remove "(m,n)" from FLOAT(m,n) and DOUBLE(m,n) |
68864 | 2013-04-04 8:17 | 2013-04-04 8:37 | MySQL Server: Data Types | Verified (4037 days) | S2 | 5.6.10 | Any | Any | INTERVAL treats null values of text columns as float/int |
47049 | 2009-09-01 17:10 | 2009-09-01 22:03 | MySQL Server: DML | Not a Bug (5348 days) | S3 | 5.1.35, 4.1, 5.0, 5.1, 5.4 bzr | Any (SunOS 5.10 Generic_138889-02 i86pc i386 i86pc) | Any | Boundaries are included in result when using a float in a range (< or >) |
42154 | 2009-01-16 11:17 | 2011-02-16 23:43 | MySQL Server: General | Verified (5576 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 |
37624 | 2008-06-25 10:26 | 2008-06-25 11:39 | MySQL Server: MyISAM storage engine | Not a Bug (5781 days) | S3 | 5.0 | Any | Any | query produces incorrect results witch float values |
29228 | 2007-06-20 3:10 | 2007-09-15 11:23 | MySQL Cluster: Cluster (NDB) storage engine | Closed (6065 days) | S3 | 5.1 | Any | Any | ndb_size.pl fails on FLOAT columns with comma in () |
43270 | 2009-02-27 18:10 | 2011-02-16 23:43 | MySQL Server: General | Verified (5533 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 |
43561 | 2009-03-11 13:05 | 2009-03-11 14:20 | MySQL Server: General | Not a Bug (5522 days) | S3 | 5.0.70 | Linux | Any | can't find some floating point numbers |
55677 | 2010-08-02 9:35 | 2010-08-03 14:03 | MySQL Server: Data Types | Not a Bug (5012 days) | S3 | 5.1.13 | Linux (CentOS) | Any | Floats rounded when read using JDBC |
60876 | 2011-04-15 6:20 | 2011-04-23 16:47 | MySQL Server | Not a Bug (4749 days) | S2 | mysql Ver 14.12 Distrib 5.0.45 | Linux (Red Hat Enterprise Linux Server release 5.3 ) | Any | A Floating Point Issue |
75750 | 2015-02-03 14:10 | 2015-02-06 14:48 | MySQL Server: Optimizer | Not a Bug (3364 days) | S2 | 5.6.22, 5.6.23 | Linux (gentoo) | Any | incorrect sorting results when using float field and LIMIT clause |
38851 | 2008-08-18 12:47 | 2008-08-18 16:35 | MySQL Server | Can't repeat (5727 days) | S3 | 5.0.51a-community | Linux (SUSE) | Any | Entering 999.99 into FLOAT(5,2) gives warning 1264 (Out of range value adjust..) |
34015 | 2008-01-23 18:02 | 2008-02-11 21:00 | MySQL Server: Federated storage engine | Closed (5916 days) | S1 | 5.0.54 | Linux | Any | Problems with float fields using federated tables |
33059 | 2007-12-07 10:43 | 2007-12-07 11:54 | MySQL Server: Data Types | Not a Bug (5982 days) | S3 | Ver 14.12 Distrib 5.0.22 | Linux | Any | Loss of precision when selecting a FLOAT |
24907 | 2006-12-08 12:19 | 2007-12-14 17:25 | MySQL Server | Closed (5975 days) | S1 | 5.0.32-BK, 4.1.22 | Linux (Linux, freebsd) | Any | unpredictable (display) precision, if input precision increases |
50740 | 2010-01-29 16:44 | 2018-06-24 20:45 | MySQL Workbench: Modeling | Duplicate (5102 days) | S3 | 5.2.15a beta | MacOS (10.6.2) | Any | Type field is blank after changing type from INT to FLOAT |
10079 | 2005-04-21 22:59 | 2007-06-13 9:20 | Connector / ODBC | Can't repeat (6159 days) | S2 | 3.51.11 | Windows (Windows XP Pro SP2) | Any | Float function doesn't return result in full precision through ODBC |
30326 | 2007-08-09 1:24 | 2007-08-09 7:49 | MySQL Server: InnoDB storage engine | Not a Bug (6102 days) | S1 | 5.0.46 | Windows (Vista) | Any | UNION returns incorrect results to 14 decimals |
47355 | 2009-09-16 8:53 | 2009-09-16 9:19 | MySQL Server: Data Types | Not a Bug (5333 days) | S3 | mySQL server 4.1 | Windows (SP2) | Any | Cannot compute sum of values with 1 or 2 decimal place if type is Float. |
Showing all 29 (Edit, Save, CSV, Feed) |