Showing all 15 (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 (3783 days) | S3 | 5.5.31, 5.6.21 | Any | Any | Strange result types for LPAD/RPAD and CONCAT when mixing binary and non-binary |
69729 | 2013-07-12 2:18 | 2018-07-12 12:54 | MySQL Server: Optimizer | Verified (4158 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 (3952 days) | S2 | 5.5.13 | Any | Any | Bit-shift operators produce signed integer overflow on large input |
70767 | 2013-10-29 19:09 | 2020-02-14 21:55 | MySQL Server: Charsets | Verified (3847 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 (3845 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 (4033 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 |
71378 | 2014-01-14 18:03 | 2014-01-15 5:49 | MySQL Server: DML | Verified (3971 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 (3971 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 (3968 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' |
72089 | 2014-03-20 20:30 | 2014-03-22 6:19 | MySQL Server: DML | Verified (3905 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 |
72672 | 2014-05-16 18:17 | 2014-05-22 9:21 | MySQL Server: Data Types | Verified (3844 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 |
72685 | 2014-05-19 20:20 | 2014-05-20 7:01 | MySQL Server: Charsets | Verified (3846 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 (3844 days) | S2 | 5.5.31, 5.5.38 | Any | Any | HOUR() of a DATETIME with date zero occasionally (unpredictably) returns NULL |
73086 | 2014-06-23 23:56 | 2014-06-24 4:48 | MySQL Server: Charsets | Verified (3811 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" |
73552 | 2014-08-12 18:56 | 2014-08-18 19:47 | MySQL Server: DML | Verified (3756 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 15 (Edit, Save, CSV, Feed) |