| Showing all 28 (Edit, Save, CSV, Feed) |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 69666 | 2013-07-03 19:09 | 2014-07-22 19:40 | MySQL Server: Data Types | Verified (3560 days) | S3 | 5.5.31, 5.6.21 | Any | Any | Strange result types for LPAD/RPAD and CONCAT when mixing binary and non-binary |
| 69715 | 2013-07-10 17:39 | 2019-03-31 18:48 | MySQL Server: Data Types | Closed (2056 days) | S3 | Any | Any | UBSAN: Item_func_mul::int_op() mishandles 9223372036854775809*-1 | |
| 69729 | 2013-07-12 2:18 | 2018-07-12 12:54 | MySQL Server: Optimizer | Verified (3935 days) | S2 | 5.5.31, 5.5.32 | Any | Any | Bad interaction between MIN/MAX and "NOT BETWEEN" leads to wrong results |
| 69796 | 2013-07-19 18:19 | 2014-09-18 6:24 | MySQL Server: Data Types | Verified (3729 days) | S2 | 5.5.13 | Any | Any | Bit-shift operators produce signed integer overflow on large input |
| 69833 | 2013-07-24 20:58 | 2016-01-12 20:45 | MySQL Server: Optimizer | Closed (3606 days) | S2 | 5.5.31,5,5.32, 5.6.12, 5.7.2-m12 | Any | Any | Bad interaction between MIN/MAX and "HAVING SUM(DISTINCT)": wrong results |
| 69841 | 2013-07-25 23:41 | 2013-10-01 18:37 | MySQL Server: Optimizer | Closed (3854 days) | S3 | 5.5/5.6 | Any | Any | SELECT COUNT(DISTINCT a,b) incorrectly counts rows containing NULL |
| 70341 | 2013-09-13 19:00 | 2013-11-01 9:45 | MySQL Server: Optimizer | Closed (3823 days) | S2 | 5.5.31, 5.6 | Any | Any | Key lengths lead to incomplete result sets; unhinted scans prefer such indexes |
| 70767 | 2013-10-29 19:09 | 2020-02-14 21:55 | MySQL Server: Charsets | Verified (3624 days) | S2 | 5.5.31, 5.5.34 | Any | Any | LOCATE() and INSTR() claim to be multibyte aware, but are not |
| 70815 | 2013-11-05 3:43 | 2014-05-21 19:00 | MySQL Server: Charsets | Verified (3622 days) | S2 | 5.5.31, 5.5.34 | Any | Any | SELECT DISTINCT hashes Unicode space characters incorrectly |
| 70901 | 2013-11-13 20:18 | 2013-11-14 18:02 | MySQL Server: Optimizer | Verified (3810 days) | S3 | 5.5.31, 5.5.35, 5.1.71, 5.0.97, 5.6.15 | Any | Any | ORDER BY of a TEXT column doesn't use the same ordering as the < > = operators |
| 71259 | 2014-01-01 0:42 | 2014-11-12 22:48 | MySQL Server: Data Types | Closed (3447 days) | S3 | 5.5.34 | Any | Any | LOAD DATA into a SET with exactly 64 elements gives bogus errors |
| 71368 | 2014-01-14 2:09 | 2019-11-12 22:43 | MySQL Server: DML | Closed (1621 days) | S2 | 5.5.31, 5.5.34, 5.5.35, 5.6.15 | Any | Any | -1 % 0.5 yields -0.0 |
| 71378 | 2014-01-14 18:03 | 2014-01-15 5:49 | MySQL Server: DML | Verified (3748 days) | S2 | 5.5.31,5.5.34, 5.5.35, 5.6.15 | Any | Any | FROM_DAYS(3652499) yields invalid unprintable date |
| 71380 | 2014-01-14 19:35 | 2014-01-15 7:20 | MySQL Server: Optimizer | Verified (3748 days) | S2 | 5.5.31, 5.5.35, 5.6.15 | Any | Any | FORMAT(x,y) is incorrectly truncated when used with a sorted JOIN |
| 71414 | 2014-01-17 20:41 | 2014-01-18 5:35 | MySQL Server: DML | Verified (3745 days) | S3 | 5.5.31, 5.5.35, 5.6.15, 5.1.73 | Any | Any | DATE_FORMAT('0000-00-00', '%U') overflows, gives '613566757' |
| 71434 | 2014-01-20 21:24 | 2019-11-12 23:00 | MySQL Server: DML | Closed (1621 days) | S2 | 5.5.31, 5.5.35, 5.6.15, 5.1.73 | Any | Any | DECIMAL `0.1` evaluates to TRUE in project list, FALSE in where/having clauses |
| 72089 | 2014-03-20 20:30 | 2014-03-22 6:19 | MySQL Server: DML | Verified (3682 days) | S3 | 5.5.8, 5.5.31, 5.5.38 | Any | Any | FOUND_ROWS returns 0 or garbage when used in non-trivial queries |
| 72100 | 2014-03-21 22:09 | 2014-08-19 14:52 | MySQL Server: DML | Closed (3532 days) | S2 | 5.5.8, 5.5.31, 5.6.17, 5.5.37 | Any | Any | 0.00000000042 MOD 10 = 0.42000000000 |
| 72127 | 2014-03-25 19:16 | 2019-11-18 22:42 | MySQL Server: DML | Closed (1615 days) | S3 | 5.5.8, 5.5.31,5.6 | Any | Any | DIV with floats or doubles and unsigned integers sometimes errors out spuriously |
| 72672 | 2014-05-16 18:17 | 2014-05-22 9:21 | MySQL Server: Data Types | Verified (3621 days) | S2 | 5.5.31,5.5.34, 5.7.5, 5.6.19 | Any | Any | Zero-valued DATETIME column can be simultaneously NULL and NOT NULL |
| 72673 | 2014-05-16 22:38 | 2014-06-02 11:29 | MySQL Server: DML | Duplicate (3610 days) | S2 | 5.5.31, 5.5.34 | Any | Any | SUBSTRING_INDEX with negative index sometimes returns uninitialized memory |
| 72685 | 2014-05-19 20:20 | 2014-05-20 7:01 | MySQL Server: Charsets | Verified (3623 days) | S2 | 5.5.31, 5.5.34, 5.6.19, 5.7.5 | Any | Any | LOCATE/INSTR with mixed collations returns inconsistent results |
| 72711 | 2014-05-21 18:33 | 2014-05-22 8:33 | MySQL Server: Optimizer | Verified (3621 days) | S2 | 5.5.31, 5.5.38 | Any | Any | HOUR() of a DATETIME with date zero occasionally (unpredictably) returns NULL |
| 72856 | 2014-06-03 21:01 | 2014-08-19 14:49 | MySQL Server: Optimizer | Closed (3532 days) | S3 | 5.5.8, 5.5.31, 5.5.38, 5.6.20, 5.7.5 | Any | Any | SHA2(x, NULL) yields SHA2(x, 0) instead of NULL |
| 73086 | 2014-06-23 23:56 | 2014-06-24 4:48 | MySQL Server: Charsets | Verified (3588 days) | S3 | 5.5.8, 5.5.31, 5.5.34, 5.6.19 | Any | Any | Collation and coercibility of AVG(NULL) is incorrectly reported as "binary" |
| 73248 | 2014-07-09 19:51 | 2020-09-30 18:23 | MySQL Server: DML | Closed (1298 days) | S2 | 5.5.8, 5.5.31, 5.5.34, 5.6.20, 5.7.5 | Any | Any | Many, many classes of string-to-integer conversion bug |
| 73543 | 2014-08-12 0:28 | 2014-09-30 16:26 | MySQL Server: DML | Closed (3490 days) | S2 | 5.5.8, 5.5.31, 5.5.34, 5.5.40 | Any | Any | SUM(DISTINCT ...) incorrectly converts DATE, DATETIME, and TIMESTAMP to YEAR |
| 73552 | 2014-08-12 18:56 | 2014-08-18 19:47 | MySQL Server: DML | Verified (3533 days) | S2 | 5.5.8, 5.5.31, 5.5.34,5.6.20 | Any | Any | ('string' = CAST(0 as TIME)) produces bogus error "Illegal mix of collations" |
| Showing all 28 (Edit, Save, CSV, Feed) |
