| Showing all 158 (Edit, Save, CSV, Feed) |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 117983 | 2025-04-15 5:58 | 2025-04-15 10:02 | MySQL Server: Data Dictionary | Verified (233 days) | S2 | 8.0.41 | Any | Any | Huge memory usage while upragding data dictionary with many views |
| 118101 | 2025-05-01 23:58 | 2025-05-13 15:59 | MySQL Server: Data Dictionary | Verified (205 days) | S2 | 8.0.37, 8.0.41, 8.0.42 | Linux | Any | In-Place upgrade fails with out of memory when instance has large number of routines |
| 118367 | 2025-06-05 9:18 | 2025-06-06 10:06 | MySQL Server: Data Dictionary | Verified (181 days) | S1 | 8.0 | Any | Any | The server may fail to start again if it exits abnormally during the upgrade |
| 117135 | 2025-01-08 11:54 | 2025-01-10 12:04 | MySQL Server: DDL | Verified (328 days) | S2 | 8.0 | Any | Any | When executing online ddl rebuilt table, concurrent delete operations may cause row_log memory to be read out of bounds. |
| 117241 | 2025-01-20 7:42 | 2025-02-08 6:21 | MySQL Server: DDL | Not a Bug (299 days) | S2 | 8.0 | Any | Any | Adding an auto-increment primary key to an InnoDB table may lead to data inconsistency. |
| 117563 | 2025-02-25 3:25 | 2025-02-25 7:22 | MySQL Server: DDL | Verified (282 days) | S2 | 8.4.4, 8.0, 9.2.0 | Any | Any | MySQL should check the range of auto-increment values when altering a column |
| 117720 | 2025-03-17 2:39 | 2025-03-17 10:14 | MySQL Server: DDL | Verified (262 days) | S2 | 8030, 8.0.41, 8.4.4 | Any | Any | Instant modification causes inconsistency in double data. |
| 117735 | 2025-03-18 6:21 | 2025-03-18 12:34 | MySQL Server: DDL | Verified (261 days) | S2 | 8.4, 8.0.41 | Any | Any | Concurrent execution of transactions and DDL operations causes abnormal deadlocks. |
| 117754 | 2025-03-20 7:48 | 2025-03-20 10:10 | MySQL Server: DDL | Verified (259 days) | S2 | 8.4.1 9.1.0 , 8.4.4, 8.0.41 | Windows (windows 11) | x86 (x86_64) | Row counts differ with and without an index for same table. |
| 117964 | 2025-04-14 6:21 | 2025-04-16 12:02 | MySQL Server: DDL | Verified (232 days) | S2 | 8.0.41, 8.0.42 | Any | Any | Inconsistent Query Results Between Primary Key and Secondary Index After Online DDL Execution |
| 118151 | 2025-05-09 8:35 | 2025-06-11 5:04 | MySQL Server: DDL | Verified (176 days) | S2 | 8.4.5 | Ubuntu (22.04) | x86 | When creating an index: ERROR 1553 (HY000): Cannot drop index '<unknown key name>': needed in a foreign key constraint |
| 118233 | 2025-05-20 13:54 | 2025-05-20 15:04 | MySQL Server: DDL | Verified (198 days) | S2 | 8.0.42 | Any | Any | Fixed a bug in the DDL for invisible indexes. |
| 118476 | 2025-06-18 8:45 | 2025-07-02 14:47 | MySQL Server: DDL | Verified (169 days) | S2 | 8.0, 8.4 | Red Hat | x86 | Unable to create partition with name '1e3fRQM2GhI' |
| 118888 | 2025-08-25 7:19 | 2025-09-16 11:29 | MySQL Server: DDL | Verified (79 days) | S2 | 8.0.43/8.4.6 | Any | Any | DDL operation fills the entire disk space and eventually fails |
| 119241 | 2025-10-27 11:25 | 2025-10-27 11:29 | MySQL Server: DDL | Open (38 days) | S2 | 8.0.41 | Any | Any | Exception when creating index instance |
| 119467 | 2025-11-27 6:05 | 2025-11-27 6:05 | MySQL Server: DDL | Open | S2 | 8.0.41 | Any | Any | Creating the index directly works, but the operation fails when wrapped in an IF() function, |
| 117186 | 2025-01-13 3:01 | 2025-01-15 6:36 | MySQL Server: DML | Verified (325 days) | S2 | 8.0.40, 8.4.3 | Any | Any | result is incorrect |
| 117233 | 2025-01-18 6:00 | 2025-01-20 5:54 | MySQL Server: DML | Verified (318 days) | S2 | 8.4.1,9.1.0, 8.0.40, 8.4.3 | Windows | x86 | The same query involving TIME type returns different results with and without using an index. |
| 117453 | 2025-02-13 1:51 | 2025-02-13 5:20 | MySQL Server: DML | Verified (294 days) | S2 | 8.4.1 9.1.0, 8.0.41 | Windows (windows 11) | x86 (x86_64) | Unexpected results with ACOS function in WHERE clause. |
| 117612 | 2025-03-03 22:42 | 2025-03-04 11:05 | MySQL Server: DML | Not a Bug (275 days) | S2 | 8.0.40, 8.0.41, 8.4.4 | Any | Any | EVAL in UPDATE statement changes row value before statement is fully parsed |
| 118001 | 2025-04-17 4:15 | 2025-04-21 12:26 | MySQL Server: DML | Verified (227 days) | S2 | 8.4.3, 8.4.5 | Any | Any | delete sql returns error: Temporary file write failure. |
| 118007 | 2025-04-18 2:24 | 2025-04-25 13:30 | MySQL Server: DML | Not a Bug (223 days) | S2 | 8.4.3 | Any | Any | str_TO_DATE( '1980-07-06','YYYY-MM-DD HH24:MI:SS') in dml reports error |
| 118022 | 2025-04-21 4:12 | 2025-04-28 12:23 | MySQL Server: DML | Not a Bug (220 days) | S2 | Any | Any | between date and str_TO_DATE in select where returns incorrect result | |
| 118053 | 2025-04-24 15:47 | 2025-05-19 2:25 | MySQL Server: DML | Verified (223 days) | S2 | 8.4.3, 9.3.0, 8.4.5, 8.0.42 | CentOS | Any | cast((NULLIF) as datetime) returns incorrect result |
| 118092 | 2025-04-30 3:31 | 2025-08-06 12:51 | MySQL Server: DML | Verified (218 days) | S2 | 8.0.41, 8.0.42, 8.4.5, 9.3.0 | Linux | Any | The query result using index is different with not used index |
| 118159 | 2025-05-10 2:12 | 2025-05-13 7:37 | MySQL Server: DML | Duplicate (205 days) | S2 | 8.4.3 | Any | Any | recursive CTE with float returns error: Out of range value |
| 118312 | 2025-05-30 8:12 | 2025-05-30 10:32 | MySQL Server: DML | Verified (188 days) | S2 | 8.0.42, 8.4.5, 9.3.0 | Any | Any | Inconsistent results when evaluating `EXCEPT` or `INTERSECT` operations involving `NULL` |
| 119204 | 2025-10-22 8:10 | 2025-10-23 10:04 | MySQL Server: DML | Verified (42 days) | S2 | 8.0,9.5 | Any | Any | The change of join order may lead to inconsistent update data |
| 117234 | 2025-01-18 6:35 | 2025-01-20 5:58 | MySQL Server: JSON | Verified (318 days) | S2 | 8.4.1,9.1.0, 8.0.40, 8.4.3 | Windows | x86 | Unexpected results when using JSON_ARRAY(NULL) in query predicates. |
| 117454 | 2025-02-13 2:08 | 2025-02-13 5:48 | MySQL Server: JSON | Verified (294 days) | S2 | 8.4.1 9.1.0 , 8.0.41 | Windows (windows 11) | x86 (x86_64) | Unexpected results with JSON_VALID function in WHERE clause. |
| 117674 | 2025-03-12 6:20 | 2025-03-17 9:46 | MySQL Server: JSON | Verified (262 days) | S2 | 8.0.37, 8.0.41, 8.4.4 | Any | Any | JSON value is not recognized by Mysql inside Stored Routines |
| 117927 | 2025-04-10 6:25 | 2025-04-10 7:35 | MySQL Server: JSON | Verified (238 days) | S2 | 8.0.41, 8.4 | Any | Any | duplicate key in table while using tmp table for group by a json data |
| 116895 | 2024-12-06 11:45 | 2024-12-25 3:09 | MySQL Server: Optimizer | Verified (363 days) | S2 | 9.0,8.0, 8.0.40, 8.4.3 | Any | Any | View using IN(SELECT LIMIT) has wrong result |
| 116964 | 2024-12-13 8:06 | 2024-12-13 9:31 | MySQL Server: Optimizer | Verified (356 days) | S2 | 8.0.38, 8.0.40 | Linux | Any | Result mismatch caused by derived condition push down. |
| 117072 | 2024-12-30 9:24 | 2024-12-30 10:06 | MySQL Server: Optimizer | Verified (339 days) | S2 | 8.4.3, 9.1.0, 8.0.40 | Any (Ubuntu 22.04) | Any (x86) | MAX() as a Window Function Returns NULL for the First Row Even With Non-empty Window Frame Under Specific Conditions |
| 117105 | 2025-01-04 10:02 | 2025-01-06 9:43 | MySQL Server: Optimizer | Verified (334 days) | S2 | 8.0.39, 8.0.40 | Any | Any | Dependent subqueries incorrect results |
| 117242 | 2025-01-20 9:13 | 2025-01-20 9:50 | MySQL Server: Optimizer | Verified (318 days) | S2 | 8.0, 8.0.40, 8.4.3 | Ubuntu | x86 | DISTINCT does not fetch all distinct rows when used with GROUP BY |
| 117275 | 2025-01-23 7:14 | 2025-01-23 8:39 | MySQL Server: Optimizer | Closed (315 days) | S2 | 8.0.40 | Any | Any | when index_merge is on, the result is incorrect |
| 117348 | 2025-01-31 10:06 | 2025-01-31 13:56 | MySQL Server: Optimizer | Verified (307 days) | S2 | 8.4, 8.0.41, 8.4.4, 9.2.0 | Debian | x86 | Query with DISTINCT in combination with big_tables returns wrong sortorder |
| 117386 | 2025-02-05 10:13 | 2025-02-05 13:51 | MySQL Server: Optimizer | Verified (302 days) | S2 | 8.0, 8.0.41, 8.4.4 | Ubuntu | x86 | Ambiguous functional index not based on any column under-fetches rows |
| 117387 | 2025-02-05 12:39 | 2025-02-05 15:42 | MySQL Server: Optimizer | Verified (302 days) | S2 | 8.4.4, 8.0.41 | Any | Any | Query returns wrong results when using offset limit subquery in view |
| 117439 | 2025-02-11 14:27 | 2025-02-20 13:12 | MySQL Server: Optimizer | Verified (295 days) | S2 | 8.0, 8.0.41, 8.4.4, 9.2.0 | Ubuntu | x86 | Suspicious behaviour around creation of multi-column indexes |
| 117451 | 2025-02-13 1:33 | 2025-02-13 4:24 | MySQL Server: Optimizer | Verified (294 days) | S2 | 8.4.1 9.1.0, 8.0.41 | Windows (windows 11) | x86 (x86_64) | Comparing a BIGINT column with the result of an IF function using "=" yields unexpected results. |
| 117485 | 2025-02-17 7:04 | 2025-02-17 7:53 | MySQL Server: Optimizer | Verified (290 days) | S2 | 9.1.0, 8.0.41, 8.4.4 | Ubuntu (22.04) | x86 | Incorrect Semi-join Execution |
| 117486 | 2025-02-17 8:04 | 2025-02-17 22:40 | MySQL Server: Optimizer | Verified (290 days) | S2 | 9.1.0, 8.0.41 | Ubuntu (22.04) | x86 | Incorrect Semi-join Execution |
| 117500 | 2025-02-18 11:40 | 2025-03-11 8:56 | MySQL Server: Optimizer | Verified (289 days) | S2 | 9.2.0, 8.0.41, 8.4.4 | Any | Any | result error when row compared with scalar subquery using '<=>' |
| 117549 | 2025-02-24 2:24 | 2025-02-24 4:52 | MySQL Server: Optimizer | Verified (283 days) | S1 | 8.0, 8.0.41, 8.4.4 | Any | Any | Wrong result when use "in (select * from (set operation) d)" |
| 117572 | 2025-02-26 2:37 | 2025-02-26 6:36 | MySQL Server: Optimizer | Verified (281 days) | S2 | 8.0.41 | Ubuntu (22.04) | x86 | The same query yields different results across different versions |
| 117573 | 2025-02-26 4:47 | 2025-03-21 7:12 | MySQL Server: Optimizer | Verified (258 days) | S2 | 9.2.0, 8.0.41, 8.4.4 | Ubuntu (22.04) | x86 | Equivalent inner-join queries return different results |
| 117598 | 2025-02-28 3:28 | 2025-09-22 15:11 | MySQL Server: Optimizer | Verified (279 days) | S2 | 8.0.35, 8.0.41, 8.4.4 | Any | Any | Wrong sort order for queries with ORDER BY DESC when using range comparison with LIMIT |
| 117606 | 2025-02-28 16:01 | 2025-02-28 16:27 | MySQL Server: Optimizer | Verified (279 days) | S1 | 8.4.4, 8.0.41 | Any | Any | Incorrect query result |
| 117619 | 2025-03-05 0:14 | 2025-03-05 5:53 | MySQL Server: Optimizer | Verified (274 days) | S2 | 8.*, 8.0.41, 8.0.44 | Any | Any | MySQL indexes in MyISAM tables not behave as expected. |
| 117634 | 2025-03-06 14:00 | 2025-03-07 12:59 | MySQL Server: Optimizer | Verified (272 days) | S1 | 8.4.4, 8.0.41 | Any | Any | Incorrect query results |
| 117648 | 2025-03-09 14:15 | 2025-03-10 7:19 | MySQL Server: Optimizer | Verified (269 days) | S2 | 9.2.0, 9.1.0, 8.0.41, 8.4.4, | Ubuntu (22.04) | Any | Equivalent straight-join queries with different join orders return different results. |
| 117651 | 2025-03-09 15:43 | 2025-03-10 6:50 | MySQL Server: Optimizer | Verified (269 days) | S2 | 9.2.0, 9.1.0, 8.0.41, 8.4.4 | Ubuntu (22.04) | Any | STRAIGHT_JOIN produces inconsistent results when comparing text values |
| 117653 | 2025-03-10 3:22 | 2025-03-10 5:36 | MySQL Server: Optimizer | Verified (269 days) | S2 | 8.0, 8.0.41, 8.4.4, 9.2.0 | Ubuntu | x86 | Invisible index affects output of query result |
| 117666 | 2025-03-11 10:59 | 2025-03-25 22:54 | MySQL Server: Optimizer | Closed (254 days) | S2 | 8.0.41 | Any | Any | EXPLAIN FORMAT=TREE does not say the index is covering, unlike plain EXPLAIN |
| 117667 | 2025-03-11 12:57 | 2025-03-11 22:03 | MySQL Server: Optimizer | Not a Bug (268 days) | S2 | 9.2.0, 9.1.0, 8.0.41, 8.4.4 | Ubuntu (22.04) | Any | Both INNER JOIN and SEMI JOIN are contradictory |
| 117702 | 2025-03-14 8:48 | 2025-03-14 10:29 | MySQL Server: Optimizer | Verified (265 days) | S2 | 9.1.0 , 8.0.41, 8.4.4, 9.2.0 | Ubuntu (20.04) | Any | Incorrect Query Results When Using DISTINCT and Logical AND in Subquery |
| 117703 | 2025-03-14 9:00 | 2025-03-14 10:39 | MySQL Server: Optimizer | Verified (265 days) | S2 | 9.1.0, 8.0.41, 8.4.4, 9.2.0 | Ubuntu (20.04) | Any | Incorrect Query Results When Using REPEAT (Branch Structure) in Subquery |
| 117704 | 2025-03-14 9:24 | 2025-03-14 10:49 | MySQL Server: Optimizer | Verified (265 days) | S2 | 9.1.0, 8.0.41, 8.4.4, 9.2.0 | Ubuntu (20.04) | Any | WHERE Clause Fails to Filter NULL Values in Condition (col1 = col2) |
| 117714 | 2025-03-14 15:36 | 2025-03-21 1:11 | MySQL Server: Optimizer | Verified (261 days) | S2 | 5.7.42 | Any | Any | Incorrect row filtering when using CAST(... AS DATE) adding an AND condition. |
| 117765 | 2025-03-21 3:09 | 2025-03-21 9:01 | MySQL Server: Optimizer | Verified (258 days) | S2 | 9.2.0, 8.0.41, 8.4.4 | Any | Any | Query result may be wrong if using compound order by inside GROUP_CONCAT |
| 117783 | 2025-03-25 8:45 | 2025-03-26 8:20 | MySQL Server: Optimizer | Verified (253 days) | S2 | 8.0.32, 8.0.41 | Any | Any | optimizer selects the wrong index due to the "low_limit" mechanism |
| 117797 | 2025-03-26 5:55 | 2025-06-04 2:18 | MySQL Server: Optimizer | Not a Bug (183 days) | S1 | 9.2.0 | Any (Ubuntu 22.04) | Any | Lost Update WITH CONSISTENT SNAPSHOT |
| 117811 | 2025-03-27 15:19 | 2025-04-03 14:22 | MySQL Server: Optimizer | Verified (251 days) | S1 | 8.4.4, 8.0.41, 9.2.0 | Any | Any | Incorrect query results for BLOB type |
| 117847 | 2025-04-02 6:29 | 2025-04-02 7:47 | MySQL Server: Optimizer | Verified (246 days) | S2 | 9.1.0 , 8.0.41, 8.4.4, 9.2.0 | Ubuntu (20.04) | Any | NULLIF Filtering Fails in WHERE Clause |
| 117848 | 2025-04-02 6:37 | 2025-04-02 9:50 | MySQL Server: Optimizer | Verified (246 days) | S2 | 9.1.0, 8.0.41, 8.4.4, 9.2.0 | Ubuntu (20.04) | Any | INTERVAL Function Incorrectly Filters Results in WHERE Clause |
| 117849 | 2025-04-02 6:52 | 2025-04-02 9:48 | MySQL Server: Optimizer | Verified (246 days) | S2 | 9.1.0, 8.0.41, 8.4.4, 9.2.0 | Ubuntu (20.04) | Any | Incorrect Query Results When Using Nested String Operation Functions with Conditional Expressions as Inner Parameters |
| 117851 | 2025-04-02 7:05 | 2025-04-02 9:45 | MySQL Server: Optimizer | Verified (246 days) | S2 | 9.1.0, 8.0.41, 8.4.4, 9.2.0 | Ubuntu (20.04) | Any | Incorrect Behavior of EXISTS Condition with OR in SQL Query |
| 117852 | 2025-04-02 7:14 | 2025-04-08 15:00 | MySQL Server: Optimizer | Verified (246 days) | S2 | 9.1.0, 8.0.41, 8.4.4, 9.2.0 | Ubuntu (20.04) | Any | Incorrect Handling of NULL Values with FIELD Function in SQL Query |
| 117853 | 2025-04-02 7:23 | 2025-04-02 9:27 | MySQL Server: Optimizer | Verified (246 days) | S2 | 9.1.0, 8.0.41, 8.4.4, 9.2.0 | Ubuntu (20.04) | Any | Incorrect Result When Using LEFT OUTER JOIN with Subquery |
| 117854 | 2025-04-02 7:31 | 2025-04-02 8:35 | MySQL Server: Optimizer | Verified (246 days) | S2 | 9.1.0, 8.0.41, 8.4.4, 9.2.0 | Ubuntu (20.04) | Any | Incorrect Filtering Behavior of MAKE_SET Function |
| 117855 | 2025-04-02 7:37 | 2025-04-02 8:15 | MySQL Server: Optimizer | Verified (246 days) | S2 | 9.1.0 , 8.0.41, 8.4.4, 9.2.0 | Ubuntu (20.04) | Any | QUOTE Function Incorrectly Handles NULL Values |
| 117856 | 2025-04-02 7:42 | 2025-04-02 8:01 | MySQL Server: Optimizer | Verified (246 days) | S2 | 9.1.0, 8.0.41, 8.4.4, 9.2.0 | Ubuntu (20.04) | Any | REPEAT Function Causes Row Loss in WHERE Clause |
| 117860 | 2025-04-02 10:44 | 2025-05-12 12:20 | MySQL Server: Optimizer | Verified (206 days) | S2 | 9.2.0 | Any (Ubuntu 22.04) | Any | Read another insertion WITH CONSISTENT SNAPSHOT |
| 117911 | 2025-04-08 12:06 | 2025-04-08 14:45 | MySQL Server: Optimizer | Verified (240 days) | S2 | 9.2.0 | Ubuntu (22.04) | Any | INTERSECT operation return wrong result |
| 117926 | 2025-04-09 19:08 | 2025-04-11 21:03 | MySQL Server: Optimizer | Not a Bug (237 days) | S2 | 8.0.41, 9.2.0, 8.4.4 | Ubuntu (22.04) | Any | INTERSECT may incorrectly eliminate duplicate |
| 117930 | 2025-04-10 8:29 | 2025-04-11 16:53 | MySQL Server: Optimizer | Not a Bug (237 days) | S2 | 9.2.0, 8.4.4, 8.0.41 | Ubuntu (22.04) | Any | INTERSECT operation fails on INT ZEROFILL column type. |
| 117941 | 2025-04-10 13:29 | 2025-04-10 14:45 | MySQL Server: Optimizer | Verified (238 days) | S2 | 8.0.41, 8.4.4, 9.2.0 | Any | Any | Inconsistent query results with / without NOT NULL for BLOB type |
| 117945 | 2025-04-11 11:10 | 2025-04-11 12:23 | MySQL Server: Optimizer | Verified (237 days) | S2 | 9.2.0 | Ubuntu (22.04) | Any | UNION operation may return wrong result[ |
| 117959 | 2025-04-13 0:31 | 2025-04-13 16:37 | MySQL Server: Optimizer | Verified (235 days) | S2 | 9.2.0 | Ubuntu (22.04) | Any | PRIMARY KEY leads to incorrect INTERSECT result |
| 118014 | 2025-04-19 16:53 | 2025-04-20 13:53 | MySQL Server: Optimizer | Verified (228 days) | S2 | 9.3.0,8.0, 8.0.42, 8.4.5, 9.3.0 | Any | Any | Wrong Left Join Result |
| 118016 | 2025-04-20 10:34 | 2025-04-21 12:52 | MySQL Server: Optimizer | Verified (228 days) | S2 | 9.3, 9.0, 8.0, 8.0.42 | Any | Any | Wrong inner join result involving subquery containing distinct |
| 118018 | 2025-04-20 13:49 | 2025-08-12 4:14 | MySQL Server: Optimizer | Verified (199 days) | S1 | 9.2.0, 9.3.0 | Ubuntu (22.04) | Any | A query expose a logic bug and performance bug |
| 118019 | 2025-04-20 16:30 | 2025-04-21 7:56 | MySQL Server: Optimizer | Verified (227 days) | S2 | 9.0, 8.0, 9.3.0, 8.4.5, 8.0.42 | Any | Any | Wrong Right Join with a subquery containing distinct and wrong NULL-value expression optimization |
| 118020 | 2025-04-20 23:23 | 2025-08-12 4:14 | MySQL Server: Optimizer | Verified (199 days) | S1 | 9.2.0, 9.3.0 | Any (22.04) | Any | A critical logic bug and performance bug |
| 118024 | 2025-04-21 12:46 | 2025-04-23 8:07 | MySQL Server: Optimizer | Verified (227 days) | S1 | 9.3.0 | Any | Any | Wrong Right Join involving a predicate containing IFNULL and IN |
| 118033 | 2025-04-22 14:51 | 2025-04-23 8:09 | MySQL Server: Optimizer | Verified (225 days) | S2 | 9.3.0 | Any | Any | Wrong Result of an and expression |
| 118061 | 2025-04-26 13:02 | 2025-04-28 7:40 | MySQL Server: Optimizer | Verified (220 days) | S1 | 9.3, 8.4.5, 8.0.42 | Any | Any | wrong inner join result when adding an additional true expression |
| 118063 | 2025-04-27 19:02 | 2025-04-28 7:39 | MySQL Server: Optimizer | Verified (220 days) | S1 | 9.0, 8.0, 8.0.42, 8.4.5, 9.3.0 | Any | Any | Wrong Join Result after creating index on expressions |
| 118071 | 2025-04-28 13:09 | 2025-04-28 14:07 | MySQL Server: Optimizer | Verified (220 days) | S2 | 8.0.41, 8.0.42, 8.4.5, 9.3.0 | Any | Any | Indexed table fails WHERE filtering with different charset value |
| 118073 | 2025-04-28 15:10 | 2025-04-29 6:29 | MySQL Server: Optimizer | Verified (219 days) | S1 | 9.3,9.0,8.0, 8.0.42 | Any | Any | Wrong Inner Join Result |
| 118085 | 2025-04-29 12:14 | 2025-04-29 13:43 | MySQL Server: Optimizer | Verified (219 days) | S1 | 9.3,9.0,8.0,8.0.42, 8.4.5 | Any | Any | Wrong right join result involving subquery |
| 118090 | 2025-04-29 17:33 | 2025-05-07 11:55 | MySQL Server: Optimizer | Can't repeat (211 days) | S1 | 9.3 | MacOS | Any | Wrong inner join result with the subquery contain -0 |
| 118195 | 2025-05-14 13:34 | 2025-05-20 8:23 | MySQL Server: Optimizer | Not a Bug (198 days) | S2 | 9.3.0 | Ubuntu (22.04) | Any | The opposite WHERE clause intersects and is always an empty set. |
| 118196 | 2025-05-14 13:42 | 2025-05-19 21:16 | MySQL Server: Optimizer | Duplicate (199 days) | S2 | 9.3.0 | Ubuntu (22.04) | Any | The opposite HAVING clause intersects and is always an empty set. |
| 118198 | 2025-05-14 14:16 | 2025-05-19 22:49 | MySQL Server: Optimizer | Verified (199 days) | S2 | 9.3.0 | Ubuntu (22.04) | Any | Different intersection orders lead to more than 20,000 times performance gap |
| 118217 | 2025-05-16 16:11 | 2025-09-21 20:45 | MySQL Server: Optimizer | Analyzing (192 days) | S1 | 8.4.5 | Ubuntu | x86 | Issues with the NULLIF function. |
| 118269 | 2025-05-26 9:41 | 2025-05-26 12:29 | MySQL Server: Optimizer | Closed (192 days) | S2 | Any | Any | The result of anti disk hash join is wrong | |
| 118512 | 2025-06-24 7:52 | 2025-10-27 22:53 | MySQL Server: Optimizer | Closed (66 days) | S2 | 8.0.42, 8.4.5, 9.3.0 | Any | Any | The missing semi join condition causes incorrect result |
| 118536 | 2025-06-26 17:55 | 2025-09-21 20:45 | MySQL Server: Optimizer | Analyzing (160 days) | S2 | 8.0.40, 9.3.0 | Linux (RDS, Docker) | Any (Tested on x86_64 and aarch64) | Concurrent CTE queries cause erroneous missing temporary table errors |
| 118540 | 2025-06-27 7:27 | 2025-09-23 4:02 | MySQL Server: Optimizer | Verified (72 days) | S2 | 9.2.0 , 8.0.42 | Linux | Any | Inconsistent results between NATURAL JOIN and INNER JOIN simulated via LEFT JOIN, RIGHT JOIN, and EXCEPT ALL with NULL v |
| 118541 | 2025-06-27 8:31 | 2025-09-23 4:02 | MySQL Server: Optimizer | Verified (72 days) | S2 | 9.2.0 , 8.0.42 | Linux | Any | Inconsistent Results Between NATURAL JOIN and its Equivalent Form Using EXCEPT ALL with Implicit Type Casting |
| 118544 | 2025-06-27 14:18 | 2025-09-23 4:03 | MySQL Server: Optimizer | Verified (72 days) | S2 | 9.2.0 , 9.3.0 | Linux | Any | A potential join operator bug |
| 118548 | 2025-06-28 7:56 | 2025-09-23 6:56 | MySQL Server: Optimizer | Not a Bug (72 days) | S2 | 9.2.0, 9.3.0 | Linux | x86 | A potential bugs in Mysql Server |
| 118669 | 2025-07-16 5:22 | 2025-07-16 6:46 | MySQL Server: Optimizer | Verified (141 days) | S1 | 8 and above, 8.0.42, 8.4.5, 9.3.0 | Any | Any | Issue in applying limit on aggregated data |
| 118682 | 2025-07-18 3:52 | 2025-10-10 7:41 | MySQL Server: Optimizer | Verified (133 days) | S2 | 8.0, 8.0.42 | Any | Any | connection_memory_limit and global_connection_memory_limit don't work |
| 118684 | 2025-07-18 14:54 | 2025-07-21 6:07 | MySQL Server: Optimizer | Verified (136 days) | S2 | 9.2.0, 8.0.42, 8.4.5 | Linux | Any | Inconsistent rows are returned |
| 118689 | 2025-07-21 11:33 | 2025-08-04 9:43 | MySQL Server: Optimizer | Not a Bug (122 days) | S2 | 9.2.0, 8.0.42, 8.4.5, 9.3.0 | Linux | Any | Inconsistent data returns when using INTERESECT operator |
| 118710 | 2025-07-23 12:08 | 2025-07-23 12:42 | MySQL Server: Optimizer | Verified (134 days) | S1 | 8.0.36, 8.0.42, 8.0.43, 8.4.6 | Windows | Any | Optimizer incorrectly simplifies negative float/decimal comparison in JOIN condition, leading to wrong results |
| 118808 | 2025-08-10 11:26 | 2025-08-11 7:00 | MySQL Server: Optimizer | Verified (115 days) | S2 | 9.4.0, 8.4.3, 8.4.6 | Any | Any | Different result with range scan and table scan in sql with subquery |
| 118857 | 2025-08-20 8:39 | 2025-08-20 10:19 | MySQL Server: Optimizer | Verified (106 days) | S2 | 9.2.0 | Linux | Any | Bug Summary: MySQL Returns Incorrect Results for Complex Query with Set Operations |
| 118858 | 2025-08-20 8:51 | 2025-09-23 4:03 | MySQL Server: Optimizer | Verified (72 days) | S2 | 9.2.0 | Linux | Any | Inconsistency between the results returned by MySQL and other vendors' database systems was found during differentiation |
| 118863 | 2025-08-20 14:23 | 2025-08-21 6:30 | MySQL Server: Optimizer | Verified (105 days) | S2 | 8.4.x, 8.4.6 | Any | Any | Complex collection query incorrectly missing '0' |
| 118904 | 2025-08-28 3:20 | 2025-09-04 11:46 | MySQL Server: Optimizer | Verified (94 days) | S2 | 8.0.41+ | Any | Any | Incorrect results could be returned when using index condition pushdown and Range checked for each record |
| 118912 | 2025-08-28 16:24 | 2025-09-04 11:48 | MySQL Server: Optimizer | Verified (94 days) | S1 | 8 and above, 8.0.42, 8.4.5, 9.3.0 | Any | Any | Mismatch in Column values with SUM of IFNULL vs IFNULL of SUM |
| 118913 | 2025-08-29 3:40 | 2025-09-01 10:19 | MySQL Server: Optimizer | Verified (94 days) | S2 | 8.0.41, 9.4.0 | Any | Any | queries have different results for non primary key table and table with primary key |
| 118916 | 2025-08-31 18:26 | 2025-09-05 8:21 | MySQL Server: Optimizer | Duplicate (90 days) | S2 | 9.4.0 | Any | Any | Incorrect result set when querying view with LEFT JOIN, COALESCE and EXISTS subquery |
| 118918 | 2025-09-01 7:30 | 2025-09-04 11:47 | MySQL Server: Optimizer | Verified (92 days) | S2 | 9.4.0 | Any | Any | Inconsistent NULL handling in CTE LEFT JOIN results |
| 118937 | 2025-09-04 4:36 | 2025-09-10 0:43 | MySQL Server: Optimizer | Verified (86 days) | S2 | 9.4.0 | Any | Any | LEFT JOIN with constant functions returns incorrect results when condition is ON FALSE |
| 118941 | 2025-09-05 8:19 | 2025-09-10 14:45 | MySQL Server: Optimizer | Verified (85 days) | S2 | 8.0.x, 8.4.x | Any | Any | Bug Report: DECIMAL(22,2) Column Comparison with -0.001 Excludes 0.00 Row |
| 118949 | 2025-09-05 13:57 | 2025-09-10 0:42 | MySQL Server: Optimizer | Verified (87 days) | S2 | 9.2.0 | Linux (ubuntu 20.04) | Any | MySQL 9.2.0: Complex CASE in JOIN makes INNER vs INTERSECT yield different rows |
| 118980 | 2025-09-10 2:52 | 2025-09-15 16:00 | MySQL Server: Optimizer | Verified (84 days) | S2 | MySQL8.0.41 | Any | Any | queries have different results using and without index |
| 118982 | 2025-09-10 6:55 | 2025-09-26 12:01 | MySQL Server: Optimizer | Not a Bug (69 days) | S1 | 9.4.0 | Linux | Any | Unexpected result of IN operator |
| 119022 | 2025-09-17 12:40 | 2025-09-23 0:51 | MySQL Server: Optimizer | Verified (73 days) | S2 | 9.4.0 | Any | Any | column value change cased by Union ALL |
| 119032 | 2025-09-18 7:52 | 2025-09-23 0:51 | MySQL Server: Optimizer | Verified (73 days) | S2 | 9.2.0 | Any | Any | Inconsistency with MySQL 8.0.36 in MySQL 9.2.0: Equivalent INTERSECT query does not match INNER JOIN result and returns |
| 119041 | 2025-09-19 8:19 | 2025-09-23 9:57 | MySQL Server: Optimizer | Verified (72 days) | S2 | 8.0.25 8.0.40 | Any | Any | statistics automatic update cause poor execution plan |
| 119049 | 2025-09-22 7:23 | 2025-09-22 7:53 | MySQL Server: Optimizer | Closed (73 days) | S2 | 8.0.41 | Linux (5.10.134-19.al8.x86_64) | x86 (x86_64) | Performance regression in 8.0.41 compared to 5.7.37 for queries using limit |
| 119059 | 2025-09-23 3:44 | 2025-09-25 16:07 | MySQL Server: Optimizer | Verified (72 days) | S2 | 9.2.0, 9.4.0 | Any | Any | Inconsistent result behavior when using EXCEPT equivalent NATRUAL JOIN |
| 119068 | 2025-09-25 8:43 | 2025-10-01 14:05 | MySQL Server: Optimizer | Verified (66 days) | S2 | 9.4.0 | Linux | x86 | RIGHT JOIN on VIEW with IN subquery returns incorrect non-NULL value instead of NULL |
| 119074 | 2025-09-26 4:46 | 2025-10-01 13:59 | MySQL Server: Optimizer | Verified (66 days) | S2 | 9.4.0 | Linux | x86 | Incorrect result with derived_condition_pushdown optimization in correlated subquery with LEFT JOIN ON FALSE |
| 119097 | 2025-09-30 9:04 | 2025-10-11 3:24 | MySQL Server: Optimizer | Open (54 days) | S2 | MySQL 8.4.6 | Windows | Other (x64) | STRAIGHT_JOIN returns different results compared to INNER JOIN with identical conditions |
| 119100 | 2025-10-01 1:00 | 2025-10-06 4:18 | MySQL Server: Optimizer | Verified (59 days) | S2 | 9.4.0 | Linux | x86 | WHERE alias IS NULL Fails for Derived Column Using subquery |
| 119110 | 2025-10-07 5:19 | 2025-10-11 3:25 | MySQL Server: Optimizer | Open (54 days) | S2 | 9.4.0 | Linux | x86 | Incorrect NULL filtering in CTE with UNION ALL over view containing LEFT JOIN on FALSE |
| 119117 | 2025-10-09 4:15 | 2025-10-09 4:15 | MySQL Server: Optimizer | Open | S2 | 8.4.6 | Windows | Other (x64) | INNER JOIN returns results when join condition evaluates to false |
| 119121 | 2025-10-09 11:06 | 2025-10-09 11:06 | MySQL Server: Optimizer | Open | S2 | 8.4.6 | Windows | Other (x64) | STRAIGHT_JOIN returns fewer rows than expected when ON condition is true for multiple rows |
| 119127 | 2025-10-10 11:58 | 2025-10-10 11:58 | MySQL Server: Optimizer | Open | S2 | 8.4.6 | Any | Any | INNER JOIN and INTERSECT of LEFT/RIGHT JOINs return different results when unique index is present |
| 119144 | 2025-10-13 12:49 | 2025-10-13 12:49 | MySQL Server: Optimizer | Open | S2 | 8.4.6 | Windows | Any (x64) | INNER JOIN and STRAIGHT_JOIN return different results with identical ABS function conditions |
| 119145 | 2025-10-13 12:53 | 2025-10-13 12:53 | MySQL Server: Optimizer | Open | S2 | 8.4.6 | Any (windows ) | Any (x64) | INNER JOIN and INTERSECT of LEFT/RIGHT JOINs return different results with complex boolean conditions |
| 119156 | 2025-10-15 2:01 | 2025-10-15 2:01 | MySQL Server: Optimizer | Open | S2 | 8.0.41 | CentOS | x86 | Query returns incorrect result (12 vs 2) when using FORCE INDEX compared to optimizer's automatic index selection, when |
| 119187 | 2025-10-18 4:41 | 2025-10-18 4:41 | MySQL Server: Optimizer | Open | S2 | 9.4.0 | Linux | x86 | CTE with correlated EXISTS subquery causes incorrect NULL handling in WHERE clause with IS NULL predicate |
| 119198 | 2025-10-20 19:44 | 2025-10-22 6:59 | MySQL Server: Optimizer | Verified (43 days) | S2 | 8.4.6 | Any | Any | Optimizer with reverse index range scan gives incorrect query result |
| 119220 | 2025-10-23 14:55 | 2025-11-07 9:22 | MySQL Server: Optimizer | Verified (27 days) | S2 | 8.4.6 | Any | x86 | Subquery materialization in LEFT JOIN ON clause loses WHERE conditions |
| 119444 | 2025-11-22 11:32 | 2025-11-27 7:01 | MySQL Server: Optimizer | Open (12 days) | S2 | any | Any | Any | Union with bound variable silently trims result |
| 119453 | 2025-11-24 14:12 | 2025-11-24 14:12 | MySQL Server: Optimizer | Open | S2 | 9.4 | Any | Any | DEFAULT(column) returns wrong result when column is to the right of left join |
| 119454 | 2025-11-24 16:04 | 2025-11-27 5:11 | MySQL Server: Optimizer | Verified (7 days) | S2 | 9.4.0 | Any | Any | Hash join has wrong result when the join equality involves FLOAT or DECIMAL column |
| 119470 | 2025-11-27 14:30 | 2025-11-28 13:06 | MySQL Server: Optimizer | Verified (6 days) | S1 | 8.0.44+ | Any | Any | sql injection |
| 119474 | 2025-11-29 9:29 | 2025-12-01 4:16 | MySQL Server: Optimizer | Verified (3 days) | S2 | 8.0.41 | Any | Any | Result error caused by the subquery_to_derived optimizer switch |
| 119485 | 2025-12-01 14:10 | 2025-12-02 5:32 | MySQL Server: Optimizer | Verified (2 days) | S2 | 9.5.0,8.0.41 | Any | Any | Wrong result with left joins |
| 119488 | 2025-12-01 14:52 | 2025-12-02 4:37 | MySQL Server: Optimizer | Verified (2 days) | S2 | 9.4.0, 9.5.0 | Ubuntu (22.04) | Any | NTERSECT Bug: NULL-Handling Inconsistency Returns Non-Intersecting Row from Outer Joins with NULL Comparisons |
| 119492 | 2025-12-02 11:57 | 2025-12-03 3:38 | MySQL Server: Optimizer | Closed (1 day) | S2 | 8.0.41 | Any | Any | Inconsistent data types of the IN condition in JOIN queries leads to incorrect query results. |
| 119499 | 2025-12-03 15:20 | 2025-12-03 15:20 | MySQL Server: Optimizer | Open | S2 | 9.5.0,8.0.41 | Any | Any | Item_view_ref::used_tables() is wrong, leads to wrong query result |
| 117223 | 2025-01-17 7:33 | 2025-01-17 9:16 | MySQL Server: Data Types | Verified (321 days) | S2 | 8.4.1 9.1.0, 8.0.40 | Windows | x86 | Query results are unexpected with BIT data type and IN operator. |
| 117232 | 2025-01-18 5:48 | 2025-01-20 5:29 | MySQL Server: Data Types | Verified (318 days) | S2 | 8.4.1,9.1.0, 8.4.0, 8.4.3 | Windows (windows 11) | x86 | Unexpected results with YEAR data type comparisons in query predicates. |
| 118591 | 2025-07-07 11:28 | 2025-07-10 7:11 | MySQL Server: Data Types | Duplicate (147 days) | S1 | 9.3.0 | Any | Any | empty string parse to 0 in SET statement, which is different from that in the SELECT query |
| 119432 | 2025-11-20 8:47 | 2025-11-27 7:06 | MySQL Server: Data Types | Open (13 days) | S1 | 8.4.6 | Any | Any | Inconsistent time conversion behaviors between text and integer |
| 119433 | 2025-11-20 9:30 | 2025-11-27 7:06 | MySQL Server: Data Types | Open | S1 | 8.4.6 | Any | Any | Inconsistent date conversion behaviors between text and integer |
| Showing all 158 (Edit, Save, CSV, Feed) |
