Showing 1–30 of 1808
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 24004 | 2006-11-06 10:42 | 2011-02-16 23:43 | Connector / MXJ | Patch pending (7290 days) | S2 | 5.0 | Any | Cannot running MXJ as part of the JDBC driver on non-3306 ports when ... | |
| 92331 | 2018-09-07 6:29 | 2025-08-17 20:45 | MySQL Server: Documentation | In progress (1554 days) | S3 | 8.0.12 | Any | Any | Document JSON numeric types and conversion rules |
| 46037 | 2009-07-08 11:11 | 2018-11-04 20:45 | MySQL Server: Data Types | Verified (6331 days) | S3 | mysql-azalea/5.1 | Any | Any | Inconsistent behavior when casting floating point numbers to integer |
| 120905 | 2026-07-13 10:06 | 2026-07-20 11:02 | MySQL Server: Optimizer | Verified (116 days) | S1 | 9.1 | Any | Any | CASE Expression with Mixed FLOAT/INT Constant Returns Different Results in Single Table vs. Derived Table Due to Type In |
| 121325 | 2026-09-20 20:01 | 2026-09-21 8:46 | MySQL Server: Optimizer | Verified (47 days) | S2 | 8.0.46, 8.4.11, 9.7.2, 26.10.0 | Any | Any | MIN()/MAX() with BETWEEN and a non-integral bound returns NULL while rows match |
| 119944 | 2026-02-25 22:14 | 2026-02-26 13:13 | MySQL Server: Optimizer | Verified (254 days) | S1 | 8.0, 8.4, 9.X | Any | Any | Feature Request: Extend TIMESTAMP range beyond 2038-01-19 by switching to 64-bit signed storage (Year 2038 Problem) |
| 121010 | 2026-07-27 7:15 | 2026-07-27 7:15 | MySQL Server: User-defined functions ( UDF ) | Open | S2 | 8.4.7-7 | Any | Any | Contribution by ByteDance RDS MySQL team: mysqld crashes on keyring_key_store UDF return-type mismatch |
| 121531 | 2026-10-16 9:20 | 2026-10-19 6:05 | MySQL Server: Optimizer | Verified (19 days) | S2 | 8.0.46, 8.4.11, 9.7.2, 26.07 | Any | Any | IP address validation functions incorrectly return 0 instead of NULL for integer-typed NULL arguments |
| 121509 | 2026-10-15 5:00 | 2026-10-20 4:31 | MySQL Server: Data Types | Verified (18 days) | S3 | 8.0.46, 8.4.11, 9.7.2, 26.07 | Any | Any | Integer >= 2^63 converted to TIME is read as signed: CAST(18446744073709551614 AS TIME) = -00:00:02, TIME_TO_SEC() = -2 |
| 43763 | 2009-03-20 6:30 | 2025-12-07 20:45 | MySQL Server | Verified (6441 days) | S3 | 6.0.11, 5.0, 5.1, 6.0 bzr | Any | Any | Difference in warnings generated between engines |
| 61735 | 2011-07-04 11:30 | 2011-07-08 6:02 | MySQL Server: InnoDB storage engine | Verified (5601 days) | S3 | 5.1, etc | Any | Any | index->lock held while preads are done |
| 44330 | 2009-04-16 21:22 | 2021-05-02 20:45 | MySQL Cluster: Cluster (NDB) storage engine | Verified (6407 days) | S2 | mysql-5.1-telco-7.0 | Any | Any | ndb-connection-pool set higher then NDB API slots makes db appear corrupt |
| 70684 | 2013-10-22 8:13 | 2013-10-22 11:35 | MySQL Server: Optimizer | Verified (4764 days) | S3 | 5.5.33, 5.6.14 | Any | Any | HAVING referring to subquery results in WARNING 1292 |
| 121513 | 2026-10-15 5:12 | 2026-10-20 4:23 | MySQL Server: Data Types | Verified (18 days) | S3 | 8.0.46, 8.4.11, 9.7.2, 26.07 | Any | Any | TIME string parser takes the hour, minute and second fields modulo 2^64: CAST('18446744073709551635:40:27' AS TIME) = 19 |
| 120907 | 2026-07-13 10:36 | 2026-07-21 15:19 | MySQL Server: Optimizer | Verified (116 days) | S1 | 8.0.46, 8.4.10, 9.7.1 | Any | Any | Index Lookup Loses Unary Plus Operator During Condition Pushdown, Causing String-to-Integer Truncation and Wrong Match |
| 47118 | 2009-09-04 1:35 | 2026-05-28 1:12 | MySQL Server: General | Patch pending (2173 days) | S1 | 5.1.39, 5.1.37, 5.0.83,8.0.22, 5.6.10 | Any | Any | Wrong auto_increment value when auto_increment_offset > auto_increment_increment |
| 119432 | 2025-11-20 8:47 | 2025-12-07 21:44 | MySQL Server: Data Types | Verified (335 days) | S1 | 8.0 | Any | Any | Inconsistent time conversion behaviors between text and integer |
| 120966 | 2026-07-21 5:58 | 2026-07-22 8:41 | MySQL Server: Optimizer | Verified (108 days) | S1 | 8.0.46, 8.4.10, 9.7.1 | Any | Any | LEAST Expression Incorrectly Evaluated as Integer for Index Lookup in IN Condition |
| 110244 | 2023-03-01 3:46 | 2023-03-01 6:30 | MySQL Server: Optimizer | Verified (1347 days) | S2 | 8.0.32 | Any | Any | Nesting queries in a projection results in different output |
| 88033 | 2017-10-09 18:38 | 2021-06-06 8:13 | MySQL Server: JSON | Verified (1980 days) | S3 | 8.0.24, 5.7.19 | Any | Any | Generated INT column with value from JSON document |
| 40747 | 2008-11-14 15:03 | 2020-05-03 20:45 | MySQL Server: Data Types | Verified (6567 days) | S3 | 5.0.70, 5.1.29, 6.0.7 | Any | Any | Duplicate datetime truncation warning if a range optimizer is used. |
| 69704 | 2013-07-09 23:26 | 2013-07-10 5:36 | MySQL Server: Options | Verified (4868 days) | S3 | 5.5.32, 5.6.12 | Any | Any | Strangeness with max_binlog_stmt_cache_size Settings |
| 119033 | 2025-09-18 9:16 | 2025-09-23 0:51 | MySQL Server: Optimizer | Verified (411 days) | S3 | 9.4.0 8.4.6 | Any | Any | Incorrect filtering when comparing a BINARY-cast integer to a BIT column with a UNIQUE key |
| 120975 | 2026-07-22 4:42 | 2026-07-22 9:05 | MySQL Server: Optimizer | Verified (108 days) | S1 | 8.0.46, 8.4.10, 9.7.1 | Any | Any | Mixed-Type IFNULL Constant Causes Wrong Integer Conversion in Index Lookup |
| 119433 | 2025-11-20 9:30 | 2025-12-07 21:58 | MySQL Server: Data Types | Verified (335 days) | S1 | 8.4.6 | Any | Any | Inconsistent date conversion behaviors between text and integer |
| 102831 | 2021-03-05 16:32 | 2021-04-19 6:39 | MySQL Server: InnoDB storage engine | Verified (2072 days) | S2 | 5.7.31, 5.7.33 | Any (CentOS, Ubuntu) | Any | transaction-isolation level is not honored when changed at session level |
| 52283 | 2010-03-22 19:10 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (6073 days) | S3 | 5.1.46 | Any | Any | Innodb reports extra warnings when SELECT/WHERE is performed using invalid value |
| 114922 | 2024-05-08 9:25 | 2024-05-08 9:58 | MySQL Server: Optimizer | Verified (913 days) | S1 | 8.0.36 | Any | Any | Incorrect query results caused by different data conversion |
| 112181 | 2023-08-25 9:04 | 2023-09-18 8:39 | MySQL Server: Partitions | Verified (1167 days) | S3 | 8.0 | Any | Any | TIMESTAMP(N) partitions doesn't prune for inequity |
| 121508 | 2026-10-15 4:52 | 2026-10-20 4:44 | MySQL Server: Data Types | Verified (18 days) | S3 | 8.0.46, 8.4.11, 9.7.2, 26.07 | Any | Any | DATE_ADD/ADDDATE/SUBDATE/TIMESTAMPADD read an unsigned interval >= 2^63 as negative: ADDDATE(d, 18446744073709551614) = |
Showing 1–30 of 1808
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.147 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.