| Showing all 9 (Edit, Save, CSV, Feed) |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 34612 | 2008-02-15 19:49 | 2013-03-03 20:45 | MySQL Server: CSV | Verified (5986 days) | S2 | 5.0,5.1.22 | Other (i5/OS v5r4 PASE) | Any | CSV storage engine does not honor time_zone |
| 62696 | 2011-10-12 9:36 | 2011-11-09 15:38 | MySQL Server: Parser | Verified (5239 days) | S3 | 5.5.17, 5.6.4-m5 | Any | Any | Using a numeric operator on a TIME column should return an error or warning |
| 65017 | 2012-04-17 23:41 | 2012-04-25 8:51 | MySQL Server: DML | Verified (5050 days) | S3 | 5.0, 5.1, 5.5 | Any | Any | Date and time functions are not consistently named |
| 77232 | 2015-06-02 20:38 | 2015-06-03 7:08 | MySQL Server: DML | Verified (3909 days) | S3 | 5.6.23, 5.6.24, 5.6.25 | Any | Any | Microtime not supported for <1 second past epoch |
| 74867 | 2014-11-14 13:03 | 2015-03-06 12:27 | MySQL Enterprise Monitor: Advisors/Rules | Verified (3998 days) | S3 | 3.0.14 | Any | Any | False positive for "Agent Host Time Out of Sync Relative to Dashboard" |
| 106597 | 2022-02-28 13:25 | 2022-03-01 7:21 | MySQL Server: DML | Verified (1446 days) | S3 | 8.0.25, 8.0.28 | Any | Any | TIME type truncate error in 'in' function |
| 116790 | 2024-11-27 2:24 | 2026-01-26 19:48 | MySQL Server: Documentation | Verified (439 days) | S3 | 8.0.22 | Any | Any | Retrieving TIME type from MYSQL JSON yields incorrect result |
| 119863 | 2026-02-09 11:16 | 2026-02-11 0:22 | Connector / J | Verified (3 days) | S2 | 8.0.30, 9.6.0 (Verified in both) | Linux (OpenJDK 17) | Any (OpenJDK 17) | Inaccurate decoding of negative TIME durations in Binary Protocol (Cursor Mode) |
| 110310 | 2023-03-09 8:41 | 2023-04-29 15:24 | MySQL Server: Optimizer | Verified (1073 days) | S3 | 8.0.32 | Ubuntu (22.04) | x86 (x86_64) | BETWEEN query with wrong result |
| Showing all 9 (Edit, Save, CSV, Feed) |
