Showing all 19 (Edit, Save, CSV, Feed) |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
24907 | 2006-12-08 12:19 | 2007-12-14 17:25 | MySQL Server | Closed (5970 days) | S1 | 5.0.32-BK, 4.1.22 | Linux (Linux, freebsd) | Any | unpredictable (display) precision, if input precision increases |
27921 | 2007-04-18 9:45 | 2007-05-15 2:53 | MySQL Server: Views | Closed (6183 days) | S3 | 5.0.37, 5.1 | Linux | Any | View ignores precision for CAST() |
33059 | 2007-12-07 10:43 | 2007-12-07 11:54 | MySQL Server: Data Types | Not a Bug (5977 days) | S3 | Ver 14.12 Distrib 5.0.22 | Linux | Any | Loss of precision when selecting a FLOAT |
36270 | 2008-04-23 0:52 | 2011-02-16 23:43 | MySQL Server | Closed (5607 days) | S2 | 5.0.58, 5.1.24 | Any | Any | incorrect calculation result - works in 4.1 but not in 5.0 or 5.1 |
34075 | 2008-01-26 5:20 | 2012-08-01 11:10 | MySQL Server: GIS | Not a Bug (4278 days) | S3 | 5.x, 6.0 - BK | Any | Any | Geometry Precision Loss |
41886 | 2009-01-05 20:53 | 2009-01-06 11:54 | MySQL Server: General | Not a Bug (5581 days) | S3 | 4.1.22, 5.0.67 | Linux | Any | max() and min() functions truncate result to 14 places on double columns |
45686 | 2009-06-23 16:36 | 2011-02-16 23:44 | MySQL Server: Data Types | Won't fix (5410 days) | S2 | 4.1, 5.0, 5.1 bzr | Any (MS Windows, Linux) | Any | Double min or max values rounding error |
55677 | 2010-08-02 9:35 | 2010-08-03 14:03 | MySQL Server: Data Types | Not a Bug (5007 days) | S3 | 5.1.13 | Linux (CentOS) | Any | Floats rounded when read using JDBC |
61938 | 2011-07-21 6:57 | 2012-01-24 10:27 | MySQL Server: Stored Routines | Won't fix (4468 days) | S3 | 5.5.14 | Any | Any | Invalid result from equation of double data return by stored function |
63126 | 2011-11-07 2:16 | 2011-12-07 7:00 | MySQL Server: Data Types | No Feedback (4516 days) | S3 | 5.5.16 | Any | Any | cannot perform a precise calculation with decimal data |
61329 | 2011-05-27 15:17 | 2011-05-31 18:55 | MySQL Server: Documentation | Not a Bug (4706 days) | S3 | 5.1 and maybe others | Any | Any | manual conains a bad paragraph on decimal/numeric precision |
69754 | 2013-07-16 9:36 | 2014-08-21 0:36 | MySQL Workbench: Modeling | Closed (3528 days) | S3 | 5.2.46, 5.2.47,6.0.3 | Linux (Ubuntu 10.04.4) | Any | Syntax 'DOUBLE PRECISION' rejected in MySQL Workbench |
76187 | 2015-03-06 12:40 | 2015-08-12 0:52 | Connector / J | Closed (3172 days) | S3 | 5.7 | Any | Any | getTypeInfo report maximum precision of 255 for varchar |
76609 | 2015-04-07 12:14 | 2015-04-07 12:33 | MySQL Server: Data Types | Not a Bug (3299 days) | S3 | Linux (version 5.6.23) | Any | Decimal Division Innacurate or Wrong | |
84363 | 2016-12-28 23:04 | 2019-04-28 0:45 | MySQL Server: Documentation | Closed (1817 days) | S3 | all | Any | Any | Deprecate or remove "(m,n)" from FLOAT(m,n) and DOUBLE(m,n) |
97197 | 2019-10-11 7:49 | 2019-10-14 11:54 | MySQL Server: DML | Not a Bug (1651 days) | S3 | 8.0.16 | CentOS | Any | The decimal type result calculated by division gets truncated in temporary table |
84308 | 2016-12-22 3:47 | 2022-11-05 2:04 | Connector / J | Closed (530 days) | S2 | 5.1.40 | Any | Any | MySQL JDBC driver do not report COLUMN_SIZE for TIME/TIMESTAMP related columns |
109119 | 2022-11-17 10:44 | 2022-11-17 13:00 | MySQL Server: JSON | Not a Bug (518 days) | S3 | 8.0.20 | Any | Any | "CAST AS JSON" casts numeric values with big precision incorrectly |
100034 | 2020-06-29 13:17 | 2023-05-05 8:05 | Connector / Python | Closed (708 days) | S2 | mysql-connector-python (8.0.20), 8.0.20 | Any | Any | datetime precision incorrectly converted from MySQL datetime to Python datetime |
Showing all 19 (Edit, Save, CSV, Feed) |