Showing all 13 (Edit, Save, CSV, Feed) |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
51521 | 2010-02-25 18:03 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5345 days) | S2 | 5.1.42, 5.1.45-bzr | Any | Any | MERGE Algorithm in LEFT JOIN retuns 0000-00-00 instead of NULL |
53971 | 2010-05-25 12:34 | 2012-05-18 20:19 | MySQL Server: DB2SE for IBM i | Verified (5220 days) | S3 | 5.1.39 | IBM i (V6R1) | Any | Cardinality NULL of index over date field |
56025 | 2010-08-16 18:25 | 2018-09-09 20:45 | MySQL Server: General | Verified (5174 days) | S3 | 5.0.67, 5.0, 5.1, 5.6.99 | Any | Any | Weird date between behavior, not consistent between versions |
60724 | 2011-04-01 16:19 | 2011-04-05 14:50 | MySQL Server: DML | Verified (4946 days) | S2 | 5.5.11, 5.5.10-log, 5.1.57, 5.0.93 | Any | Any | Unquoted date literal in comparison yields incorrect implicit conversion |
65017 | 2012-04-17 23:41 | 2012-04-25 8:51 | MySQL Server: DML | Verified (4563 days) | S3 | 5.0, 5.1, 5.5 | Any | Any | Date and time functions are not consistently named |
21677 | 2006-08-16 18:48 | 2014-02-06 14:01 | MySQL Server: Data Types | Verified (3904 days) | S3 | 4.1.21, 5.0.23 | Linux (Linux) | Any | Change in results with "now() BETWEEN date_field1 AND date_field2" |
72761 | 2014-05-27 10:00 | 2014-05-27 17:03 | MySQL Server: DML | Verified (3794 days) | S3 | 5.6.17 | Any | Any | MySQL 5.6 FROM_UNIXTIME function returns different result than 5.5 |
77232 | 2015-06-02 20:38 | 2015-06-03 7:08 | MySQL Server: DML | Verified (3422 days) | S3 | 5.6.23, 5.6.24, 5.6.25 | Any | Any | Microtime not supported for <1 second past epoch |
83256 | 2016-10-04 16:17 | 2016-10-04 16:51 | MySQL Server: Parser | Verified (2933 days) | S3 | 5.5/5.6/5.7 | Red Hat (rhel6) | Any | date in multi-column IN clause with multi-values clause is parsed incorrectly |
84704 | 2017-01-29 11:02 | 2017-01-30 8:12 | MySQL Server: Document Store: MySQL Shell | Verified (2815 days) | S2 | 1.0.5 | Any | Any | The month in the output of a timestamp in MySQL shell is offset by 1. |
108937 | 2022-10-31 13:30 | 2022-12-13 4:03 | MySQL Server: Optimizer | Verified (672 days) | S3 | 8.0.30 | Any | Any | Date value change caused by HAVING |
108938 | 2022-10-31 13:59 | 2022-12-13 4:08 | MySQL Server: Optimizer | Verified (672 days) | S3 | 8.0.30 | Any | Any | Date value change caused by ON |
113366 | 2023-12-08 1:39 | 2023-12-08 8:06 | MySQL Server: DML | Verified (312 days) | S3 | 8.0.35 | Any | Any | Incorrect query results involving the date type. |
Showing all 13 (Edit, Save, CSV, Feed) |