| Showing 1-1000 of 2284 (Edit, Save, CSV, Feed) | Show Next 1000 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 120582 | 2026-05-31 10:11 | 2026-05-31 10:11 | MySQL Server: Optimizer | Open | S3 | 8.0.44 | MacOS | Any | unique index causes incorrect result when comparing DOUBLE and BIGINT |
| 120581 | 2026-05-31 9:02 | 2026-05-31 9:02 | MySQL Server: Optimizer | Open | S2 | 8.0.44 | MacOS | Any | unique index causes incorrect result for IN comparison with implicit type conversion |
| 120580 | 2026-05-31 7:52 | 2026-05-31 7:53 | MySQL Server: Optimizer | Open | S3 | 8.0.44 | Any | Any | MyISAM prefix index causes incorrect range query result |
| 120579 | 2026-05-30 11:39 | 2026-05-30 11:39 | MySQL Server: Optimizer | Open | S3 | 8.0.45 | Any | Any | LIKE query returns inconsistent results with MyISAM prefix index |
| 120578 | 2026-05-30 9:05 | 2026-05-30 9:05 | MySQL Server: Optimizer | Open | S3 | 8.0.45 | Any | Any | Multiple-Column Index Creation Changes Query Results |
| 120575 | 2026-05-30 6:57 | 2026-05-30 6:57 | MySQL Server: Optimizer | Open | S2 | 8.0.41+ | Any | Any | Range optimizer chooses bad range plan for large IN lists and execution is very slow and memory usage spikes. |
| 120574 | 2026-05-29 14:05 | 2026-05-29 14:12 | MySQL Server: Optimizer | Open | S2 | 8.0.41 | Any | Any | Range optimizer exceeds memory limit and chooses bad range plan for large IN lists |
| 120555 | 2026-05-27 8:22 | 2026-05-27 11:39 | MySQL Server: Optimizer | Verified (4 days) | S2 | 8.0.45 | Ubuntu | Any | Equivalent VIEW and CTE queries return different row counts with EXISTS, BINARY ENUM comparison, and LEFT JOIN |
| 120543 | 2026-05-25 9:57 | 2026-05-27 5:37 | MySQL Server: Optimizer | Verified (4 days) | S2 | 8.4.8 | Any | Any | MySQL `MERGE` vs `TEMPTABLE` view evaluation changes `MAX(SET)` result |
| 120535 | 2026-05-24 5:29 | 2026-05-26 12:42 | MySQL Server: Optimizer | Verified (5 days) | S3 | 8.0.45 | Any | Any | Incorrect Query Result: IN and NOT IN return the same row simultaneously (boolean logic violation) |
| 120534 | 2026-05-24 5:19 | 2026-05-26 12:26 | MySQL Server: Optimizer | Verified (5 days) | S3 | 8.0.45 | Any | Any | Wrong Query Result Due to Incorrect Evaluation of GREATEST() with Mixed Types in OR (||) Boolean Context |
| 120533 | 2026-05-23 12:35 | 2026-05-26 8:30 | MySQL Server: Optimizer | Verified (5 days) | S2 | 8.0.45 | Ubuntu | x86 | A LEFT JOIN over DECIMAL ZEROFILL UNIQUE wrongly loses an obvious match |
| 120531 | 2026-05-23 12:33 | 2026-05-26 7:24 | MySQL Server: Optimizer | Verified (5 days) | S2 | 8.0.45 | Ubuntu | x86 | A NULL comparison inside an IN subquery becomes spuriously true in the original path |
| 120526 | 2026-05-22 11:47 | 2026-05-26 6:59 | MySQL Server: Optimizer | Verified (5 days) | S3 | 8.0.43 | Any | Any | Wrong result for IN subquery involving CURRENT_USER(), BIT column, and UNIQUE prefix index |
| 120525 | 2026-05-22 9:41 | 2026-05-26 6:49 | MySQL Server: Optimizer | Verified (5 days) | S2 | 8.0.45 | Ubuntu (Ubuntu 20.04.4 LTS) | x86 (Intel(R) Xeon(R) Platinum 8358P @ 2.60GHz (64 Cores, 96MB L3 Cache)) | Append-Only Growth Breaks Subset Monotonicity for Implicit VARCHAR-to-DECIMAL IN-Subquery Comparison |
| 120524 | 2026-05-22 9:40 | 2026-05-26 6:27 | MySQL Server: Optimizer | Verified (5 days) | S2 | 8.0.45 | Ubuntu (Ubuntu 20.04.4 LTS) | x86 (Intel(R) Xeon(R) Platinum 8358P @ 2.60GHz (64 Cores, 96MB L3 Cache)) | Materialized Correlated EXISTS Returns Positive COUNT(*) But No Rows for Implicit VARCHAR-to-YEAR Comparison |
| 120522 | 2026-05-22 6:39 | 2026-05-22 6:39 | MySQL Server: Optimizer | Open | S5 | 9.7.0 | Any | Any | Sub‑optimal execution plan for multi‑table row‑value IN condition leads to full index scan instead of index range scans |
| 120520 | 2026-05-21 16:34 | 2026-05-25 19:58 | MySQL Server: Optimizer | Verified (6 days) | S3 | 8.0.43 | Any | Any | Wrong result for IS NOT UNKNOWN when NULLIF() uses CURRENT_USER() as an argument |
| 120519 | 2026-05-21 15:49 | 2026-05-25 19:43 | MySQL Server: Optimizer | Verified (6 days) | S3 | 8.0.43 | Any | Any | Wrong result for BETWEEN predicate with LONGBLOB prefix PRIMARY KEY and implicit type conversion |
| 120518 | 2026-05-21 14:29 | 2026-05-25 19:27 | MySQL Server: Optimizer | Verified (6 days) | S3 | 8.0.43 | Any | Any | Wrong result for SOME quantified comparison with ELT() returning NULL and PRIMARY KEY optimization |
| 120515 | 2026-05-21 10:36 | 2026-05-21 11:55 | MySQL Server: Optimizer | Verified (10 days) | S3 | 8.0 | Any | Any | Wrong result for NOT BETWEEN involving interval arithmetic and implicit type conversion |
| 120512 | 2026-05-21 7:43 | 2026-05-21 11:23 | MySQL Server: Optimizer | Verified (10 days) | S3 | 8.0 | Any | Any | ALL quantified comparison involving implicit numeric conversion of BLOB values |
| 120511 | 2026-05-21 7:24 | 2026-05-21 8:26 | MySQL Server: Optimizer | Verified (10 days) | S3 | 8.0.46 | Ubuntu | x86 | LEFT JOIN ON with IN (empty subquery) produces a spurious match |
| 120502 | 2026-05-20 10:16 | 2026-05-20 10:16 | MySQL Server: Optimizer | Open | S5 | 9.7.0 | Any | Any | Impossible WHERE with inequality-only contradictions not optimized |
| 120495 | 2026-05-18 16:12 | 2026-05-27 6:34 | MySQL Server: Optimizer | Verified (4 days) | S5 | 9.7.0 | Any | Any | Incorrect Cardinality Estimation for Index Lookup with Equality Predicate on the Index Column |
| 120493 | 2026-05-18 14:26 | 2026-05-19 19:53 | MySQL Server: Optimizer | Verified (12 days) | S3 | 8.0 | Any | Any | Wrong result for SOME quantified comparison in WHERE clause |
| 120491 | 2026-05-18 5:53 | 2026-05-18 12:22 | MySQL Server: Optimizer | Verified (13 days) | S2 | 8.0.46 | CentOS | Any | Semijoin returns wrong results for VARCHAR-to-DECIMAL comparison with non-canonical numeric strings |
| 120490 | 2026-05-18 3:24 | 2026-05-18 8:26 | MySQL Server: Optimizer | Verified (13 days) | S5 | 9.7.0 | Any | Any | Join Not Eliminated When Constant Table is Empty Due to PrimaryKeyCol IN (NULL) Condition |
| 120477 | 2026-05-14 15:50 | 2026-05-18 10:26 | MySQL Server: Optimizer | Verified (13 days) | S5 | 9.7.0 | Any | Any | Index Not Used for HAVING Without GROUP BY or aggregate functions |
| 120476 | 2026-05-14 11:53 | 2026-05-18 8:25 | MySQL Server: Optimizer | Verified (13 days) | S2 | 9.6.0 | Linux | Any | Index Merge Union returns duplicate row for overlapping OR conditions, producing wrong result count |
| 120475 | 2026-05-14 9:09 | 2026-05-18 10:20 | MySQL Server: Optimizer | Verified (13 days) | S2 | 8.0.46 | Linux | Any | Index Merge Intersection incorrectly drops matching rows in SELECT with OR predicate, returning wrong result count |
| 120472 | 2026-05-14 4:07 | 2026-05-18 9:40 | MySQL Server: Optimizer | Verified (13 days) | S3 | 8.0.43 | Any | Any | Wrong Result After Removing Semantically Redundant RIGHT JOIN ... ON FALSE |
| 120456 | 2026-05-12 15:02 | 2026-05-17 23:00 | MySQL Server: Optimizer | Verified (14 days) | S2 | 8.0.46 | Linux | Any | Semijoin Nested Loop index lookup uses raw VARCHAR keys against a DOUBLE B-tree, causing mismatches when the string over |
| 120422 | 2026-05-08 8:56 | 2026-05-08 8:56 | MySQL Server: Optimizer | Open | S2 | 9.7.0 (also reproducible in 8.0.x) | Any | Any | ORDER BY ignored when internal_tmp_mem_storage_engine = TempTable with GROUP BY on CTE |
| 120420 | 2026-05-08 8:19 | 2026-05-08 8:19 | MySQL Server: Optimizer | Open | S3 | 9.7.0 (also reproducible in 8.0.x) | Any | Any | ORDER BY ignored when internal_tmp_mem_storage_engine = TempTable with GROUP BY on temp table |
| 120419 | 2026-05-08 7:50 | 2026-05-08 19:26 | MySQL Server: Optimizer | Verified (23 days) | S3 | 8.0.46 | Linux | Any | rematerialized temptable cause wrong order |
| 120377 | 2026-04-29 8:45 | 2026-04-29 10:47 | MySQL Server: Optimizer | Verified (32 days) | S3 | 8.0.43 (MySQL Community Server - GPL) | Any (Docker container) | Any (x86_64) | Incorrect row count in MySQL when using LATERAL derived table with DISTINCT and CASE |
| 120363 | 2026-04-28 6:58 | 2026-04-30 8:28 | MySQL Server: Optimizer | Verified (31 days) | S3 | 8.0.43 | Any (Docker container) | Any (x86_64) | LEFT JOIN ON FALSE causes incorrect NULL comparison result in MySQL |
| 120352 | 2026-04-27 9:34 | 2026-04-28 4:26 | MySQL Server: Optimizer | Verified (33 days) | S2 | 9.6.0 | Linux | Any | Prefix index with length 1 causes incorrect "Zero rows" optimization with float overflow literal in range condition |
| 120350 | 2026-04-27 8:35 | 2026-04-28 4:31 | MySQL Server: Optimizer | Verified (33 days) | S2 | 9.6.0 | Linux | Any | Prefix index on TEXT column causes range scan to miss qualifying rows in MySQL |
| 120344 | 2026-04-26 6:43 | 2026-04-27 4:04 | MySQL Server: Optimizer | Verified (34 days) | S2 | 9.6.0 | Any | Any | VIEW and equivalent CTE return different results with UNION, YEAR(0), and repeated reference in subquery |
| 120313 | 2026-04-21 17:11 | 2026-04-22 4:43 | MySQL Server: Optimizer | Verified (39 days) | S1 | 9.6 | Linux (Observed on Linux via the `mysql:9.6` ) | Any | Wrong result when only GROUP BY key order is changed in a join query with nested window-function input |
| 120312 | 2026-04-21 16:58 | 2026-04-22 4:40 | MySQL Server: Optimizer | Verified (39 days) | S2 | 9.6 | Linux (Observed on Linux via the `mysql:9.6` ) | Any | Wrong result for MIN(TIME) UNION ALL DATE after view extraction |
| 120311 | 2026-04-21 16:52 | 2026-04-22 4:38 | MySQL Server: Optimizer | Verified (39 days) | S2 | 9.6 | Linux (Observed on Linux via the `mysql:9.6` ) | Any | Wrong result for grouped SUM(DISTINCT ...) with DENSE_RANK() after view extraction |
| 120310 | 2026-04-21 16:45 | 2026-04-22 4:34 | MySQL Server: Optimizer | Verified (39 days) | S2 | 9.6 | Linux (Observed on Linux via the `mysql:9.6` ) | Any | Wrong result for MAX(BIT(8)) UNION ALL BLOB after view extraction in a window-function workload |
| 120308 | 2026-04-21 14:03 | 2026-04-22 4:27 | MySQL Server: Optimizer | Verified (39 days) | S2 | 9.6 | Linux (Observed on Linux via the `mysql:9.6` ) | Any | Wrong result for string-vs-`BIT` comparison in a window-function query |
| 120307 | 2026-04-21 14:02 | 2026-04-22 4:23 | MySQL Server: Optimizer | Verified (39 days) | S2 | 9.6 | Linux (Observed on Linux via the `mysql:9.6` ) | Any | Wrong result for `<= ANY (subquery)` in a window-function query |
| 120302 | 2026-04-20 9:51 | 2026-04-20 11:26 | MySQL Server: Optimizer | Verified (41 days) | S2 | 9.6.0 | Any | Any | Inconsistent results between VIEW and CTE involving YEAR(DATETIME), UNION, and JOIN. |
| 120300 | 2026-04-20 9:02 | 2026-04-20 11:03 | MySQL Server: Optimizer | Verified (41 days) | S2 | 8.0.45 | Any (Observed on Linux via the `mysql:9.6` ) | Any | Window function logic mismatch across engines |
| 120299 | 2026-04-20 9:00 | 2026-04-20 10:41 | MySQL Server: Optimizer | Verified (41 days) | S2 | 9.6 | Linux (Observed on Linux via the `mysql:9.6` ) | Any | mismatch in `DELETE ... EXISTS` under window function query |
| 120297 | 2026-04-20 8:44 | 2026-04-20 10:04 | MySQL Server: Optimizer | Verified (41 days) | S2 | 8.0.32 | Any | Any | query_term.cc:320 assert(false) crash — UNION query triggers unhandled AccessPath |
| 120296 | 2026-04-20 7:50 | 2026-04-20 9:24 | MySQL Server: Optimizer | Verified (41 days) | S2 | 8.0.45 | Ubuntu (Ubuntu 20.04.4 LTS) | x86 (Intel(R) Xeon(R) Platinum 8358P @ 2.60GHz (64 Cores, 96MB L3 Cache)) | Materialized Correlated EXISTS Loses Implicit VARCHAR-to-YEAR Coercion,Causing Plan-Dependent Result Divergence |
| 120294 | 2026-04-19 17:16 | 2026-04-27 14:11 | MySQL Server: Optimizer | Verified (34 days) | S3 | 9.6.0; 8.0.45 | Any | Any | Inconsistent fractional seconds precision (FSP) for TIME function results between VIEW and CTE |
| 120293 | 2026-04-19 17:10 | 2026-04-27 14:10 | MySQL Server: Optimizer | Verified (34 days) | S1 | 9.6.0; 8.0.45 | Any | Any | Query result inconsistency between VIEW and CTE involving a UNION of scalar aggregation and grouped aggregation |
| 120292 | 2026-04-19 17:01 | 2026-04-27 14:09 | MySQL Server: Optimizer | Verified (34 days) | S2 | 9.6.0; 8.0.45 | Any | Any | Inconsistent results between VIEW and CTE involving IN subquery and RIGHT JOIN |
| 120291 | 2026-04-19 16:45 | 2026-04-27 13:16 | MySQL Server: Optimizer | Verified (34 days) | S2 | 9.6.0 | Any | Any | Inconsistent results between VIEW and CTE involving EXISTS subquery and LEFT JOIN |
| 120289 | 2026-04-19 14:35 | 2026-04-20 8:13 | MySQL Server: Optimizer | Verified (41 days) | S2 | 9.6 | Linux (Observed on Linux via the `mysql:9.6` ) | Any | Mismatch in indexed `IN` under windows function query |
| 120288 | 2026-04-19 14:29 | 2026-04-20 8:04 | MySQL Server: Optimizer | Verified (41 days) | S2 | 8.0.45 | Linux (Observed on Linux via the `mysql:9.6` ) | Any | Window function logic mismatch in indexed `NOT IN` |
| 120286 | 2026-04-19 5:14 | 2026-04-20 7:53 | MySQL Server: Optimizer | Verified (41 days) | S2 | 8.0.45 | Any | Any | `SUM(DISTINCT pk)` returns `NULL` with a window function when a secondary index is used for group-by scanning |
| 120285 | 2026-04-18 15:49 | 2026-04-18 15:54 | MySQL Server: Optimizer | Open (43 days) | S2 | 8.0.45 | Ubuntu (Ubuntu 20.04.4 LTS) | x86 (Intel(R) Xeon(R) Platinum 8358P @ 2.60GHz (64 Cores, 96MB L3 Cache)) | Materialized Semijoin + Outer ORDER BY Loses Rows for Correlated EXISTS,Causing Plan-Dependent Result Divergence |
| 120284 | 2026-04-18 15:46 | 2026-04-20 7:33 | MySQL Server: Optimizer | Verified (41 days) | S2 | 8.0.45 | Ubuntu (Ubuntu 20.04.4 LTS) | x86 (Intel(R) Xeon(R) Platinum 8358P @ 2.60GHz (64 Cores, 96MB L3 Cache)) | Materialized `IN (subquery)` Loses VARCHAR-to-YEAR Coercion,Causing Plan-Dependent Result Divergence |
| 120279 | 2026-04-17 7:23 | 2026-04-17 14:09 | MySQL Server: Optimizer | Verified (44 days) | S3 | 8.0.43 (MySQL Community Server - GPL) | Any | Any | Severe performance degradation with window function + joins (works fast in PostgreSQL/DuckDB/TiDB) |
| 120275 | 2026-04-16 7:10 | 2026-04-20 6:51 | MySQL Server: Optimizer | Verified (41 days) | S2 | 8.0.45 | Ubuntu (Ubuntu 20.04.4 LTS) | x86 (Intel(R) Xeon(R) Platinum 8358P @ 2.60GHz (64 Cores, 96MB L3 Cache)) | DATE Index Lookup Loses Existing JOIN Matches Even with Explicit CAST(MEDIUMTEXT AS DATE), Causing S1/S2 Divergence |
| 120271 | 2026-04-15 10:54 | 2026-04-16 21:39 | MySQL Server: Optimizer | Verified (45 days) | S3 | 8.0.43 (MySQL Community Server - GPL) | Any (Docker container) | Any (x86_64) | Logic error: EXISTS subquery treated as constant TRUE yields different result than literal TRUE |
| 120270 | 2026-04-15 9:49 | 2026-04-16 21:20 | MySQL Server: Optimizer | Verified (45 days) | S1 | 8.0.45 | Any | Any | Incorrect result for INTERSECT ALL with semantically equivalent EXCEPT operands when right EXCEPT left operand is wrap |
| 120265 | 2026-04-14 8:24 | 2026-04-14 9:47 | MySQL Server: Optimizer | Verified (47 days) | S1 | 9.6.0 | Any | Any | Query returns with UNION, INTERSECT ALL and Derived SELECT DISTINCT |
| 120263 | 2026-04-14 5:30 | 2026-04-14 10:56 | MySQL Server: JSON | Verified (47 days) | S2 | 8.0.45 | Any | Any | Inconsistent results for query with JSON_CONTAINS and CAST(... AS SIGNED) |
| 120261 | 2026-04-14 2:52 | 2026-04-14 4:32 | MySQL Server: Optimizer | Verified (47 days) | S2 | 8.4.8 | Any | Any | CREATE VIEW materialization changes a key scalar output |
| 120260 | 2026-04-14 2:48 | 2026-04-14 4:42 | MySQL Server: Optimizer | Verified (47 days) | S2 | 8.4.8 | Any | Any | CREATE VIEW materialization changes byte-valued outputs after aggregate or window processing |
| 120259 | 2026-04-14 2:43 | 2026-04-14 4:49 | MySQL Server: Optimizer | Verified (47 days) | S2 | 8.4.8 | Any | Any | CREATE VIEW materialization changes byte-valued UNION results |
| 120258 | 2026-04-14 2:07 | 2026-04-14 4:45 | MySQL Server: Optimizer | Verified (47 days) | S2 | 8.4.8 | Any | Any | CREATE VIEW materialization changes NULL aggregate outputs into numeric values after GROUP BY |
| 120256 | 2026-04-13 11:44 | 2026-04-13 12:48 | MySQL Server: Optimizer | Verified (48 days) | S2 | 8.4.8 | Any | Any | CREATE VIEW materialization turns zero datetime values into runtime timestamps in UNION ALL output |
| 120255 | 2026-04-13 11:24 | 2026-04-13 13:04 | MySQL Server: Optimizer | Verified (48 days) | S2 | 8.4.8 | Any | Any | CREATE VIEW materialization changes grouped results when replacing a grouped CTE or derived input |
| 120253 | 2026-04-13 9:14 | 2026-04-13 10:18 | MySQL Server: Optimizer | Verified (48 days) | S3 | 8.0.45 | Ubuntu (Ubuntu 20.04.4 LTS) | x86 (Intel(R) Xeon(R) Platinum 8358P @ 2.60GHz (64 Cores, 96MB L3 Cache)) | Index Lookup Skips CAST for LONGTEXT-to-DATE Coercion in JOIN,Causing Plan-Dependent Result Divergence |
| 120248 | 2026-04-11 9:16 | 2026-04-13 4:56 | MySQL Server: Optimizer | Verified (48 days) | S3 | 8.4.8 | Ubuntu | Any | Changing the order of GROUPING columns gives wrong results |
| 120225 | 2026-04-07 13:40 | 2026-04-08 4:30 | MySQL Server: Optimizer | Verified (53 days) | S3 | 8.0.43 (MySQL Community Server - GPL) | Any (Docker container) | Any (x86_64) | Inconsistent behavior between SELECT and DELETE/UPDATE with EXISTS and LEFT JOIN subquery |
| 120224 | 2026-04-07 12:25 | 2026-04-08 4:34 | MySQL Server: Optimizer | Verified (53 days) | S3 | 8.0.43 (MySQL Community Server - GPL) | Any (Docker container) | Any (x86_64) | Inconsistent row counts for DELETE vs SELECT with EXISTS and lateral subquery on the same table |
| 120223 | 2026-04-07 12:06 | 2026-04-09 19:33 | MySQL Server: Data Types | Verified (52 days) | S2 | 9.6.0 | Linux | Any | VECTOR(0) silently accepted, produces unusable column with corrupted metadata (dimension 4294967295) |
| 120222 | 2026-04-07 12:02 | 2026-04-09 19:30 | MySQL Server: Data Types | Verified (52 days) | S2 | 9.6.0 | Linux | Any | VECTOR(n) dimension silently wraps to wrong value due to integer overflow in parser |
| 120217 | 2026-04-05 12:27 | 2026-04-06 5:24 | MySQL Server: Optimizer | Verified (55 days) | S3 | 9.6.0 | Ubuntu (22.04) | Any | GROUPING() in ORDER BY of EXISTS/IN/ALL/ANY subquery: invalid arguments not rejected |
| 120215 | 2026-04-04 16:59 | 2026-04-06 5:38 | MySQL Server: Optimizer | Verified (55 days) | S3 | 9.6.0 | Ubuntu (22.04) | Any | Inconsistent window aggregate results with GROUP BY ... WITH ROLLUP |
| 120203 | 2026-04-02 2:35 | 2026-04-04 19:49 | MySQL Server: Optimizer | Verified (57 days) | S2 | 8.0.45 | Any | Any | MySQL returns an incorrect result for an indexed comparison between an `INT` column and a non-integer function value. |
| 120179 | 2026-03-30 10:54 | 2026-03-30 12:26 | MySQL Server: Optimizer | Verified (62 days) | S3 | 8.0.43 (MySQL Community Server - GPL) | Any (Docker container) | Any (x86_64) | NoREC Test: COUNT(*) vs SUM(CASE...) produces inconsistent results with RIGHT JOIN + LEFT JOIN |
| 120174 | 2026-03-28 9:25 | 2026-03-29 20:21 | MySQL Server: Optimizer | Verified (63 days) | S3 | 8.0.45 | Ubuntu (22.04) | Any | Incorrect empty result for BETWEEN on binary string columns when a UNIQUE index is used |
| 120172 | 2026-03-28 9:14 | 2026-03-29 20:15 | MySQL Server: Optimizer | Verified (63 days) | S3 | 8.0.45 | Ubuntu (22.04) | Any | Inconsistent result: NOT IN (subquery on BIT column) differs when using secondary index vs IGNORE INDEX |
| 120171 | 2026-03-28 8:58 | 2026-03-29 20:06 | MySQL Server: Optimizer | Verified (63 days) | S3 | 8.0.45 | Ubuntu (22.04) | Any | Wrong result: LEFT JOIN empty derived table + WHERE equality uses literal from SELECT list |
| 120159 | 2026-03-26 11:41 | 2026-03-27 4:57 | MySQL Server: Optimizer | Verified (66 days) | S3 | 8.0.43 (MySQL Community Server - GPL) | Any (Docker container) | Any (x86_64) | RIGHT JOIN + Complex Subqueries Returns Extra Rows |
| 120158 | 2026-03-26 6:04 | 2026-03-29 19:37 | MySQL Server: Optimizer | Verified (63 days) | S2 | 8.0.45 | Ubuntu (Ubuntu 20.04.4 LTS) | x86 (Intel(R) Xeon(R) Platinum 8358P @ 2.60GHz (64 Cores, 96MB L3 Cache)) | Incorrect result (NULL included) in index lookup/MAX() on FLOAT ZEROFILL column when filtering by 0.0 |
| 120152 | 2026-03-25 8:50 | 2026-03-26 9:05 | MySQL Server: Optimizer | Verified (66 days) | S3 | 8.0.43 (MySQL Community Server - GPL) | Any (Docker container) | Any (x86_64) | Unexpected behavior of LEFT JOIN + empty subquery with NULL comparison in WHERE clause |
| 120146 | 2026-03-25 6:22 | 2026-05-28 14:53 | MySQL Server: Optimizer | Open (3 days) | S2 | 9.6.0 | Linux (ubuntu 20.04) | x86 | Wrong result due to incorrect const-table pruning for NOT IN on FLOAT UNIQUE column in MEMORY engine |
| 120145 | 2026-03-25 6:05 | 2026-03-25 19:22 | MySQL Server: Optimizer | Verified (67 days) | S2 | 8.0.45 | Linux (ubuntu 20.04) | x86 | Incorrect empty result after relocating a HAVING predicate into a derived-table boolean column with WHERE ref1 |
| 120142 | 2026-03-25 3:09 | 2026-03-25 20:29 | MySQL Server: JSON | Verified (67 days) | S3 | 8.0.45 | Any | Any | Incorrect result with DISTINCTROW and JSON_OBJECTAGG when replacing COALESCE(SUM(NULL),0) with constant |
| 120132 | 2026-03-23 11:28 | 2026-03-24 7:45 | MySQL Server: Optimizer | Verified (68 days) | S3 | 8.4.8 | Any | Any | Unexpected Query Results Caused by Prefix Index on TEXT Column |
| 120131 | 2026-03-23 11:27 | 2026-03-24 7:40 | MySQL Server: Optimizer | Verified (68 days) | S3 | 8.0.45 | Any | Any | Bug in Query Behavior due to ZEROFILL in DOUBLE Column |
| 120123 | 2026-03-20 7:15 | 2026-03-20 12:18 | MySQL Server: Optimizer | Verified (72 days) | S3 | 8.0.45 | Any | Any | Inconsistent query results when using EXISTS subqueries with MyISAM engine in derived tables. |
| 120122 | 2026-03-20 4:58 | 2026-03-20 12:06 | MySQL Server: Optimizer | Verified (72 days) | S3 | 8.0.45 | Linux | x86 | Inconsistent evaluation of GREATEST() with ZEROFILL column in OUTER JOIN queries |
| 120111 | 2026-03-19 9:14 | 2026-03-19 14:10 | MySQL Server: JSON | Verified (73 days) | S3 | 8.0.45 | Any | Any | Unexpected row elimination when using DISTINCT on JSON_SET output |
| 120110 | 2026-03-19 9:04 | 2026-03-19 14:07 | MySQL Server: JSON | Verified (73 days) | S3 | 8.0.45 | Any | Any | Wrong result: DISTINCT eliminates JSON_OBJECT result containing NULL value |
| 120109 | 2026-03-19 9:01 | 2026-03-19 14:03 | MySQL Server: JSON | Verified (73 days) | S3 | 8.0.45 | Any | Any | Wrong result: DISTINCT eliminates JSON_ARRAY(NULL) result |
| 120107 | 2026-03-19 8:40 | 2026-03-19 13:34 | MySQL Server: JSON | Verified (73 days) | S3 | 8.0.45 | Any | Any | DISTINCT eliminates non-duplicate rows for JSON_OBJECTAGG results |
| 120106 | 2026-03-19 7:49 | 2026-03-19 8:33 | MySQL Server: Optimizer | Verified (73 days) | S1 | 8.0.45 | Any | Any | Optimizer incorrectly handles constant derived table in RIGHT JOIN |
| 120102 | 2026-03-19 1:34 | 2026-03-19 8:22 | MySQL Server: JSON | Verified (73 days) | S3 | 8.0.45 | Any | Any | Incorrect DISTINCT behavior with JSON_ARRAYAGG when aggregating NULL-only groups |
| 120099 | 2026-03-18 12:08 | 2026-03-19 8:04 | MySQL Server: Optimizer | Verified (73 days) | S1 | 8.0.45 | Any | Any | Query returns wrong result when condition involves CAST(division AS CHAR) |
| 120098 | 2026-03-18 9:58 | 2026-03-18 10:59 | MySQL Server: Optimizer | Verified (74 days) | S1 | 8.0.45 | Any | Any | Incorrect result when using EXISTS with INTERSECT ALL and correlated subquery |
| 120097 | 2026-03-18 9:34 | 2026-03-18 9:48 | MySQL Server: Optimizer | Verified (74 days) | S1 | 8.0.45 | Any | Any | Incorrect result set when use INTERSECT ALL |
| 120095 | 2026-03-18 8:42 | 2026-03-31 1:45 | MySQL Server: DML | Open (61 days) | S3 | 8.4.8, 8.0.41 | Any | Any | query result changed after UPDATE HISTOGRAM, caused by query plan changed to "skip scan" |
| 120094 | 2026-03-18 8:29 | 2026-03-18 9:35 | MySQL Server: Optimizer | Verified (74 days) | S1 | 8.0.45 | Any | Any | Query returns incorrect results due to incorrect handling of predicate logic |
| 120091 | 2026-03-18 6:13 | 2026-03-18 9:01 | MySQL Server: Optimizer | Verified (74 days) | S3 | 8.0.45 | Linux | x86 | Incorrect result with OUTER JOIN on DECIMAL compared to floating-point condition when partitioned by IS NOT NULL predica |
| 120087 | 2026-03-17 13:12 | 2026-03-18 4:58 | MySQL Server: Optimizer | Verified (74 days) | S2 | 8.0.45 | Linux | x86 | Incorrect result with RIGHT JOIN and IS NULL predicate on partitioned indexed table |
| 120084 | 2026-03-17 9:40 | 2026-03-17 11:47 | MySQL Server: Optimizer | Verified (75 days) | S3 | 8.0.45 | Linux | x86 | Incorrect result with string-to-decimal comparison in OUTER JOIN condition |
| 120083 | 2026-03-17 8:59 | 2026-03-17 11:38 | MySQL Server: Optimizer | Verified (75 days) | S2 | 8.0.45 | Linux | x86 | incorrect result when comparing floating constant in OUTER JOIN condition |
| 120075 | 2026-03-16 14:26 | 2026-03-25 12:47 | MySQL Server: Optimizer | Verified (74 days) | S1 | 8.0.45 | Linux (ubuntu 20.04) | x86 | Silent Data Truncation of DOUBLE (DBL_MAX) in Subqueries/Temporary Tables |
| 120058 | 2026-03-14 10:40 | 2026-03-14 14:52 | MySQL Server: Optimizer | Verified (78 days) | S3 | 8.0.45 | Any | Any | UPDATE IGNORE fails to match rows when combining OR-weakened predicates with complex CASE expressions |
| 120057 | 2026-03-14 4:32 | 2026-03-14 14:43 | MySQL Server: Optimizer | Verified (78 days) | S3 | 8.0.45 | Any | Any | Multi-table UPDATE with CTE returns zero rows when weakening a predicate from '=' to '<=' |
| 120056 | 2026-03-14 4:22 | 2026-03-14 14:24 | MySQL Server: Optimizer | Verified (78 days) | S3 | 8.0.45 | Any | Any | UPDATE IGNORE returns empty result after weakening WHERE clause with OR in a JOIN context |
| 120051 | 2026-03-13 9:31 | 2026-03-13 21:16 | MySQL Server: Optimizer | Verified (79 days) | S1 | 8.0.45 | Linux (ubuntu 20.04) | Any | Wrong result for derived-table rewrite of GROUP BY ... HAVING query |
| 120047 | 2026-03-13 5:08 | 2026-03-13 5:57 | MySQL Server: Optimizer | Verified (79 days) | S3 | 9.5.0 | Any | Any | Incorrect empty update result when weakening WHERE clause in UPDATE IGNORE with CROSS JOIN and IN subquery |
| 120037 | 2026-03-12 2:46 | 2026-03-13 11:31 | MySQL Server: Optimizer | Verified (79 days) | S3 | 8.4.8 | Any | Any | Query Results Differ Between Tables with Same Data and Query Due to RENAME Operation |
| 120036 | 2026-03-12 2:09 | 2026-03-13 13:15 | MySQL Server: Optimizer | Verified (79 days) | S3 | 8.0.45 | Any | Any | Different results for semantically equivalent expressions using CASE and MIN(CASE ...) with GROUP BY on a FLOAT column |
| 120034 | 2026-03-11 15:13 | 2026-03-11 21:10 | MySQL Server: Optimizer | Verified (81 days) | S3 | 8.4.8 | Any | Any | Wrong Results with LOG(1, N) <=> NULL: UNIQUE Constraint Causes Incorrect Row Deduplication |
| 120033 | 2026-03-11 15:01 | 2026-03-11 21:02 | MySQL Server: Optimizer | Verified (81 days) | S3 | 8.4.8 | Any | Any | Inconsistent Results with SUBTIME(1, SYSDATE()) in HAVING Clause: UNIQUE Constraint Affects Optimizer Evaluation |
| 120032 | 2026-03-11 14:56 | 2026-03-11 20:56 | MySQL Server: Optimizer | Verified (81 days) | S3 | 8.4.8 | Any | Any | Inconsistent Aggregation Results in Derived Tables: PRIMARY KEY Affects AVG(NOT(...)) Evaluation and Optimizer Execution |
| 120031 | 2026-03-11 14:48 | 2026-03-11 20:46 | MySQL Server: Optimizer | Verified (81 days) | S3 | 8.4.8 | Any | Any | Inconsistent INTERSECT Results in Derived Tables: Impact of PRIMARY KEY on JSON_OBJECTAGG and LEAST Operators |
| 120030 | 2026-03-11 14:44 | 2026-03-11 20:31 | MySQL Server: Optimizer | Verified (81 days) | S3 | 8.4.8 | Any | Any | Query Results Differ Due to Primary Key and INTERSECT Operation |
| 120029 | 2026-03-11 14:42 | 2026-03-11 20:19 | MySQL Server: Optimizer | Verified (81 days) | S3 | 8.4.8 | Any | Any | Query Results Differ Due to Primary Key Column - Issue with MIN, MAX, and Time-Related Functions |
| 120028 | 2026-03-11 14:38 | 2026-03-11 19:59 | MySQL Server: Optimizer | Verified (81 days) | S3 | 8.4.8 | Any | Any | Query Results Differ Due to Primary Key Column and TRUNCATE Function Behavior |
| 120027 | 2026-03-11 14:34 | 2026-03-11 19:48 | MySQL Server: Optimizer | Verified (81 days) | S3 | 8.4.8 | Any | Any | Query Results Differ Due to Presence of Primary Key - Issue with MIN and DATE_ADD Functions |
| 120022 | 2026-03-11 2:22 | 2026-03-11 7:10 | MySQL Server: Optimizer | Verified (81 days) | S3 | MySQL 8.0.28 | Any | Any | CAST(AVG()) returns a different result than CAST(SUM()/COUNT()) on DECIMAL values |
| 120019 | 2026-03-10 12:29 | 2026-03-10 14:40 | MySQL Server: Optimizer | Verified (82 days) | S2 | 8.0.41 | Any | Any | query result change after removing partitioning |
| 120011 | 2026-03-09 10:29 | 2026-03-09 11:16 | MySQL Server: Optimizer | Verified (83 days) | S1 | 8.0.44 | Any | Any | The normal query generated a non-optimal query plan with index. |
| 120005 | 2026-03-08 0:14 | 2026-03-10 8:04 | MySQL Server: Optimizer | Verified (82 days) | S2 | 8.4.7 | Any | Any | Wrong results with subquery with semijoin=on and antijoin optimization |
| 120004 | 2026-03-07 19:38 | 2026-03-09 9:48 | MySQL Server: Optimizer | Verified (83 days) | S2 | 8.0.31 | Any | Any | IndexSkipScanIterator Assertion Failure |
| 120003 | 2026-03-07 12:14 | 2026-03-09 9:41 | MySQL Server: Optimizer | Verified (83 days) | S3 | 8.0.45 | Any | Any | column name unexpectedly change because of '1' as a column |
| 119991 | 2026-03-06 5:56 | 2026-03-06 11:27 | MySQL Server: Optimizer | Verified (86 days) | S2 | 8.0.45 | Linux | x86 | Incorrect result with LEFT/RIGHT JOIN when comparing boolean expression with = 0 in presence of functional index |
| 119977 | 2026-03-03 13:44 | 2026-03-03 20:55 | MySQL Server: Optimizer | Verified (89 days) | S3 | 8.0.36 | Any (windows 11) | Any | NULL > ALL(subquery) produces NULL but IS NULL / IS UNKNOWN both return FALSE |
| 119973 | 2026-03-02 21:01 | 2026-03-03 8:45 | MySQL Server: Optimizer | Verified (89 days) | S1 | 8.0.45 | Any | Any | Inconsistent results depending on whether the column has a PRIMARY KEY index |
| 119972 | 2026-03-02 19:47 | 2026-03-03 9:47 | MySQL Server: Optimizer | Verified (89 days) | S1 | 8.0.45 | Any | Any | Incorrect Result from IN Subquery with UNIQUE Index |
| 119963 | 2026-03-02 9:08 | 2026-03-02 13:43 | MySQL Server: Optimizer | Verified (90 days) | S3 | 8.0.45 | Any | Any | Inconsistent Results When Comparing Identical Aggregate Calculations Between Main Query and Correlated Subquery |
| 119959 | 2026-03-01 14:50 | 2026-03-02 13:16 | MySQL Server: Optimizer | Verified (90 days) | S3 | 8.0.45 | Linux (ubuntu 20.04) | x86 | Inconsistent results between direct query and derived table query involving NULLIF and IS NOT UNKNOWN |
| 119958 | 2026-02-28 13:09 | 2026-03-02 13:02 | MySQL Server: Optimizer | Verified (90 days) | S1 | 8.0.45 | Any | Any | EXISTS subquery result behaves inconsistently based on source table |
| 119955 | 2026-02-27 5:03 | 2026-03-02 12:46 | MySQL Server: Optimizer | Verified (90 days) | S3 | 8.0.43 (MySQL Community Server - GPL) | Any (Docker container) | Any (x86_64) | Semantically equivalent scalar expressions yield different result sets in WHERE clause involving RPAD() |
| 119954 | 2026-02-26 21:13 | 2026-02-28 17:08 | MySQL Server: Compiling | Open (92 days) | S3 | 8.4.8 | Ubuntu (Ubuntu 24.04.3 LTS) | x86 (n.a.) | libaio1.so loading shared library fails in binary tarball b/c it is renamed to libaio1t64 |
| 119944 | 2026-02-25 22:14 | 2026-02-26 13:13 | MySQL Server: Optimizer | Verified (94 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) |
| 119937 | 2026-02-25 4:54 | 2026-02-25 9:25 | MySQL Server: Optimizer | Verified (95 days) | S3 | 8.0 | Any | Any | Result is not correct when using pow function with group by |
| 119927 | 2026-02-20 10:28 | 2026-02-25 8:56 | MySQL Server: Optimizer | Verified (95 days) | S2 | 8.0.45 | Linux | Any | Inconsistent results between direct query and derived table with BIGINT column and FLOAT predicate (IN clause) |
| 119918 | 2026-02-17 8:12 | 2026-02-17 8:31 | MySQL Server: Optimizer | Verified (103 days) | S2 | 9.6.0 | Any | Any | Tree based explain format doesn't work well with MySQL Client or MySQL Shell |
| 119912 | 2026-02-15 4:33 | 2026-02-15 12:09 | MySQL Server: Optimizer | Verified (105 days) | S2 | 8.0.45 | Linux | Any | JOIN query returns different results depending on index visibility |
| 119909 | 2026-02-12 21:31 | 2026-02-12 21:31 | MySQL Server: Optimizer | Open | S2 | 9.5.0 | Any | Any | Wrong result due to unsafe Item_max optimization triggering on homogeneous subqueries but not heterogeneous ones |
| 119908 | 2026-02-12 12:49 | 2026-02-13 7:26 | MySQL Server: Optimizer | Verified (107 days) | S3 | 8.0.34 | Any | Any | GROUP_CONCAT returns corrupted characters when column charset is utf8mb4 and connection charset is gbk |
| 119834 | 2026-02-02 13:44 | 2026-02-03 13:20 | MySQL Server: Optimizer | Verified (117 days) | S3 | 8.0.44 | Any | Any | Inconsistent query results when selecting different columns with the same JOIN condition involving LIKE (EXISTS(subquery |
| 119832 | 2026-02-02 9:12 | 2026-02-03 12:21 | MySQL Server: Optimizer | Verified (117 days) | S3 | 8.0.44 | Any | Any | drop index can lead to different results |
| 119831 | 2026-02-02 8:32 | 2026-02-03 12:56 | MySQL Server: Optimizer | Verified (117 days) | S3 | 8.0.44 | Any | Any | drop index can lead to different results |
| 119825 | 2026-02-01 12:02 | 2026-02-02 3:51 | MySQL Server: Optimizer | Verified (118 days) | S2 | 8.0.45, 8.4.8, 9.6 | Any | Any | Inconsistent results between INNER JOIN and STRAIGHT_JOIN when comparing DOUBLE constant with INT UNIQUE column |
| 119824 | 2026-02-01 11:59 | 2026-02-02 3:57 | MySQL Server: Optimizer | Verified (118 days) | S3 | 8.0.44 | Any | Any | drop index can lead to incorrect results |
| 119823 | 2026-02-01 11:42 | 2026-02-02 3:55 | MySQL Server: Optimizer | Verified (118 days) | S3 | 8.0.44 | Any | Any | drop index can lead to different results |
| 119822 | 2026-01-31 17:35 | 2026-01-31 22:04 | MySQL Server: Optimizer | Verified (120 days) | S2 | 8.0.45 | Any | Any | MySQL and TiDB return different results |
| 119819 | 2026-01-31 10:29 | 2026-01-31 21:41 | MySQL Server: Optimizer | Verified (120 days) | S3 | 8.0.44 | Any | Any | drop index can lead to different results |
| 119818 | 2026-01-31 8:53 | 2026-01-31 21:34 | MySQL Server: Optimizer | Verified (120 days) | S3 | 8.0.44 | Any | Any | A different results occured after inserting a NULL record |
| 119816 | 2026-01-31 7:56 | 2026-01-31 21:19 | MySQL Server: Optimizer | Verified (120 days) | S3 | 8.0.44 | Any | Any | Create index can lead to incorrect results |
| 119815 | 2026-01-31 7:03 | 2026-01-31 21:11 | MySQL Server: Optimizer | Verified (120 days) | S3 | 8.0.44 | Any | Any | An incorrect results after inserting a record |
| 119814 | 2026-01-31 4:11 | 2026-01-31 20:59 | MySQL Server: Optimizer | Verified (120 days) | S3 | 8.0.44 | Any | Any | drop index can lead to incorrect results |
| 119808 | 2026-01-29 14:44 | 2026-04-20 11:52 | MySQL Server: DML | Open (41 days) | S2 | Any | Any | Error 3569 with HIGH_PRIORITY + VIEW + GROUP BY + FOR UPDATE | |
| 119805 | 2026-01-29 3:21 | 2026-01-29 4:15 | MySQL Server: DML | Verified (122 days) | S2 | 8.0.45 | Any | Any | create_tmp_field assert fail |
| 119802 | 2026-01-28 13:49 | 2026-01-28 15:52 | MySQL Server: Optimizer | Verified (123 days) | S2 | 8.0.42+ | Any | Any | Assertion 'is_nullable()' failed in Item_typecast_signed::val_int() |
| 119800 | 2026-01-28 8:53 | 2026-01-28 11:54 | MySQL Server: Compiling | Open (123 days) | S1 | 8.4 | Any | Any | An error occurred in ssl.cmake reading version information from opensslv.h, causing HAVE_TLSv13 to fail to compile. |
| 119799 | 2026-01-27 21:40 | 2026-01-28 9:08 | MySQL Server: Optimizer | Verified (123 days) | S3 | 8.0.44 | MacOS | ARM | OR condition incorrectly filters out NULL values in derived table with UNION |
| 119793 | 2026-01-27 10:32 | 2026-02-04 16:32 | MySQL Server: Prepared statements | Verified (116 days) | S1 | 9.5.0 | Any | Any | Incorrect result of prepared SELECT when running with JDBC |
| 119790 | 2026-01-27 10:14 | 2026-01-27 12:07 | MySQL Server: Optimizer | Verified (124 days) | S1 | 8.0.44 | Any | Any | Unexpected result of expression IN NULL |
| 119776 | 2026-01-26 9:31 | 2026-01-26 13:51 | MySQL Server: Optimizer | Verified (125 days) | S3 | 8.0.41 | Any | Any | Semantically identical SQLs yield different result sets. |
| 119767 | 2026-01-24 12:57 | 2026-01-24 12:57 | MySQL Server: Compiling | Open | S2 | 9.6.0 | FreeBSD (15) | x86 | MySQL fails to build on FreeBSD |
| 119752 | 2026-01-22 15:08 | 2026-01-22 21:36 | MySQL Server: Optimizer | Verified (129 days) | S3 | 8.0.44 | Any | Any | after changing MINUTE(subq.c1) to MINUTE(subq.c1 + INTERVAL '60' MINUTE),the result become empty. |
| 119741 | 2026-01-22 7:00 | 2026-01-22 8:35 | MySQL Server: Optimizer | Verified (129 days) | S1 | 8.0.44 | Any | Any | internal_tmp_mem_storage_engine = MEMORY setting makes the DISTINCTROW returns incorrect result on 0 and -0 |
| 119727 | 2026-01-20 10:11 | 2026-01-27 18:37 | MySQL Server: Data Types | Verified (131 days) | S3 | 8.0.44 | Any | Any | wrong result for 'value between a and null' for certain temporal types |
| 119724 | 2026-01-20 5:55 | 2026-01-20 8:08 | MySQL Server: Optimizer | Verified (131 days) | S3 | 8.0.44 | Any | Any | after changing asin function in group clause,column's value unexpectedly change |
| 119716 | 2026-01-19 1:36 | 2026-01-19 9:16 | MySQL Server: Optimizer | Verified (132 days) | S1 | 8.0.44 | Any | Any | Suboptimal query plan generated by normal query compare to prepared statement |
| 119714 | 2026-01-18 12:26 | 2026-01-19 9:01 | MySQL Server: Optimizer | Verified (132 days) | S3 | 8.0.44 | Any | Any | after changing ASIN(hpg31.c1) in group clause,the col_1’s value unexpectedly change. |
| 119713 | 2026-01-18 11:19 | 2026-01-20 9:37 | MySQL Server: Optimizer | Verified (131 days) | S3 | 8.0.39, 8.0.44, 8.4.6 | Any | Any | MySQL has hard time using the right indexes |
| 119708 | 2026-01-16 14:58 | 2026-02-08 12:32 | MySQL Server: Optimizer | Verified (112 days) | S2 | 8.0.44 | Linux | Any | INNER JOIN and STRAIGHT_JOIN produce different results with FLOAT UNIQUE column on MEMORY table |
| 119706 | 2026-01-16 10:46 | 2026-03-17 8:21 | MySQL Server: Optimizer | Open (75 days) | S2 | 8.0.44, 9.5.0 | Any | Any | Incorrect Results from ALL/ANY Subquery MIN/MAX Optimization with Type Mismatch |
| 119701 | 2026-01-16 7:18 | 2026-01-16 9:45 | MySQL Server: Optimizer | Verified (135 days) | S3 | 8.0.44 | Any | Any | after changing FLOOR function,col_1’s value unexpectedly change |
| 119698 | 2026-01-16 7:08 | 2026-01-16 9:16 | MySQL Server: Optimizer | Verified (135 days) | S3 | 8.0. | Any | Any | rows become less unexpectedly caused by on clause |
| 119696 | 2026-01-16 7:03 | 2026-01-16 8:58 | MySQL Server: Optimizer | Verified (135 days) | S3 | 8.0.44 | Any | Any | float value Precision loss caused by removing distinct |
| 119695 | 2026-01-16 6:59 | 2026-01-16 8:48 | MySQL Server: Optimizer | Verified (135 days) | S3 | 8.0.44 | Any | Any | The appearance of rows that should not exist caused by on clause |
| 119694 | 2026-01-16 6:56 | 2026-01-16 8:39 | MySQL Server: Optimizer | Verified (135 days) | S3 | 8.0.44 | Any | Any | rows unexpectedly become less after changing INNER to LEFT |
| 119693 | 2026-01-16 6:39 | 2026-01-16 8:28 | MySQL Server: Optimizer | Verified (135 days) | S3 | 8.0.44 | Any | Any | column value change after changing INNER to LEFT |
| 119692 | 2026-01-16 5:23 | 2026-01-16 8:09 | MySQL Server: Optimizer | Verified (135 days) | S1 | 8.0.44 | Any | Any | The normal query generated a non-optimal query plan. |
| 119687 | 2026-01-15 10:23 | 2026-01-15 13:18 | MySQL Server: Optimizer | Verified (136 days) | S1 | 8.0.44 | Any | Any | Inconsistent behaviour between normal and prepared INSERT |
| 119686 | 2026-01-15 8:37 | 2026-01-15 13:11 | MySQL Server: Optimizer | Verified (136 days) | S2 | 8.0.44 | Linux | x86 | Incorrect result when joined table has PRIMARY KEY and WHERE predicate involves CASE |
| 119683 | 2026-01-14 15:35 | 2026-01-15 12:57 | MySQL Server: Optimizer | Verified (136 days) | S1 | 8.0.44 | Linux | x86 | Different results for INNER JOIN and STRAIGHT_JOIN with GREATEST() IN predicate |
| 119681 | 2026-01-14 14:19 | 2026-01-15 12:47 | MySQL Server: Optimizer | Verified (136 days) | S3 | 9.5.0 | Any | Any | Floating-point precision loss occurs when changing avg(x) to -avg(-x) |
| 119680 | 2026-01-14 13:51 | 2026-01-15 12:25 | MySQL Server: Optimizer | Verified (136 days) | S3 | 8.0.44 | Any | Any | after changing AVG(cte.col_2) to -AVG(-cte.col_2) ,rows become less |
| 119679 | 2026-01-14 13:40 | 2026-01-15 11:25 | MySQL Server: Optimizer | Verified (136 days) | S3 | 8.0.45 | Any | Any | after changing SUM(t3.c9) to -SUM(-t3.c9),the rows become less |
| 119670 | 2026-01-13 13:46 | 2026-01-13 14:51 | MySQL Server: Optimizer | Verified (138 days) | S1 | 8.0.44 | Any | Any | Incorrect result caused by index |
| 119669 | 2026-01-13 13:27 | 2026-01-13 14:53 | MySQL Server: Optimizer | Verified (138 days) | S1 | 8.0.44 | Any | Any | Inconsistent behaviour between normal query and prepared statement |
| 119666 | 2026-01-13 7:37 | 2026-01-13 8:16 | MySQL Server: Optimizer | Verified (138 days) | S3 | 8.0.41 | Any | Any | YEAR column IN (1,2) does not match expected conversion behavior |
| 119663 | 2026-01-13 4:24 | 2026-01-13 7:46 | MySQL Server: Optimizer | Verified (138 days) | S3 | 9.3.0 | Ubuntu | Any | Query reports error when turn on optimizer_switch |
| 119638 | 2026-01-07 8:40 | 2026-01-07 9:59 | MySQL Server: Optimizer | Verified (144 days) | S3 | 8.0.42 | Any | Any | Incorrect Condition Evaluation for BETWEEN with NULL Upper Bound |
| 119636 | 2026-01-07 7:55 | 2026-01-07 9:20 | MySQL Server: Optimizer | Verified (144 days) | S3 | 8.0 | Any | Any | Incorrect Condition Evaluation for float unsigned zerofill Columns |
| 119635 | 2026-01-07 7:27 | 2026-01-07 11:07 | MySQL Server: Optimizer | Verified (144 days) | S3 | 8.0.42+ | Any | Any | Returns incorrect query results when using the between keyword |
| 119621 | 2026-01-05 11:11 | 2026-02-24 12:06 | MySQL Server: JSON | Verified (96 days) | S2 | 8.0.43 / 8.4.7 | Any | Any | query on partitioned table report "the JSON binary value contains invalid data" |
| 119619 | 2026-01-04 14:07 | 2026-01-04 21:17 | MySQL Server: Optimizer | Verified (147 days) | S1 | 8.0 | Any | Any | Incorrect results for REPLACE function |
| 119605 | 2025-12-29 9:37 | 2025-12-29 13:00 | MySQL Server: Optimizer | Verified (153 days) | S3 | 8.0.27 | Any | Any | GROUP BY brings unnecessary order columns |
| 119603 | 2025-12-29 1:19 | 2026-01-04 20:40 | MySQL Server: Optimizer | Verified (147 days) | S2 | 8.0 | Any | Any | TRUE >= ALL(...) returns incorrect result (1) when comparing against a NOT NULL column |
| 119601 | 2025-12-28 11:55 | 2026-02-08 13:32 | MySQL Server: Optimizer | Verified (112 days) | S2 | 8.0.41 | CentOS | Any (x86) | Crash for show processlist when use cursor |
| 119599 | 2025-12-27 2:30 | 2025-12-29 4:51 | MySQL Server: Optimizer | Verified (153 days) | S3 | 8.0.41 | Any | Any | Under the same SQL, the results of hash join and nested loop join are inconsistent |
| 119597 | 2025-12-26 2:37 | 2025-12-26 17:57 | MySQL Server: Optimizer | Verified (156 days) | S1 | 8.0.44 | Any | Any | WHERE ... IN ... incorrectly returns rows |
| 119596 | 2025-12-26 2:01 | 2025-12-29 4:55 | MySQL Server: Optimizer | Verified (153 days) | S3 | 9.2,9.4 | Any | Any | Inconsistent results use IFNULL with different query plan |
| 119594 | 2025-12-24 14:03 | 2025-12-26 6:21 | MySQL Server: Optimizer | Verified (156 days) | S1 | 9.5.0 | Any | Any | INTERSECT (SELECT NULL) incorrectly returns non-NULL rows when column is PRIMARY KEY |
| 119591 | 2025-12-24 7:27 | 2025-12-26 17:48 | MySQL Server: Data Types | Verified (156 days) | S1 | 8.0.44 | Any | Any | Incorrect result type for NULLIF(DOUBLE,BIGINT) function |
| 119590 | 2025-12-24 6:41 | 2025-12-26 6:22 | MySQL Server: Optimizer | Verified (156 days) | S1 | 9.5.0 | Any | Any | EXCEPT (SELECT NULL) returns incorrect result (missing row) on DECIMAL primary key column |
| 119588 | 2025-12-24 3:03 | 2025-12-26 17:23 | MySQL Server: Optimizer | Verified (156 days) | S1 | 8.0.44 | Any | Any | Incorrect result in JOIN with IN subquery |
| 119586 | 2025-12-23 9:09 | 2025-12-26 16:50 | MySQL Server: Data Types | Verified (156 days) | S1 | 8.4.7 | Any | Any | Inconsistent results for date conversion |
| 119584 | 2025-12-22 16:09 | 2025-12-22 19:42 | MySQL Server: Optimizer | Verified (160 days) | S3 | 8.0.44 | Any | Any | The HAVING clause cannot recognize alias columns defined by Boolean expressions in derived tables |
| 119583 | 2025-12-22 7:34 | 2025-12-22 19:35 | MySQL Server: Optimizer | Verified (160 days) | S3 | 8.0.44 | Any | Any | Create index can lead to incorrect results |
| 119582 | 2025-12-22 6:49 | 2025-12-22 19:27 | MySQL Server: Optimizer | Verified (160 days) | S2 | 8.0.44 | Any | Any | Inconsistency functional dependency in ONLY_FULL_GROUP_BY mode between derived tables and physical tables |
| 119581 | 2025-12-20 14:54 | 2025-12-22 19:17 | MySQL Server: Optimizer | Verified (160 days) | S3 | 8.0.33 | Ubuntu (22.04) | Any | FLOOR function shows inconsistent overflow handling |
| 119565 | 2025-12-17 1:06 | 2026-02-05 15:32 | MySQL Server: Optimizer | Verified (115 days) | S3 | 8.0.41 | Any | Any | Temporary table causes incorrect conversion from TIME to JSON type |
| 119541 | 2025-12-11 12:32 | 2025-12-12 8:19 | MySQL Server: Optimizer | Verified (170 days) | S2 | 8.0, 8.4, 9.5 | Any | Any | Performance regression due to record buffer in index range scan |
| 119538 | 2025-12-11 1:54 | 2025-12-12 5:12 | MySQL Server: Optimizer | Verified (170 days) | S3 | 8.0.41 | Any | Any | different values set for sql_buffer_result and materialization lead to different query results. |
| 119531 | 2025-12-09 14:40 | 2025-12-15 14:58 | MySQL Server: Optimizer | Verified (167 days) | S5 | 8.4.6 | Any | Any | Optimizer should use a short-circuit DESC scan for SELECT MAX(PK) WHERE ... |
| 119530 | 2025-12-09 12:38 | 2025-12-11 9:31 | MySQL Server: Optimizer | Verified (171 days) | S1 | 8.4.7 | Any | Any | Incorrect results for NULLIF functions |
| 119528 | 2025-12-09 9:49 | 2025-12-10 12:38 | MySQL Server: Optimizer | Verified (172 days) | S2 | 8.0 | Any | Any | hash join result incorrect |
| 119520 | 2025-12-06 17:55 | 2025-12-08 3:51 | MySQL Server: Optimizer | Verified (174 days) | S2 | 9.5.0 | Ubuntu (22.04) | Any | Inconsistent NULL and Negative Zero Handling in EXISTS Subquery with HAVING Clause |
| 119491 | 2025-12-02 8:21 | 2025-12-08 21:10 | MySQL Server: Optimizer | Verified (174 days) | S1 | 8.4.7 | Any | Any | Incorrect results for make_set operation against longtext column |
| 119488 | 2025-12-01 14:52 | 2025-12-02 4:37 | MySQL Server: Optimizer | Verified (180 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 |
| 119487 | 2025-12-01 14:45 | 2026-02-05 19:41 | MySQL Server: Optimizer | Verified (115 days) | S2 | 8.0.45 | Ubuntu (22.04) | Any | JOIN, STRAIGHT_JOON Return Different Results |
| 119485 | 2025-12-01 14:10 | 2025-12-02 5:32 | MySQL Server: Optimizer | Verified (180 days) | S2 | 9.5.0,8.0.41 | Any | Any | Wrong result with left joins |
| 119474 | 2025-11-29 9:29 | 2025-12-01 4:16 | MySQL Server: Optimizer | Verified (181 days) | S2 | 8.0.41 | Any | Any | Result error caused by the subquery_to_derived optimizer switch |
| 119470 | 2025-11-27 14:30 | 2025-11-28 13:06 | MySQL Server: Optimizer | Verified (184 days) | S1 | 8.0.44+ | Any | Any | sql injection |
| 119463 | 2025-11-26 6:23 | 2026-02-05 20:07 | MySQL Server: Charsets | Verified (115 days) | S2 | 9.5.0 | Any | Any | some charactor may be truncated use utf8mb4_general_ci collation_connection |
| 119456 | 2025-11-25 6:52 | 2025-11-28 14:55 | MySQL Server: Optimizer | Verified (184 days) | S3 | 8.0.44, 8.4.7, 9.5 | Any | Any | Query block name uses mixed decimal/hexadecimal in optimizer trace and hint |
| 119454 | 2025-11-24 16:04 | 2025-11-27 5:11 | MySQL Server: Optimizer | Verified (185 days) | S2 | 9.4.0 | Any | Any | Hash join has wrong result when the join equality involves FLOAT or DECIMAL column |
| 119453 | 2025-11-24 14:12 | 2025-12-07 22:36 | MySQL Server: Optimizer | Verified (175 days) | S2 | 8.0 | Any | Any | DEFAULT(column) returns wrong result when column is to the right of left join |
| 119447 | 2025-11-23 8:34 | 2025-11-27 5:04 | MySQL Server: Optimizer | Verified (185 days) | S5 | 8.0.41 | CentOS | x86 | Prepare Statement execute much slower than normal select query |
| 119446 | 2025-11-23 6:46 | 2025-11-27 4:57 | MySQL Server: Optimizer | Verified (185 days) | S3 | 9.4.0 | Any | Any | rows become more after changing COUNT to COUNT(DISTINCT) |
| 119433 | 2025-11-20 9:30 | 2025-12-07 21:58 | MySQL Server: Data Types | Verified (175 days) | S1 | 8.4.6 | Any | Any | Inconsistent date conversion behaviors between text and integer |
| 119432 | 2025-11-20 8:47 | 2025-12-07 21:44 | MySQL Server: Data Types | Verified (175 days) | S1 | 8.0 | Any | Any | Inconsistent time conversion behaviors between text and integer |
| 119416 | 2025-11-18 6:11 | 2025-12-07 21:23 | MySQL Server: Optimizer | Verified (175 days) | S3 | 9.4.0 | Any | Any | Incorrect in Subquery on MEMORY Engine |
| 119415 | 2025-11-18 6:07 | 2025-12-07 21:17 | MySQL Server: Optimizer | Verified (175 days) | S3 | 9.4.0 | Any | Any | Incorrect IN Subquery on ARCHIVE Engine |
| 119413 | 2025-11-17 23:52 | 2025-12-07 21:06 | MySQL Server: Optimizer | Verified (175 days) | S3 | mysql Ver 9.4. | Any | Any | Intersection order |
| 119403 | 2025-11-15 9:38 | 2025-12-07 20:55 | MySQL Server: Optimizer | Verified (175 days) | S3 | 9.4.0 | Any | Any | INTERSECT operation incorrectly gets rows with NULL and non-NULL combination |
| 119402 | 2025-11-15 8:39 | 2025-12-07 20:50 | MySQL Server: Optimizer | Verified (175 days) | S3 | 9.4.0 | Any | Any | EXCEPT operation incorrectly removes rows with NULL and non-NULL combination when subtracting sets with NULL values |
| 119400 | 2025-11-15 7:20 | 2025-12-07 20:08 | MySQL Server: Optimizer | Verified (175 days) | S3 | 8.0 | Any | Any | rows become less after changing join clause |
| 119399 | 2025-11-15 7:00 | 2025-12-07 19:31 | MySQL Server: Optimizer | Verified (175 days) | S3 | 9.4.0 | Any | Any | Column name change after adding DISTINCT |
| 119398 | 2025-11-15 6:56 | 2025-12-07 19:21 | MySQL Server: Optimizer | Verified (175 days) | S3 | 9.4.0 | Any | Any | rows become less after removing Except clause |
| 119391 | 2025-11-14 7:19 | 2025-11-27 7:19 | MySQL Server: Compiling | Open | S3 | 9.5.0 | Linux (mysqld --no-defaults --help failed) | x86 | /mysql-9.5.0/cmake/info_bin.cmake:37 (CREATE_INFO_BIN) |
| 119386 | 2025-11-13 11:44 | 2026-01-15 12:35 | MySQL Server: Optimizer | Verified (136 days) | S1 | 9.4.0 | Any | Any | unexpected error "Can't write; duplicate key in table '/tmp/#sql1_372_1'" |
| 119385 | 2025-11-13 9:41 | 2025-12-06 22:51 | MySQL Server: Optimizer | Verified (176 days) | S3 | 8.0.41 | Any | Any | After replacing the expressions inside BETWEEN ... AND with constants, the results become inconsistent. |
| 119381 | 2025-11-13 8:14 | 2026-01-13 19:17 | MySQL Server: DML | Verified (138 days) | S2 | 8.0.43, 9.4.0 | Any | Any | Contribution by Tencent: Duplicate auto-increment values happened with partitioned tables and uk conflict |
| 119370 | 2025-11-12 10:07 | 2025-12-06 22:40 | MySQL Server: Optimizer | Verified (176 days) | S3 | 9.4.0 8.4.6 | Any | Any | FLOAT Value Returned by CASE Statement Evaluates Incorrectly in Bitwise Operation |
| 119365 | 2025-11-12 3:14 | 2025-12-06 22:25 | MySQL Server: Optimizer | Verified (176 days) | S3 | 9.4.0 8.4.6 | Any | Any | Incorrect NOT IN Evaluation for NULL on Indexed TEXT Column |
| 119364 | 2025-11-12 3:01 | 2025-12-06 22:14 | MySQL Server: Optimizer | Verified (176 days) | S3 | 9.4.0 8.4.6 | Any | Any | Incorrect Evaluation of = ANY Subquery with NULL on Indexed DECIMAL Column |
| 119363 | 2025-11-12 2:52 | 2025-11-12 3:10 | MySQL Server: Optimizer | Verified (200 days) | S3 | 9.4.0 8.4.6 | Any | Any | Complex WHERE Expression on Indexed FLOAT Column Evaluates Incorrectly |
| 119360 | 2025-11-11 8:42 | 2026-02-08 14:00 | MySQL Server: Optimizer | Verified (112 days) | S3 | 8.0.41 | Any | Any | Result inconsistency due to sorting in temporary tables |
| 119356 | 2025-11-10 16:20 | 2025-12-06 22:04 | MySQL Server: Charsets | Verified (176 days) | S3 | Any | Any | Contribution: Fix NUL characters in FORMAT() output | |
| 119355 | 2025-11-10 16:15 | 2025-12-06 22:02 | MySQL Server: Optimizer | Verified (176 days) | S3 | 9.4.0 8.4.6 | Any | Any | BETWEEN ... AND NULL evaluates incorrectly with bitwise shift |
| 119354 | 2025-11-10 15:51 | 2025-12-06 21:52 | MySQL Server: Optimizer | Verified (176 days) | S3 | 9.4.0 8.4.6 | Any | Any | IN subquery evaluates incorrectly when using IFNULL and CAST AS DATETIME |
| 119353 | 2025-11-10 14:30 | 2026-02-05 20:53 | MySQL Server: Optimizer | Verified (115 days) | S3 | 9.4.0 | Any | Any | Column Value change after removing DISTINCT in query |
| 119352 | 2025-11-10 13:11 | 2026-02-05 21:02 | MySQL Server: Optimizer | Verified (115 days) | S3 | 8.0.45 | Any | Any | row number become less after changing where clause |
| 119351 | 2025-11-10 13:00 | 2026-02-05 21:15 | MySQL Server: Optimizer | Verified (115 days) | S3 | 8.0.45 | Any | Any | Index caused different result |
| 119350 | 2025-11-10 12:14 | 2025-11-20 13:15 | MySQL Server: Optimizer | Verified (192 days) | S3 | 8.0 | Any | Any | Column name change after changing having clause |
| 119349 | 2025-11-10 12:06 | 2025-11-20 13:05 | MySQL Server: Optimizer | Verified (192 days) | S3 | 9.4.0 | Any | Any | Incorrect String Comparison with MyISAM BIT Column in IN Subquery |
| 119348 | 2025-11-10 11:01 | 2025-11-20 12:58 | MySQL Server: Optimizer | Verified (192 days) | S3 | 8.0 | Any | Any | Incorrect row number after changing having clause |
| 119347 | 2025-11-10 10:43 | 2025-11-20 12:48 | MySQL Server: Optimizer | Verified (192 days) | S3 | 8.0 | Any | Any | IN predicate incorrectly evaluates RADIANS() and TINYINT with key |
| 119346 | 2025-11-10 9:43 | 2025-11-20 12:40 | MySQL Server: Optimizer | Verified (192 days) | S3 | 8.0 | Any | Any | CASE expression evaluates incorrectly |
| 119345 | 2025-11-10 9:21 | 2025-11-20 11:33 | MySQL Server: Optimizer | Verified (192 days) | S3 | 8.0 | Any | Any | Presence of UNIQUE index on INT column causes inconsistent results for IF with ANY subquery |
| 119344 | 2025-11-10 8:47 | 2025-11-12 3:04 | MySQL Server: Optimizer | Verified (200 days) | S3 | 9.4.0 | Any | Any | Floating-point precision loss happen after changing UNION to UNION ALL |
| 119342 | 2025-11-10 8:26 | 2025-11-11 8:10 | MySQL Server: Optimizer | Verified (201 days) | S3 | 9.4.0 | Any | Any | Bits value change after changing UNION to UNION ALL |
| 119341 | 2025-11-10 8:24 | 2025-11-11 7:56 | MySQL Server: Optimizer | Verified (201 days) | S3 | 9.4.0 | Any | Any | ALL subquery evaluates incorrectly in SELECT list when comparing against a BIT column |
| 119339 | 2025-11-08 17:27 | 2025-11-11 7:31 | MySQL Server: Optimizer | Verified (201 days) | S3 | 8.0.41 | Any | Any | The results are different after extracting the value of the COALESCE function |
| 119329 | 2025-11-07 8:13 | 2025-11-11 14:02 | MySQL Server: Optimizer | Verified (205 days) | S3 | 8.0.44 | Any | Any | Column name unexpectedly change after changing COUNT to COUNT(DISTINCT) |
| 119327 | 2025-11-07 7:52 | 2026-02-05 21:26 | MySQL Server: Optimizer | Verified (115 days) | S3 | 8.0.45 | Any | Any | after adding an index ,the result return different |
| 119326 | 2025-11-07 7:40 | 2025-11-07 9:07 | MySQL Server: Optimizer | Verified (205 days) | S3 | 8.0.41 | Any | Any | Using the COALESCE function, two opposite conditions return the same result. |
| 119323 | 2025-11-07 5:59 | 2025-11-07 7:26 | MySQL Server: Optimizer | Verified (205 days) | S3 | 9.4.0 | Any | Any | row number become less after changing COUNT(DISTINCT) to COUNT |
| 119322 | 2025-11-07 4:58 | 2025-11-07 7:29 | MySQL Server: Optimizer | Verified (205 days) | S3 | 9.4.0 | Any | Any | Unexpected None after adding a window column |
| 119321 | 2025-11-07 4:35 | 2025-11-07 7:37 | MySQL Server: Optimizer | Verified (205 days) | S3 | 9.4.0 | Any | Any | Unexpected None after changing SUM to SUM (x*2) |
| 119313 | 2025-11-06 3:03 | 2025-12-06 21:22 | MySQL Server: Optimizer | Verified (176 days) | S3 | 8.0.41 | Any | Any | BETWEEN clause returns incorrect results when comparing numeric literal with DATETIME columns |
| 119306 | 2025-11-05 7:02 | 2025-11-06 5:34 | MySQL Server: Optimizer | Verified (206 days) | S3 | 8.0, 9.5 | Any | Any | The EXPLAIN plan may be inconsistent with the actual execution. |
| 119305 | 2025-11-05 4:02 | 2025-12-16 13:55 | MySQL Server: Optimizer | Verified (166 days) | S3 | 8.0.41 | Linux | x86 | The query results of enabling and disabling materialization are inconsistent. |
| 119303 | 2025-11-05 1:49 | 2025-11-05 5:00 | MySQL Server: DML | Verified (207 days) | S3 | 8.0.41 | Any | Any | The query is normal without using the histogram, but an error occurs when using the histogram |
| 119287 | 2025-11-01 10:08 | 2025-11-04 21:01 | MySQL Server: Optimizer | Verified (208 days) | S3 | 8.0.41 | Any | Any | Decimal Precision Mismatch in UNION Query with CONCAT Function |
| 119262 | 2025-10-29 9:01 | 2025-11-04 23:01 | MySQL Server: Optimizer | Verified (208 days) | S3 | 8.0.44,8.4.6,9.4.0 | Any | Any | Incorrect result on comparison between a float expression and an indexed SMALLINT column. |
| 119246 | 2025-10-27 15:02 | 2026-04-13 14:33 | MySQL Server: Compiling | Open (48 days) | S3 | 8.4.8, 9.7.0-er2 | MacOS (26.0.1) | ARM | 9.7.0-er2 compilation error with LLVM 21 |
| 119242 | 2025-10-27 12:13 | 2025-10-27 12:35 | MySQL Server: Compiling | Open (216 days) | S3 | 8.4.7 | MacOS (26.0.1) | ARM | 8.4.7 fails to build with clang 21 |
| 119239 | 2025-10-27 7:53 | 2026-01-23 10:19 | MySQL Server: Compiling | Open (128 days) | S3 | 8.0.45, 8.4.8 | MacOS (26.0.1) | ARM | Compilation error with clang 21 |
| 119238 | 2025-10-27 7:31 | 2026-01-23 7:48 | MySQL Server: Compiling | Open (128 days) | S3 | 8.0.45 | MacOS (26.0.1) | ARM | Compilation error with clang 20 |
| 119225 | 2025-10-24 9:11 | 2025-10-31 5:22 | MySQL Server: Optimizer | Verified (212 days) | S3 | 8.0.43 | Any | Any | weedout not work for rematerialized temptable |
| 119220 | 2025-10-23 14:55 | 2025-11-07 9:22 | MySQL Server: Optimizer | Verified (205 days) | S2 | 8.4.6 | Any | x86 | Subquery materialization in LEFT JOIN ON clause loses WHERE conditions |
| 119204 | 2025-10-22 8:10 | 2025-10-23 10:04 | MySQL Server: DML | Verified (220 days) | S2 | 8.0,9.5 | Any | Any | The change of join order may lead to inconsistent update data |
| 119203 | 2025-10-21 12:46 | 2025-11-04 23:25 | MySQL Server: Optimizer | Verified (208 days) | S3 | 8.0.41 | Any | Any | An expression that returns NULL instead of NULL is used to perform the <=> operation. the sql retrun wrong result. |
| 119172 | 2025-10-16 10:00 | 2026-01-15 10:04 | MySQL Server: Optimizer | Verified (136 days) | S3 | 9.4.0 8.4.6 | Any | Any | Inconsistent Result for NOT BETWEEN When Date Interval Arithmetic Produces NULLs |
| 119171 | 2025-10-16 9:34 | 2026-01-15 9:37 | MySQL Server: Data Types | Verified (136 days) | S3 | 9.4.0 8.4.6 | Any | Any | Inconsistent Result for BETWEEN NULL AND NULL on a DECIMAL Column |
| 119168 | 2025-10-16 8:47 | 2026-01-14 14:52 | MySQL Server: Optimizer | Verified (137 days) | S3 | 9.4.0 | Any | Any | Inconsistent results for CHAR IN (subquery returning BIT) |
| 119160 | 2025-10-15 9:32 | 2026-01-13 11:27 | MySQL Server: Optimizer | Verified (138 days) | S3 | 8.0.41 | Any | Any | Found different values set for sql_buffer_result and materialization lead to different query results. |
| 119156 | 2025-10-15 2:01 | 2026-01-13 11:13 | MySQL Server: Optimizer | Verified (138 days) | 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 |
| 119154 | 2025-10-14 13:24 | 2026-01-13 10:22 | MySQL Server: Data Types | Verified (138 days) | S1 | 8.4.6 | Any | Any | Incorrect BIT_COUNT value for TEXT column |
| 119147 | 2025-10-13 13:39 | 2026-01-13 10:02 | MySQL Server: Optimizer | Verified (138 days) | S3 | 8.0 | Any | Any | >= SOME Operator Returns Incorrect Empty Set for TIMESTAMP Comparison |
| 119146 | 2025-10-13 12:53 | 2026-01-13 9:48 | MySQL Server: Optimizer | Verified (138 days) | S3 | 9.4.0 8.4.6 | Any | Any | WHERE IN with Subquery Incorrectly Matches VARCHAR to DECIMAL via Implicit Casting |
| 119144 | 2025-10-13 12:49 | 2026-01-06 12:48 | MySQL Server: Optimizer | Verified (145 days) | S2 | 8.4.6 | Windows | Any (x64) | INNER JOIN and STRAIGHT_JOIN return different results with identical ABS function conditions |
| 119143 | 2025-10-13 12:37 | 2026-01-06 12:44 | MySQL Server: Optimizer | Verified (145 days) | S3 | 8.4.6 | Any | Any | INNER JOIN and STRAIGHT_JOIN return different results with ATAN function |
| 119141 | 2025-10-13 8:21 | 2026-01-06 11:28 | MySQL Server: DML | Verified (145 days) | S3 | 8.0.41 | Linux | x86 | The results returned by the prepare query are different from those returned by the non-prepare query. |
| 119140 | 2025-10-13 8:01 | 2026-01-06 14:56 | MySQL Server: Optimizer | Verified (145 days) | S1 | 8.4 | Any | Any | DISTINCT works inconsistently in normal SELECT and prepared statement for 0 and -0 |
| 119139 | 2025-10-13 7:30 | 2025-12-18 8:56 | MySQL Server: Optimizer | Verified (164 days) | S1 | 9.4.0 | Any | Any | Unexpected error `Incorrect DECIMAL value: '0' for column '' at row -1` |
| 119138 | 2025-10-13 3:45 | 2026-01-06 14:41 | MySQL Server: Optimizer | Verified (145 days) | S3 | 8.0 | Any | Any | Incorrect result with BINARY EXISTS(...) IN (...) on TIMESTAMP column |
| 119137 | 2025-10-13 3:23 | 2026-01-06 14:32 | MySQL Server: Optimizer | Verified (145 days) | S3 | 8.0 | Any | Any | Incorrect result for ADDTIME expression |
| 119132 | 2025-10-11 3:44 | 2025-12-18 8:37 | MySQL Server: DML | Verified (164 days) | S3 | 8.0.41 | Any | Any | Unexpected query result when using complex boolean expressions with UNION ALL and LIKE in SELECT query |
| 119130 | 2025-10-11 2:30 | 2025-12-17 9:33 | MySQL Server: Optimizer | Verified (165 days) | S3 | 8.0.41 | Any | Any | Different values set for sql_buffer_result and materialization lead to different query results. |
| 119127 | 2025-10-10 11:58 | 2025-12-17 8:20 | MySQL Server: Optimizer | Verified (165 days) | S2 | 8.4.6 | Any | Any | INNER JOIN and INTERSECT of LEFT/RIGHT JOINs return different results when unique index is present |
| 119125 | 2025-10-10 3:52 | 2025-12-17 8:10 | MySQL Server: Optimizer | Verified (165 days) | S3 | 8.0.41 | Any | Any | after modifying the insertion sequence of the table,the results of the same query are inconsistent. |
| 119124 | 2025-10-10 3:28 | 2025-12-16 9:19 | MySQL Server: DML | Verified (166 days) | S3 | 8.0.41 | Any | Any | The result of the COALESCE function varies depending on its different parameters. |
| 119122 | 2025-10-09 11:53 | 2025-12-16 9:14 | MySQL Server: DML | Verified (166 days) | S3 | 8.0.41 | Any | Any | The query is normal without using the histogram, but an error occurs when using the histogram |
| 119118 | 2025-10-09 8:17 | 2025-12-15 12:50 | MySQL Server: Optimizer | Verified (167 days) | S3 | 8.0.41 | Any | Any | The difference in results caused by enabling or disabling the optimizer's index_merge_union. |
| 119097 | 2025-09-30 9:04 | 2025-12-15 11:15 | MySQL Server: Optimizer | Verified (167 days) | S2 | MySQL 8.4.6 | Windows | Other (x64) | STRAIGHT_JOIN returns different results compared to INNER JOIN with identical conditions |
| 119094 | 2025-09-29 13:03 | 2025-12-12 13:38 | MySQL Server: Optimizer | Verified (170 days) | S3 | Any | Any | Performance optimization patches | |
| 119087 | 2025-09-28 5:54 | 2025-12-12 9:33 | MySQL Server: Optimizer | Verified (170 days) | S3 | 9.4.0 8.4.6 | Any | Any | Incorrect result for subquery with BIGINT UNSIGNED |
| 119081 | 2025-09-27 8:35 | 2025-10-02 7:12 | MySQL Server: Optimizer | Verified (244 days) | S3 | 8.0.43 | Any | Any | UPDATE with CASE/IFNULL expression produces unexpected error: Incorrect DECIMAL value: '0' for column '' at row -1 |
| 119080 | 2025-09-27 8:16 | 2025-10-01 13:58 | MySQL Server: Optimizer | Verified (244 days) | S3 | 8.0.43 | Any | Any | SELECT vs. TLP partitioning query returns different cardinalities (cardinality mismatch) |
| 119068 | 2025-09-25 8:43 | 2025-10-01 14:05 | MySQL Server: Optimizer | Verified (244 days) | S2 | 9.4.0 | Linux | x86 | RIGHT JOIN on VIEW with IN subquery returns incorrect non-NULL value instead of NULL |
| 119066 | 2025-09-24 13:06 | 2025-10-03 11:03 | MySQL Server: Optimizer | Verified (244 days) | S5 | 8.0.40+ | Any | Any | MySQL 8.0.40+ is about 2-3x times slower than 8.0.39 in particular index scan scenario |
| 119062 | 2025-09-23 11:08 | 2025-09-25 16:09 | MySQL Server: Optimizer | Verified (250 days) | S5 | 9.4.0 | Any | Any | A missed optimization opportunity of "FALSE and any_expr" in WHERE clause |
| 119059 | 2025-09-23 3:44 | 2025-09-25 16:07 | MySQL Server: Optimizer | Verified (250 days) | S2 | 9.2.0, 9.4.0 | Any | Any | Inconsistent result behavior when using EXCEPT equivalent NATRUAL JOIN |
| 119058 | 2025-09-23 0:57 | 2025-09-25 16:08 | MySQL Server: Prepared statements | Verified (250 days) | S1 | 9.4.0 | Any | Any | `\` is inconsistent in prepared statement and normal query |
| 119056 | 2025-09-22 15:21 | 2025-09-23 2:40 | MySQL Server: Optimizer | Verified (250 days) | S3 | 9.4.0 | Any | Any | column value change cased by SUM(DISTINCT) changed to AVG(DISTINCT)*COUNT(DISTINCT) |
| 119053 | 2025-09-22 9:22 | 2025-09-23 2:40 | MySQL Server: Optimizer | Verified (250 days) | S3 | 9.4.0 8.4.6 | Any | Any | Incorrect filtering for NOT BETWEEN on a FLOAT PRIMARY KEY |
| 119052 | 2025-09-22 9:22 | 2025-09-23 2:43 | MySQL Server: Optimizer | Verified (250 days) | S5 | 8.0.43 | Linux (5.10.134-19.al8.x86_64) | x86 (x86_64) | Performance regression in 8.0.40 |
| 119048 | 2025-09-21 12:57 | 2025-09-23 1:27 | MySQL Server: Prepared statements | Verified (251 days) | S2 | 9.4.0 | Any | Any | inconsistent result of two equivalent query with operator ~ |
| 119041 | 2025-09-19 8:19 | 2025-09-23 9:57 | MySQL Server: Optimizer | Verified (250 days) | S2 | 8.0.25 8.0.40 | Any | Any | statistics automatic update cause poor execution plan |
| 119040 | 2025-09-19 6:46 | 2025-09-23 1:39 | MySQL Server: Optimizer | Verified (254 days) | S3 | 8.0.41 | Linux | x86 | The execution performance of the default execution plan is poor. If ignore index is used, the query performance is great |
| 119035 | 2025-09-18 10:11 | 2025-09-23 0:48 | MySQL Server: Optimizer | Verified (251 days) | S3 | 9.4.0 8.4.6 | Any | Any | Incorrect result for BETWEEN with mixed types on a BINARY column with a UNIQUE key |
| 119034 | 2025-09-18 9:34 | 2025-09-23 0:50 | MySQL Server: Optimizer | Verified (251 days) | S3 | 9.4.0 8.4.6 | Any | Any | Incorrect result when comparing a numeric string literal to a BIT column with a UNIQUE key |
| 119033 | 2025-09-18 9:16 | 2025-09-23 0:51 | MySQL Server: Optimizer | Verified (251 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 |
| 119032 | 2025-09-18 7:52 | 2025-09-23 0:51 | MySQL Server: Optimizer | Verified (251 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 |
| 119029 | 2025-09-18 0:40 | 2025-09-22 14:34 | MySQL Server: Optimizer | Verified (254 days) | S5 | 9.4.0 | Any | Any | Two missed optimization opportunities of "TRUE OR any_expr" |
| 119028 | 2025-09-18 0:20 | 2025-09-22 14:33 | MySQL Server: Optimizer | Verified (254 days) | S5 | 9.4.0 | Any | Any | two missed optimization oppotunities of "FALSE and any_expr" |
| 119022 | 2025-09-17 12:40 | 2025-09-23 0:51 | MySQL Server: Optimizer | Verified (251 days) | S2 | 9.4.0 | Any | Any | column value change cased by Union ALL |
| 118981 | 2025-09-10 3:41 | 2025-09-22 14:32 | MySQL Server: DML | Verified (254 days) | S3 | 8.0.41 | Any | Any | adding DEFAULT FUNCTION in the where clause, the query returns a wrong result caused by the cached value. |
| 118980 | 2025-09-10 2:52 | 2025-09-15 16:00 | MySQL Server: Optimizer | Verified (262 days) | S2 | MySQL8.0.41 | Any | Any | queries have different results using and without index |
| 118949 | 2025-09-05 13:57 | 2025-09-10 0:42 | MySQL Server: Optimizer | Verified (265 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 |
| 118941 | 2025-09-05 8:19 | 2025-09-10 14:45 | MySQL Server: Optimizer | Verified (263 days) | S2 | 8.0.x, 8.4.x | Any | Any | Bug Report: DECIMAL(22,2) Column Comparison with -0.001 Excludes 0.00 Row |
| 118937 | 2025-09-04 4:36 | 2025-09-10 0:43 | MySQL Server: Optimizer | Verified (264 days) | S2 | 9.4.0 | Any | Any | LEFT JOIN with constant functions returns incorrect results when condition is ON FALSE |
| 118913 | 2025-08-29 3:40 | 2025-09-01 10:19 | MySQL Server: Optimizer | Verified (272 days) | S2 | 8.0.41, 9.4.0 | Any | Any | queries have different results for non primary key table and table with primary key |
| 118912 | 2025-08-28 16:24 | 2025-09-04 11:48 | MySQL Server: Optimizer | Verified (272 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 |
| 118909 | 2025-08-28 11:04 | 2025-09-04 11:49 | MySQL Server: Optimizer | Verified (270 days) | S3 | 8.0.41, 9.4.0 | Linux | x86 | Inconsistent evaluation of WHERE predicate between table-scan and covering-index paths; result set changes with projecti |
| 118904 | 2025-08-28 3:20 | 2025-09-04 11:46 | MySQL Server: Optimizer | Verified (272 days) | S2 | 8.0.41+ | Any | Any | Incorrect results could be returned when using index condition pushdown and Range checked for each record |
| 118893 | 2025-08-26 8:31 | 2025-09-04 11:53 | MySQL Server: Optimizer | Verified (272 days) | S3 | 9.4.0-1.el9 | Linux | Any | "SELECT AUTO_INCREMENT FROM information_schema.TABLES" reports a value that is reduced by one |
| 118887 | 2025-08-25 2:49 | 2025-08-29 11:06 | MySQL Server: Optimizer | Verified (279 days) | S3 | 9.4.0 | CentOS | Any | Zero '0000-00-00 00:00:00' datetime returned when SQL_BUFFER_RESULT is used |
| 118875 | 2025-08-21 12:42 | 2025-08-21 13:16 | MySQL Server: DML | Verified (283 days) | S3 | 8.0.41, 8.0.43 | Any | Any | set optimizer_switch='block_nested_loop=off/on', result is different. |
| 118871 | 2025-08-21 2:37 | 2025-08-29 11:12 | MySQL Server: Optimizer | Verified (279 days) | S3 | 8.0.43 MySQL Community Server - GPL | Linux (Linux (Rocky Linux release 8.8 (Green Obsidian))) | Any | Constant conditions in SQL with derived views are not passed.new |
| 118863 | 2025-08-20 14:23 | 2025-08-21 6:30 | MySQL Server: Optimizer | Verified (283 days) | S2 | 8.4.x, 8.4.6 | Any | Any | Complex collection query incorrectly missing '0' |
| 118862 | 2025-08-20 14:05 | 2025-08-21 6:28 | MySQL Server: Optimizer | Verified (283 days) | S3 | 8.0.x, 8.4.x, 8.0.43 | Any | Any | 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 (250 days) | S2 | 9.2.0 | Linux | Any | Inconsistency between the results returned by MySQL and other vendors' database systems was found during differentiation |
| 118857 | 2025-08-20 8:39 | 2025-08-20 10:19 | MySQL Server: Optimizer | Verified (284 days) | S2 | 9.2.0 | Linux | Any | Bug Summary: MySQL Returns Incorrect Results for Complex Query with Set Operations |
| 118849 | 2025-08-18 12:14 | 2025-08-18 23:50 | MySQL Server: Optimizer | Verified (286 days) | S3 | 8.0.41 | Any | Any | after add HINT:JOIN_ORDER, the result is wrong. |
| 118846 | 2025-08-15 8:50 | 2025-08-19 7:34 | MySQL Server: Optimizer | Verified (285 days) | S3 | 9.3.0 | Ubuntu | Any | column name change cased by where |
| 118839 | 2025-08-14 3:13 | 2025-08-18 23:50 | MySQL Server: DML | Verified (286 days) | S3 | 8.0.41 | Any | Any | a query including the having subclause that returns NULL, return a wrong nonempty result. |
| 118837 | 2025-08-14 3:05 | 2025-08-18 23:51 | MySQL Server: Optimizer | Verified (286 days) | S3 | 8.0.41 | Any | Any | After having(col) in the query statement is changed to having min(col), the returned result is incorrect. |
| 118836 | 2025-08-14 3:01 | 2025-08-18 23:56 | MySQL Server: Optimizer | Verified (286 days) | S3 | 8.0.41 | Any | Any | adding a having clause that return 1/TRUE, the query returns a different and wrong empty result. |
| 118835 | 2025-08-14 2:56 | 2025-08-19 0:17 | MySQL Server: Optimizer | Verified (285 days) | S3 | 8.0.41 | Any | Any | A query statement that returns 0/FALSE in the having clause, the returned result is not null. |
| 118833 | 2025-08-14 2:43 | 2025-08-19 0:36 | MySQL Server: Optimizer | Verified (285 days) | S3 | 8.0.41 | Any | Any | Two queries that use the where clause with opposite semantics return the same result. |
| 118832 | 2025-08-14 2:39 | 2025-08-19 7:34 | MySQL Server: Optimizer | Verified (285 days) | S3 | 8.0.41, 9.4.0 | Any | Any | using the return value replacing the IFNUILL function , the query returns different value; |
| 118831 | 2025-08-14 2:33 | 2025-08-19 10:51 | MySQL Server: Optimizer | Verified (285 days) | S3 | 8.0.41, 9.4.0 | Any | Any | !(expression1 or expression2) return a different result from !(expression1), while expression2 is 0. |
| 118830 | 2025-08-14 2:26 | 2025-08-19 10:51 | MySQL Server: DML | Verified (285 days) | S3 | 8.0.41, 9.4.0 | Any | Any | After a constant value is replaced by a LEAST function returnning the same value, the sql returns different result; |
| 118811 | 2025-08-11 3:31 | 2025-08-11 12:02 | MySQL Server: Optimizer | Verified (293 days) | S3 | 8.0.43 | Linux | x86 | When hints are added, different execution plans are used for query. The query result are different. |
| 118810 | 2025-08-11 3:19 | 2025-08-11 10:35 | MySQL Server: Optimizer | Verified (293 days) | S3 | 8.0.41, 8.0.43, 8.4.6 | Linux | x86 | he query result are inconsistent,when select difference indexes |
| 118808 | 2025-08-10 11:26 | 2025-08-11 7:00 | MySQL Server: Optimizer | Verified (293 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 |
| 118806 | 2025-08-09 13:00 | 2025-08-11 5:39 | MySQL Server: Optimizer | Verified (293 days) | S3 | 8.0,9.0, 8.0.43, 8.4.6, 9.4.0 | Ubuntu | x86 | NULLIF with VARCHAR omits rows unexpectedly |
| 118788 | 2025-08-06 9:33 | 2025-08-21 8:59 | MySQL Server: Optimizer | Verified (298 days) | S3 | 8.0.41, 8.0.43 | Linux | x86 | When two tables are joined, the execution results are different in different join order. |
| 118765 | 2025-08-01 2:56 | 2025-08-01 5:26 | MySQL Server: DML | Verified (303 days) | S3 | 8.0, 9.0, 8.4.6, 8.0.43 | Any | Any | Substring_index with negative index returns inconsistent results across different character sets |
| 118729 | 2025-07-28 13:17 | 2025-07-29 6:37 | MySQL Server: Optimizer | Verified (306 days) | S3 | 8.4.4 (Any), 8.0.43, 8.4.6, 9.4.0 | Any | Any | Select Query is showing wrong column name alias from sub-query |
| 118710 | 2025-07-23 12:08 | 2025-07-23 12:42 | MySQL Server: Optimizer | Verified (312 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 |
| 118694 | 2025-07-22 7:03 | 2025-07-22 11:45 | MySQL Server: DML | Verified (313 days) | S3 | 8.0.41 5.7, 8.0.42 | Any | Any | Item_func_between deal with decimel different from other methods |
| 118684 | 2025-07-18 14:54 | 2025-07-21 6:07 | MySQL Server: Optimizer | Verified (314 days) | S2 | 9.2.0, 8.0.42, 8.4.5 | Linux | Any | Inconsistent rows are returned |
| 118682 | 2025-07-18 3:52 | 2025-10-10 7:41 | MySQL Server: Optimizer | Verified (311 days) | S2 | 8.0, 8.0.42 | Any | Any | connection_memory_limit and global_connection_memory_limit don't work |
| 118669 | 2025-07-16 5:22 | 2025-07-16 6:46 | MySQL Server: Optimizer | Verified (319 days) | S1 | 8 and above, 8.0.42, 8.4.5, 9.3.0 | Any | Any | Issue in applying limit on aggregated data |
| 118621 | 2025-07-09 12:39 | 2025-07-09 14:19 | MySQL Server: Optimizer | Verified (326 days) | S3 | 9.3.0, 8.0.42 | Any | Any | subquery_to_derived optimizer makes query produce incorrect result |
| 118585 | 2025-07-03 16:35 | 2025-07-04 6:42 | MySQL Server: Optimizer | Verified (331 days) | S5 | 8.0.39, 8.0.42, 8.4.5, 9.3.0 | Ubuntu (Ubuntu 20.04.2) | Any | system variable "range_alloc_block_size" arouse different execution plan |
| 118570 | 2025-07-02 2:29 | 2025-07-03 9:32 | MySQL Server: DML | Verified (333 days) | S5 | 8.0.42 | Linux (22.04) | x86 | Performance regression occurs with INSERT statements after c17d86b |
| 118556 | 2025-06-29 19:07 | 2025-06-30 8:14 | MySQL Server: DML | Verified (335 days) | S3 | 9.3.0 | Ubuntu | x86 | Queries on tables with same data return different results |
| 118555 | 2025-06-29 18:55 | 2025-06-30 8:09 | MySQL Server: DML | Verified (335 days) | S3 | 9.3.0 | Ubuntu | x86 | Inconsistant results in tables containing NULL values |
| 118554 | 2025-06-29 18:42 | 2025-06-30 8:05 | MySQL Server: DML | Verified (335 days) | S3 | 9.3.0 | Ubuntu | x86 | Inconsistent results on same tables with different PRIMARY KEY constraint |
| 118553 | 2025-06-29 18:26 | 2025-06-30 8:03 | MySQL Server: DML | Verified (335 days) | S3 | 9.3.0 | Ubuntu | x86 | SELECT returns different results on tables with same data |
| 118552 | 2025-06-29 18:14 | 2025-06-30 8:00 | MySQL Server: DML | Verified (335 days) | S3 | 9.3.0 | Ubuntu | x86 | Inconsistant result on tables with same data but different constraints |
| 118551 | 2025-06-29 17:59 | 2025-06-30 7:42 | MySQL Server: DML | Verified (335 days) | S3 | 9.3.0 | Ubuntu | x86 | Inconsistant result after removing constraints on table |
| 118544 | 2025-06-27 14:18 | 2025-09-23 4:03 | MySQL Server: Optimizer | Verified (250 days) | S2 | 9.2.0 , 9.3.0 | Linux | Any | A potential join operator bug |
| 118541 | 2025-06-27 8:31 | 2025-09-23 4:02 | MySQL Server: Optimizer | Verified (250 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 |
| 118540 | 2025-06-27 7:27 | 2025-09-23 4:02 | MySQL Server: Optimizer | Verified (250 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 |
| 118495 | 2025-06-20 7:40 | 2025-06-20 10:32 | MySQL Server: DML | Verified (345 days) | S3 | 8.0.41 | Linux | x86 | The query returned wrong result with l"imit offset" |
| 118475 | 2025-06-18 7:58 | 2025-06-18 8:40 | MySQL Server: DML | Verified (347 days) | S3 | 8.0.41, 8.4.5 | Any | Any | When the IF function is invoked to replace the specified column name, the returned results are inconsistent. |
| 118464 | 2025-06-17 7:24 | 2026-02-05 22:02 | MySQL Server: Optimizer | Verified (115 days) | S3 | 8.0.41 | Any | Any | Inserting into a float value exceeding the precision, using IF function and using the column return different result. |
| 118401 | 2025-06-09 13:37 | 2025-06-10 6:32 | MySQL Server: DML | Verified (356 days) | S3 | 8.0.41 | Linux | x86 | When innodb_buffer_pool_size is set a small value , the update value is abnormal. |
| 118400 | 2025-06-09 13:34 | 2025-07-24 12:28 | MySQL Server: DML | Verified (356 days) | S3 | 8.0.41 | Linux | x86 | ERROR 3854 (HY000): Cannot convert string '\xF0\x9F\x98\xA6\xF0\x9F...' from utf8mb4 to latin1 |
| 118399 | 2025-06-09 12:35 | 2025-06-09 12:46 | MySQL Server: DML | Verified (356 days) | S3 | 8.0.41 | Linux | x86 | multijoin and related subqueries are used, the query result is incorrect during optimizer_switch="derived_merge=on" |
| 118398 | 2025-06-09 8:00 | 2025-06-11 12:40 | MySQL Server: DML | Verified (354 days) | S3 | 8.0.41 | Any | Any | Using temporary with avg cause wrong result |
| 118394 | 2025-06-09 2:04 | 2026-02-05 22:18 | MySQL Server: Optimizer | Verified (115 days) | S3 | 8.0.41 | Any | Any | while (NOT XX NOT IN ()) return 0, the query with where (NOT XX NOT IN ()) returns a wrong result. |
| 118393 | 2025-06-09 1:36 | 2026-02-05 22:47 | MySQL Server: Optimizer | Verified (115 days) | S3 | 8.0.41 | Any | Any | while the having subquery return NULL actually, the query using this having query returns a wrong result. |
| 118391 | 2025-06-08 16:43 | 2025-06-10 12:23 | MySQL Server: DML | Verified (356 days) | S3 | 8.4.2, 8.0 | Any | Any | Inconsistent BIGINT overflow behavior with unary minus operator in multiplication |
| 118375 | 2025-06-06 3:41 | 2026-02-06 12:01 | MySQL Server: Optimizer | Verified (114 days) | S3 | 8.0.41 | Any | Any | while (NOT ((t0.c1) >= (t1.c2))) returns 1 actually, the query return an empty result set. |
| 118369 | 2025-06-05 11:21 | 2026-02-06 12:16 | MySQL Server: Optimizer | Verified (114 days) | S3 | 8.0.41 | Any | Any | "having column" and "having MIN(column)" return different result.something wrong during Aggregate using temporary table |
| 118352 | 2025-06-04 4:38 | 2025-06-04 8:51 | MySQL Server: Charsets | Verified (361 days) | S3 | 8.0, 8.4 | Any | Any | Illegal mix of collations when modify collation_connection |
| 118351 | 2025-06-04 2:24 | 2025-06-04 6:34 | MySQL Server: DML | Verified (361 days) | S3 | 8.0.41 | Linux | x86 | When Backward index scan is used for query SQL statements, the returned result is incorrect. |
| 118350 | 2025-06-04 2:03 | 2025-06-04 6:32 | MySQL Server: Optimizer | Verified (361 days) | S3 | 9.x | Any | Any | Contribution: Adding fuzz directory and modifications to support it. |
| 118349 | 2025-06-04 2:03 | 2025-06-04 19:16 | MySQL Server: Optimizer | Verified (361 days) | S3 | 9.x | Any | Any | Contribution: fuzz: parse_sql target |
| 118336 | 2025-06-03 8:24 | 2026-02-06 12:26 | MySQL Server: Optimizer | Verified (114 days) | S3 | 8.0.41 | Any | Any | after adding a having clause equivalent to "having 1", the returned result set is wrong |
| 118313 | 2025-05-30 9:17 | 2025-05-30 10:19 | MySQL Server: Optimizer | Verified (366 days) | S3 | 8.0.41, 8.0.42, 8.4.5, 9.3.0 | Any | Any | The query result is incorrect. |
| 118312 | 2025-05-30 8:12 | 2025-05-30 10:32 | MySQL Server: DML | Verified (366 days) | S2 | 8.0.42, 8.4.5, 9.3.0 | Any | Any | Inconsistent results when evaluating `EXCEPT` or `INTERSECT` operations involving `NULL` |
| 118310 | 2025-05-30 3:36 | 2026-02-06 12:34 | MySQL Server: Optimizer | Verified (114 days) | S3 | 8.0.41 | Any | Any | a query with a impossile having clause, return wrong results |
| 118298 | 2025-05-29 2:46 | 2026-02-06 12:48 | MySQL Server: Optimizer | Verified (114 days) | S3 | 8.0.41 | Any | Any | "(t1.c4)<-(-1.7976931348623157E308)" and "(t1.c4)<(1.7976931348623157E308)" in where clause return different results |
| 118296 | 2025-05-29 2:32 | 2025-05-29 6:03 | MySQL Server: DML | Verified (367 days) | S3 | 8.0.41 | Linux | x86 | When join_buffer_size is set to a different value, the query returns different results. |
| 118278 | 2025-05-27 8:29 | 2026-02-06 13:01 | MySQL Server: Optimizer | Verified (114 days) | S3 | 8.0.41 | Any | Any | two query SQL statements filling with opposite semantics in the where clause, result same result |
| 118277 | 2025-05-27 8:02 | 2026-02-06 13:11 | MySQL Server: Optimizer | Verified (114 days) | S3 | 8.0.41 | Any | Any | When a constant value is replaced by the IFNULL(NULL, CONST_VALUE) function, the sql returns different value; |
| 118268 | 2025-05-26 7:47 | 2026-02-06 13:22 | MySQL Server: Optimizer | Verified (114 days) | S3 | 8.0.41 | Any | Any | The returned results of two queries with the same semantics are inconsistent. |
| 118264 | 2025-05-25 15:04 | 2025-08-13 11:05 | MySQL Server: Optimizer | Verified (298 days) | S5 | 9.3.0 | Ubuntu | Any | Performance bug in SEMI JOIN with empty tables |
| 118239 | 2025-05-21 13:05 | 2025-05-29 13:12 | MySQL Server: DML | Verified (367 days) | S3 | 9.3.0 | Ubuntu (22.04) | Any | Logical Inconsistency in MySQL String Comparison with LIKE and NOT LIKE Operators |
| 118224 | 2025-05-19 2:46 | 2026-02-07 19:22 | MySQL Server: Optimizer | Verified (113 days) | S3 | 8.0.41 | Any | Any | When a constant value is replaced by the LEST function, the sql returns different value; |
| 118198 | 2025-05-14 14:16 | 2025-05-19 22:49 | MySQL Server: Optimizer | Verified (377 days) | S2 | 9.3.0 | Ubuntu (22.04) | Any | Different intersection orders lead to more than 20,000 times performance gap |
| 118181 | 2025-05-13 12:36 | 2025-07-03 9:33 | MySQL Server: DML | Verified (334 days) | S5 | 8.0.42 | Linux | x86 | Performance regression on query statements after commit 0fa789a |
| 118177 | 2025-05-13 8:53 | 2025-05-22 6:28 | MySQL Server: Optimizer | Verified (374 days) | S3 | 8.0.35 | Any | Any | Unnecessary filter operator in the execution plan |
| 118174 | 2025-05-13 6:43 | 2025-05-14 7:18 | MySQL Server: Optimizer | Verified (382 days) | S3 | 8.0 | Any | Any | Skip Scan doesn't support non-covering key scan |
| 118173 | 2025-05-13 6:42 | 2025-07-03 9:24 | MySQL Server: DML | Verified (333 days) | S5 | 8.0.42 | Ubuntu (22.04) | x86 | The insert statement suffers a performance penalty after commit cd66c5c. |
| 118164 | 2025-05-12 8:38 | 2025-05-12 13:01 | MySQL Server: DML | Verified (384 days) | S3 | 8.0.41 | Linux | x86 | When sort_buffer_size is set to a different value, group_concat returns different results. |
| 118161 | 2025-05-12 6:57 | 2025-10-27 6:49 | MySQL Server: Compiling | Verified (216 days) | S3 | 8.0.43 | MacOS (15.4.1) | ARM | Having Homebrew-installed googletest breaks build |
| 118158 | 2025-05-09 20:09 | 2025-05-12 12:05 | MySQL Server: Optimizer | Verified (384 days) | S5 | 8.4.5 | Any | Any | Endless loop while executing some CTE |
| 118144 | 2025-05-08 23:35 | 2025-05-14 10:18 | MySQL Server: Optimizer | Verified (382 days) | S5 | 8.0.40, 8.0.42 | Red Hat (RHEL9) | x86 | Performance regression at 8.0.40 related to record buffer usage |
| 118137 | 2025-05-08 11:49 | 2025-05-08 12:10 | MySQL Server: DML | Verified (388 days) | S3 | 9.3, 8.0, 8.4 | Any | Any | Contradictory query results for decimal data type |
| 118112 | 2025-05-04 21:32 | 2025-05-05 13:34 | MySQL Server: Compiling | Verified (391 days) | S3 | 9.3.0 | Windows (11) | x86 | openssl build bug |
| 118092 | 2025-04-30 3:31 | 2025-08-06 12:51 | MySQL Server: DML | Verified (396 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 |
| 118089 | 2025-04-29 14:56 | 2025-05-08 13:57 | MySQL Server: Optimizer | Verified (396 days) | S3 | 8.0.42, 8.4.5, 9.3.0 | Any | Any | COALESCE with BIT field may return wrong values |
| 118085 | 2025-04-29 12:14 | 2025-04-29 13:43 | MySQL Server: Optimizer | Verified (397 days) | S1 | 9.3,9.0,8.0,8.0.42, 8.4.5 | Any | Any | Wrong right join result involving subquery |
| 118080 | 2025-04-29 6:51 | 2025-04-29 8:08 | MySQL Server: Optimizer | Verified (397 days) | S3 | 8.0.42 | Any | Any | The execution plan for the view with UNION ALL uses a full table scan instead of an index. |
| 118073 | 2025-04-28 15:10 | 2025-04-29 6:29 | MySQL Server: Optimizer | Verified (397 days) | S1 | 9.3,9.0,8.0, 8.0.42 | Any | Any | Wrong Inner Join Result |
| 118071 | 2025-04-28 13:09 | 2025-04-28 14:07 | MySQL Server: Optimizer | Verified (398 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 |
| 118063 | 2025-04-27 19:02 | 2025-04-28 7:39 | MySQL Server: Optimizer | Verified (398 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 |
| 118061 | 2025-04-26 13:02 | 2025-04-28 7:40 | MySQL Server: Optimizer | Verified (398 days) | S1 | 9.3, 8.4.5, 8.0.42 | Any | Any | wrong inner join result when adding an additional true expression |
| 118060 | 2025-04-25 16:53 | 2026-05-18 12:38 | MySQL Server: DML | Verified (113 days) | S2 | 8.0.40 | Any | Any | After an error occurs when importing data containing NULL fields, insert can not be executed normally. |
| 118026 | 2025-04-21 15:03 | 2025-04-22 7:02 | MySQL Server: Compiling | Verified (404 days) | S3 | 8.0.42 | MacOS | Any | Build failed with apple clang 17 |
| 118024 | 2025-04-21 12:46 | 2025-04-23 8:07 | MySQL Server: Optimizer | Verified (405 days) | S1 | 9.3.0 | Any | Any | Wrong Right Join involving a predicate containing IFNULL and IN |
| 118020 | 2025-04-20 23:23 | 2025-08-12 4:14 | MySQL Server: Optimizer | Verified (377 days) | S1 | 9.2.0, 9.3.0 | Any (22.04) | Any | A critical logic bug and performance bug |
| 118018 | 2025-04-20 13:49 | 2025-08-12 4:14 | MySQL Server: Optimizer | Verified (377 days) | S1 | 9.2.0, 9.3.0 | Ubuntu (22.04) | Any | A query expose a logic bug and performance bug |
| 118017 | 2025-04-20 10:59 | 2025-08-12 4:13 | MySQL Server: Optimizer | Verified (377 days) | S5 | 9.2.0, 9.3.0 | Ubuntu (22.04) | Any | A very serious performance bug |
| 118016 | 2025-04-20 10:34 | 2025-04-21 12:52 | MySQL Server: Optimizer | Verified (406 days) | S2 | 9.3, 9.0, 8.0, 8.0.42 | Any | Any | Wrong inner join result involving subquery containing distinct |
| 118015 | 2025-04-20 7:18 | 2025-08-12 4:13 | MySQL Server: Optimizer | Verified (377 days) | S5 | 9.2.0, 9.3.0 | Ubuntu (22.04) | Any | The query which always return a empty result should not comsume executing time |
| 118014 | 2025-04-19 16:53 | 2025-04-20 13:53 | MySQL Server: Optimizer | Verified (406 days) | S2 | 9.3.0,8.0, 8.0.42, 8.4.5, 9.3.0 | Any | Any | Wrong Left Join Result |
| 118011 | 2025-04-18 13:26 | 2026-04-16 2:26 | MySQL Server: Data Types | Verified (403 days) | S3 | 8.0.41 | Any | Any | Timestamp literals with fractional seconds and time zone offset do not convert correctly |
| 118001 | 2025-04-17 4:15 | 2025-04-21 12:26 | MySQL Server: DML | Verified (405 days) | S2 | 8.4.3, 8.4.5 | Any | Any | delete sql returns error: Temporary file write failure. |
| 117959 | 2025-04-13 0:31 | 2025-04-13 16:37 | MySQL Server: Optimizer | Verified (413 days) | S2 | 9.2.0 | Ubuntu (22.04) | Any | PRIMARY KEY leads to incorrect INTERSECT result |
| 117941 | 2025-04-10 13:29 | 2025-04-10 14:45 | MySQL Server: Optimizer | Verified (416 days) | S2 | 8.0.41, 8.4.4, 9.2.0 | Any | Any | Inconsistent query results with / without NOT NULL for BLOB type |
| 117927 | 2025-04-10 6:25 | 2025-04-10 7:35 | MySQL Server: JSON | Verified (416 days) | S2 | 8.0.41, 8.4 | Any | Any | duplicate key in table while using tmp table for group by a json data |
| 117867 | 2025-04-03 8:32 | 2025-04-09 10:19 | MySQL Server: Optimizer | Verified (417 days) | S5 | 8.0.41 | Any | Any | use distinct+left join, MySQL 8.0 excute long time than MySQL 5.7 |
| 117860 | 2025-04-02 10:44 | 2025-05-12 12:20 | MySQL Server: Optimizer | Verified (384 days) | S2 | 9.2.0 | Any (Ubuntu 22.04) | Any | Read another insertion WITH CONSISTENT SNAPSHOT |
| 117856 | 2025-04-02 7:42 | 2025-04-02 8:01 | MySQL Server: Optimizer | Verified (424 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 |
| 117855 | 2025-04-02 7:37 | 2025-04-02 8:15 | MySQL Server: Optimizer | Verified (424 days) | S2 | 9.1.0 , 8.0.41, 8.4.4, 9.2.0 | Ubuntu (20.04) | Any | QUOTE Function Incorrectly Handles NULL Values |
| 117854 | 2025-04-02 7:31 | 2025-04-02 8:35 | MySQL Server: Optimizer | Verified (424 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 |
| 117853 | 2025-04-02 7:23 | 2025-04-02 9:27 | MySQL Server: Optimizer | Verified (424 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 |
| 117852 | 2025-04-02 7:14 | 2025-04-08 15:00 | MySQL Server: Optimizer | Verified (424 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 |
| 117851 | 2025-04-02 7:05 | 2025-04-02 9:45 | MySQL Server: Optimizer | Verified (424 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 |
| 117849 | 2025-04-02 6:52 | 2025-04-02 9:48 | MySQL Server: Optimizer | Verified (424 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 |
| 117848 | 2025-04-02 6:37 | 2025-04-02 9:50 | MySQL Server: Optimizer | Verified (424 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 |
| 117847 | 2025-04-02 6:29 | 2025-04-02 7:47 | MySQL Server: Optimizer | Verified (424 days) | S2 | 9.1.0 , 8.0.41, 8.4.4, 9.2.0 | Ubuntu (20.04) | Any | NULLIF Filtering Fails in WHERE Clause |
| 117834 | 2025-03-31 3:43 | 2025-04-01 7:20 | MySQL Server: Optimizer | Verified (425 days) | S3 | 9.2, 8.0.41, 8.4.4 | Ubuntu | x86 | Double negation on booleans incorrectly returns negated value |
| 117811 | 2025-03-27 15:19 | 2025-04-03 14:22 | MySQL Server: Optimizer | Verified (429 days) | S1 | 8.4.4, 8.0.41, 9.2.0 | Any | Any | Incorrect query results for BLOB type |
| 117809 | 2025-03-27 13:06 | 2025-03-27 20:10 | MySQL Server: Optimizer | Verified (430 days) | S5 | Any | Any | Statistics update failed. | |
| 117808 | 2025-03-27 7:21 | 2025-03-27 10:01 | MySQL Server: Prepared statements | Verified (430 days) | S3 | 8.0.41, 8.4.2 | Any | Any | Unexpected JSON column DML error with prepare statement |
| 117791 | 2025-03-25 13:30 | 2026-03-23 2:03 | MySQL Server: Optimizer | Open (69 days) | S3 | 8.0, 8.4, 9.2 | Any | Any | FORCE INDEX does not skip records_in_range() for 'x IS NULL' |
| 117783 | 2025-03-25 8:45 | 2025-03-26 8:20 | MySQL Server: Optimizer | Verified (431 days) | S2 | 8.0.32, 8.0.41 | Any | Any | optimizer selects the wrong index due to the "low_limit" mechanism |
| 117776 | 2025-03-24 5:01 | 2025-03-24 7:46 | MySQL Server: Optimizer | Verified (433 days) | S3 | 8.0, 8.4, 9.2 | Any | Any | Index statistics is unexpectedly used to estimate eq ranges with null part |
| 117770 | 2025-03-22 5:32 | 2025-03-24 7:54 | MySQL Server: Optimizer | Verified (433 days) | S5 | 8.0.36, 8.0.41, 8.4.4, 9.2.0 | Any | Any | rechecking_index_usage causes the materialized table to be generated using table scan in Materialize semijoin strategy |
| 117765 | 2025-03-21 3:09 | 2025-03-21 9:01 | MySQL Server: Optimizer | Verified (436 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 |
| 117721 | 2025-03-17 3:20 | 2025-03-17 7:59 | MySQL Server: DML | Verified (440 days) | S3 | 8.0, 8.0.41 | Ubuntu | x86 | Inferred type of functional index is ambiguous and restricts column values |
| 117714 | 2025-03-14 15:36 | 2025-03-21 1:11 | MySQL Server: Optimizer | Verified (439 days) | S2 | 5.7.42 | Any | Any | Incorrect row filtering when using CAST(... AS DATE) adding an AND condition. |
| 117706 | 2025-03-14 9:41 | 2025-03-14 10:18 | MySQL Server: Optimizer | Verified (443 days) | S3 | 9.1.0 , 8.0.41, 8.4.4, 9.2.0 | Ubuntu (20.04) | Any | Inconsistent Behavior when use a <=> b and a = b in queries |
| 117705 | 2025-03-14 9:39 | 2025-03-17 8:15 | MySQL Server: Optimizer | Verified (440 days) | S5 | 8.0 | Any | Any | Subquery performance degregation |
| 117704 | 2025-03-14 9:24 | 2025-03-14 10:49 | MySQL Server: Optimizer | Verified (443 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) |
| 117703 | 2025-03-14 9:00 | 2025-03-14 10:39 | MySQL Server: Optimizer | Verified (443 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 |
| 117702 | 2025-03-14 8:48 | 2025-03-14 10:29 | MySQL Server: Optimizer | Verified (443 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 |
| 117674 | 2025-03-12 6:20 | 2025-03-17 9:46 | MySQL Server: JSON | Verified (440 days) | S2 | 8.0.37, 8.0.41, 8.4.4 | Any | Any | JSON value is not recognized by Mysql inside Stored Routines |
| 117663 | 2025-03-11 8:29 | 2025-03-11 8:57 | MySQL Server: JSON | Verified (446 days) | S3 | 9.2.0 | Any | Any | JSON_ARRAY func result error |
| 117653 | 2025-03-10 3:22 | 2025-03-10 5:36 | MySQL Server: Optimizer | Verified (447 days) | S2 | 8.0, 8.0.41, 8.4.4, 9.2.0 | Ubuntu | x86 | Invisible index affects output of query result |
| 117651 | 2025-03-09 15:43 | 2025-03-10 6:50 | MySQL Server: Optimizer | Verified (447 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 |
| 117648 | 2025-03-09 14:15 | 2025-03-10 7:19 | MySQL Server: Optimizer | Verified (447 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. |
| 117634 | 2025-03-06 14:00 | 2025-03-07 12:59 | MySQL Server: Optimizer | Verified (450 days) | S1 | 8.4.4, 8.0.41 | Any | Any | Incorrect query results |
| 117619 | 2025-03-05 0:14 | 2025-03-05 5:53 | MySQL Server: Optimizer | Verified (452 days) | S2 | 8.*, 8.0.41, 8.0.44 | Any | Any | MySQL indexes in MyISAM tables not behave as expected. |
| 117606 | 2025-02-28 16:01 | 2025-02-28 16:27 | MySQL Server: Optimizer | Verified (457 days) | S1 | 8.4.4, 8.0.41 | Any | Any | Incorrect query result |
| 117598 | 2025-02-28 3:28 | 2025-09-22 15:11 | MySQL Server: Optimizer | Verified (457 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 |
| 117573 | 2025-02-26 4:47 | 2025-03-21 7:12 | MySQL Server: Optimizer | Verified (436 days) | S2 | 9.2.0, 8.0.41, 8.4.4 | Ubuntu (22.04) | x86 | Equivalent inner-join queries return different results |
| 117572 | 2025-02-26 2:37 | 2025-02-26 6:36 | MySQL Server: Optimizer | Verified (459 days) | S2 | 8.0.41 | Ubuntu (22.04) | x86 | The same query yields different results across different versions |
| 117562 | 2025-02-25 3:09 | 2025-02-25 5:53 | MySQL Server: Data Types | Verified (460 days) | S3 | 8.4.4 | Any | Any | Typo in sql/field.cc:301 |
| 117549 | 2025-02-24 2:24 | 2025-02-24 4:52 | MySQL Server: Optimizer | Verified (461 days) | S1 | 8.0, 8.0.41, 8.4.4 | Any | Any | Wrong result when use "in (select * from (set operation) d)" |
| 117534 | 2025-02-20 14:39 | 2025-02-21 11:36 | MySQL Server: Optimizer | Verified (464 days) | S3 | 8.0 | Any | Any | Create index can lead to incorrect results |
| 117500 | 2025-02-18 11:40 | 2025-03-11 8:56 | MySQL Server: Optimizer | Verified (467 days) | S2 | 9.2.0, 8.0.41, 8.4.4 | Any | Any | result error when row compared with scalar subquery using '<=>' |
| 117486 | 2025-02-17 8:04 | 2025-02-17 22:40 | MySQL Server: Optimizer | Verified (468 days) | S2 | 9.1.0, 8.0.41 | Ubuntu (22.04) | x86 | Incorrect Semi-join Execution |
| 117485 | 2025-02-17 7:04 | 2025-02-17 7:53 | MySQL Server: Optimizer | Verified (468 days) | S2 | 9.1.0, 8.0.41, 8.4.4 | Ubuntu (22.04) | x86 | Incorrect Semi-join Execution |
| 117476 | 2025-02-15 13:10 | 2025-02-20 13:36 | MySQL Server: Optimizer | Verified (467 days) | S3 | 9.1.0-cluster | Ubuntu (18.04) | x86 | Inconsistent result after using optimizer_switch |
| 117457 | 2025-02-13 2:37 | 2025-02-13 7:02 | MySQL Server: DML | Verified (472 days) | S3 | 8.4.1 9.1.0 , 8.0.41 | Windows (windows 11) | x86 (x86_64) | Unexpected results with complex WHERE conditions |
| 117456 | 2025-02-13 2:24 | 2025-02-13 6:37 | MySQL Server: DML | Verified (472 days) | S3 | 8.4.1 9.1.0, 8.0.41 | Windows (windows 11) | x86 (x86_64) | Unexpected results when using JSON_OBJECT function in WHERE clause |
| 117454 | 2025-02-13 2:08 | 2025-02-13 5:48 | MySQL Server: JSON | Verified (472 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. |
| 117453 | 2025-02-13 1:51 | 2025-02-13 5:20 | MySQL Server: DML | Verified (472 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. |
| 117452 | 2025-02-13 1:38 | 2025-02-13 4:43 | MySQL Server: DML | Verified (472 days) | S3 | 8.4.1 9.1.0 , 8.0.41 | Windows (windows 11) | x86 (x86_64) | Unexpected results with IS_IPV4_MAPPED in WHERE clause. |
| 117451 | 2025-02-13 1:33 | 2025-12-30 7:41 | MySQL Server: Optimizer | Verified (472 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. |
| 117446 | 2025-02-12 7:56 | 2025-02-12 16:11 | MySQL Server: Optimizer | Verified (473 days) | S3 | 9.2 | Any | Any | Unexpected lock wait timeout when executing select for update |
| 117443 | 2025-02-11 19:40 | 2025-08-07 17:53 | MySQL Server: Compiling | Verified (473 days) | S3 | 9.2.0 | Any | Any | cmake doesn't detect missing quadmath library |
| 117439 | 2025-02-11 14:27 | 2025-02-20 13:12 | MySQL Server: Optimizer | Verified (473 days) | S2 | 8.0, 8.0.41, 8.4.4, 9.2.0 | Ubuntu | x86 | Suspicious behaviour around creation of multi-column indexes |
| 117409 | 2025-02-07 5:48 | 2025-02-07 6:45 | MySQL Server: Optimizer | Verified (478 days) | S5 | 8.0.35, 8.0.41 | Any | Any | join with crosse table sort is not optimized away by index |
| 117408 | 2025-02-07 4:26 | 2025-02-07 8:42 | MySQL Server: Optimizer | Verified (478 days) | S5 | 8.0.41 | Any | Any | Tight index scan not used when group by does not begin with first part of key, but where condition is list of constants |
| 117387 | 2025-02-05 12:39 | 2025-02-05 15:42 | MySQL Server: Optimizer | Verified (480 days) | S2 | 8.4.4, 8.0.41 | Any | Any | Query returns wrong results when using offset limit subquery in view |
| 117386 | 2025-02-05 10:13 | 2025-02-05 13:51 | MySQL Server: Optimizer | Verified (480 days) | S2 | 8.0, 8.0.41, 8.4.4 | Ubuntu | x86 | Ambiguous functional index not based on any column under-fetches rows |
| 117348 | 2025-01-31 10:06 | 2025-01-31 13:56 | MySQL Server: Optimizer | Verified (485 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 |
| 117346 | 2025-01-30 19:17 | 2025-02-06 13:55 | MySQL Server: Compiling | Verified (485 days) | S3 | 9.2.0 | Any | Any | Contribution: Added documentation for unused bytes at the end of Protocol:: ... |
| 117299 | 2025-01-27 11:48 | 2025-10-17 10:25 | MySQL Server: Compiling | Verified (226 days) | S3 | 8.4.5, 9.2.0 | MacOS (15.2) | ARM | ddl0bulk.h:236:15: error: parameter 'prebuilt' not found in the function declaration [-Werror,-Wdocumentation] |
| 117281 | 2025-01-23 10:27 | 2025-01-23 17:01 | MySQL Server: Compiling | Verified (493 days) | S2 | 8.0 | Any | Any | sql/table_cache.cc init does not cleanup on failure |
| 117273 | 2025-01-23 4:13 | 2025-01-24 5:18 | MySQL Server: Optimizer | Verified (492 days) | S5 | 8.0.35 | Any | Any | some sort is not optimized away by index, if index have part of primary key |
| 117261 | 2025-01-22 8:37 | 2025-01-24 7:46 | MySQL Server: Optimizer | Verified (494 days) | S3 | 8.0, 8.0.40, 8.4.3 | Ubuntu | x86 | Creation of multicolumn indexes might lead to rows not being fetched during GROUP BY |
| 117242 | 2025-01-20 9:13 | 2025-01-20 9:50 | MySQL Server: Optimizer | Verified (496 days) | S2 | 8.0, 8.0.40, 8.4.3 | Ubuntu | x86 | DISTINCT does not fetch all distinct rows when used with GROUP BY |
| 117235 | 2025-01-18 7:00 | 2025-01-20 6:07 | MySQL Server: JSON | Verified (496 days) | S3 | 8.4.1,9.1.0, 8.0.40, 8.4.3 | Windows | x86 | Unexpected results when using JSON_ARRAY comparison as a predicate. |
| 117234 | 2025-01-18 6:35 | 2025-01-20 5:58 | MySQL Server: JSON | Verified (496 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. |
| 117233 | 2025-01-18 6:00 | 2025-01-20 5:54 | MySQL Server: DML | Verified (496 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. |
| 117232 | 2025-01-18 5:48 | 2025-01-20 5:29 | MySQL Server: Data Types | Verified (496 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. |
| 117223 | 2025-01-17 7:33 | 2025-01-17 9:16 | MySQL Server: Data Types | Verified (499 days) | S2 | 8.4.1 9.1.0, 8.0.40 | Windows | x86 | Query results are unexpected with BIT data type and IN operator. |
| 117222 | 2025-01-17 7:26 | 2025-01-17 9:15 | MySQL Server: Data Types | Verified (499 days) | S3 | 8.4.1 9.1.0, 8.0.40 | Windows | x86 | Query results are unexpected with BIT data type comparisons. |
| 117213 | 2025-01-16 5:22 | 2025-01-16 15:51 | MySQL Server: DML | Verified (500 days) | S3 | 8.0 | Any | Any | Wrong execution result when remove all parentheses |
| 117199 | 2025-01-13 14:07 | 2025-01-13 14:42 | MySQL Server: Optimizer | Verified (503 days) | S3 | 8.0 | Any | Any | Inconsistent Results with JSON_UNQUOTE Between Table and View |
| 117198 | 2025-01-13 13:26 | 2025-01-13 14:40 | MySQL Server: Data Types | Verified (503 days) | S3 | 8.0 | Any | Any | Inconsistent Results with CASE and Spatial Data Between Table and View |
| 117186 | 2025-01-13 3:01 | 2025-01-15 6:36 | MySQL Server: DML | Verified (503 days) | S2 | 8.0.40, 8.4.3 | Any | Any | result is incorrect |
| 117164 | 2025-01-09 6:17 | 2025-01-09 7:08 | MySQL Server: Optimizer | Verified (507 days) | S3 | 8.0.36, 8.0.40 | Any | Any | Range estimation (index dives) overestimates the rows count on large ranges. It almost doubles the actual number of rows |
| 117155 | 2025-01-09 2:29 | 2025-01-09 4:48 | MySQL Server: Optimizer | Verified (507 days) | S3 | 8.0.32, 8.0.40 | Any | Any | drived_merge optimization error |
| 117134 | 2025-01-08 10:25 | 2025-01-08 10:47 | MySQL Server: GIS | Verified (508 days) | S1 | 8.0.40 | Any | Any | ST_Buffer gives unexpected result with LinearRing |
| 117131 | 2025-01-08 7:52 | 2025-01-09 9:20 | MySQL Server: DML | Verified (507 days) | S3 | 8.4.1, 8.0.40 | Windows (windows 11) | x86 (x86_64) | Query results don't match expectations with FIELD function in predicate. |
| 117130 | 2025-01-08 7:03 | 2025-01-08 7:50 | MySQL Server: Parser | Verified (508 days) | S3 | 9.1.0 | Any | Any | error occurs when using cast collate binary |
| 117129 | 2025-01-08 6:33 | 2025-01-08 7:15 | MySQL Server: GIS | Verified (508 days) | S3 | 8.0.40 | Any | Any | Potential bug in ST_Crosses |
| 117128 | 2025-01-08 5:42 | 2025-01-13 9:23 | MySQL Server: DML | Verified (508 days) | S3 | 8.4.1, 8.0.40 | Windows (windows 11) | x86 | Query results do not meet expectations when the predicate involves CAST AS FLOAT and >> operator |
| 117127 | 2025-01-08 5:38 | 2025-01-08 7:38 | MySQL Server: DML | Verified (508 days) | S3 | 8.4.1, 8.0.40 | Windows (windows 11) | x86 (x86_64) | Query results do not meet expectations when the predicate involves CASE WHEN and LIKE |
| 117120 | 2025-01-07 12:40 | 2025-01-07 12:46 | MySQL Server: GIS | Verified (509 days) | S3 | 9.0, 8.0.40 | Any | Any | Inconsistent Results with ST_Collect in WHERE Clause |
| 117105 | 2025-01-04 10:02 | 2025-01-06 9:43 | MySQL Server: Optimizer | Verified (512 days) | S2 | 8.0.39, 8.0.40 | Any | Any | Dependent subqueries incorrect results |
| 117096 | 2025-01-02 8:43 | 2025-01-02 11:59 | MySQL Server: DML | Verified (514 days) | S3 | 8.4.1, 8.0.40 | Windows (windows 11) | x86 (x86_64) | The result of using CAST AS DOUBLE in the query does not meet expectations. |
| 117095 | 2025-01-02 7:00 | 2025-01-02 7:24 | MySQL Server: DML | Verified (514 days) | S3 | 8.4.1, 8.0.40 | Windows (windows 11) | x86 (x86_64) | The GREATEST function in the predicate behaves unexpectedly. |
| 117094 | 2025-01-02 6:31 | 2025-01-02 7:35 | MySQL Server: DML | Verified (514 days) | S3 | 8.4.1, 8.0.40 | Windows (windows 11) | Any (x86_64) | Using TRUE and * in SELECT returns different row counts. |
| 117091 | 2025-01-01 15:26 | 2025-01-02 7:37 | MySQL Server: DML | Verified (514 days) | S3 | 8.4.3, 8.0.40 | Windows (windows 11) | x86 (x86_64) | Using two mutually exclusive predicates as WHERE conditions returned the same result. |
| 117089 | 2025-01-01 8:37 | 2025-01-01 9:29 | MySQL Server: DML | Verified (515 days) | S3 | 8.4.1, 8.0.40 | Windows (windows 11) | x86 (x86_64) | Inconsistent results using equivalent predicates in two queries. |
| 117076 | 2024-12-30 13:38 | 2024-12-30 13:49 | MySQL Server: GIS | Verified (517 days) | S2 | 8.0.40 | Any | Any | ST_Intersection returns a non-empty result for two geometries that are disjoint. |
| 117072 | 2024-12-30 9:24 | 2024-12-30 10:06 | MySQL Server: Optimizer | Verified (517 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 |
| 117063 | 2024-12-28 13:40 | 2024-12-30 13:44 | MySQL Server: GIS | Verified (517 days) | S1 | 8.0.40 | Any | Any | Spatial index causes the disjoint predicate gives wrong result with WHERE,INNER JOIN and CROSS JOIN, |
| 117060 | 2024-12-27 13:28 | 2024-12-27 13:39 | MySQL Server: DML | Verified (520 days) | S3 | 8.4.3, 8.0.40 | Any | Any | changing a constant TRUE to a condition involving TO_DAYS leads to a different result set |
| 117059 | 2024-12-27 13:14 | 2024-12-27 13:17 | MySQL Server: DML | Verified (520 days) | S3 | 8.4.3, 8.0.40 | Any | Any | Inconsistent Query Results Between Materialized Table and View with Division |
| 117058 | 2024-12-27 13:01 | 2024-12-27 13:16 | MySQL Server: DML | Verified (520 days) | S3 | 8.4.3, 8.0.40 | Any | Any | Inconsistent Results When Using COALESCE |
| 117057 | 2024-12-27 12:35 | 2024-12-27 13:16 | MySQL Server: DML | Verified (520 days) | S3 | 8.4.3, 8.0.40 | Any | Any | Inconsistent Results Between Materialized Table and View with GREATEST |
| 117055 | 2024-12-27 10:11 | 2024-12-27 12:49 | MySQL Server: Optimizer | Verified (520 days) | S3 | 8.0.40, 8.4.3 | Any | Any | Query result may be incorrect if unique index contains NULL |
| 117048 | 2024-12-26 9:06 | 2024-12-30 13:44 | MySQL Server: GIS | Verified (517 days) | S2 | 8.0.40 | Any | Any | ST_Buffer gives unexpected reuslt using end_flat strategy with closed Linestring |
| 117047 | 2024-12-26 8:27 | 2024-12-30 13:44 | MySQL Server: GIS | Verified (517 days) | S1 | 8.0.40 | Any | Any | ST_Touches always return null with Point and GeometryCollection with Points |
| 117046 | 2024-12-25 12:44 | 2024-12-30 13:44 | MySQL Server: GIS | Verified (517 days) | S2 | 8.0.40 | Any | Any | Negative buffer of a polygon gives an result that not small enough. |
| 117042 | 2024-12-25 6:56 | 2024-12-30 13:43 | MySQL Server: GIS | Verified (517 days) | S2 | 8.0.40 | Windows | Any | ST_Within gives unexpected result with Linestring and Polygon in WGS84. |
| 117040 | 2024-12-24 13:04 | 2024-12-24 13:14 | MySQL Server: DML | Verified (523 days) | S3 | 8.4.3, 8.0.40 | Windows (windows 11) | x86 (x86_64) | Inconsistent behavior for the same query on a DATETIME column with and without a PRIMARY KEY constraint. |
| 117036 | 2024-12-23 7:28 | 2024-12-31 5:43 | MySQL Server: GIS | Verified (524 days) | S2 | 8.0, 8.0.40 | Any | Any | Spatial Index causes CHECK TABLE to fail |
| 117017 | 2024-12-18 19:11 | 2025-01-09 17:17 | MySQL Server: Optimizer | Verified (528 days) | S3 | 8.0 | Any | Any | Incorrect Operator Precedence of IN and Comparators in MySQL 8.4.3 and 9.1.0 |
| 116964 | 2024-12-13 8:06 | 2024-12-13 9:31 | MySQL Server: Optimizer | Verified (534 days) | S2 | 8.0.38, 8.0.40 | Linux | Any | Result mismatch caused by derived condition push down. |
| 116937 | 2024-12-11 8:25 | 2024-12-11 15:33 | MySQL Server: Optimizer | Verified (536 days) | S3 | 8.0, 8.0.40 | Any | Any | estimation of REF is modified by index diving of INDEX MERGE |
| 116900 | 2024-12-07 8:28 | 2024-12-09 8:10 | MySQL Server: Optimizer | Verified (538 days) | S5 | 8.0.40 | Any | Any | ReuseRangeEstimateForRef does not work properly when there are non-prefixed multi keypart ref |
| 116895 | 2024-12-06 11:45 | 2024-12-25 3:09 | MySQL Server: Optimizer | Verified (541 days) | S2 | 9.0,8.0, 8.0.40, 8.4.3 | Any | Any | View using IN(SELECT LIMIT) has wrong result |
| 116893 | 2024-12-06 9:22 | 2024-12-06 9:43 | MySQL Server: DML | Verified (541 days) | S3 | 9.0, 8.0.40 | Any | Any | Inconsistent Results Between Materialized Table and View with GREATEST |
| 116892 | 2024-12-06 8:39 | 2024-12-06 9:43 | MySQL Server: DML | Verified (541 days) | S3 | 9.0, 8.0.40 | Any | Any | Inconsistent Query Results Between Materialized Table and View with FROM_UNIXTIME |
| 116890 | 2024-12-06 7:31 | 2024-12-06 11:41 | MySQL Server: Data Types | Verified (541 days) | S3 | 8.0 | Any | Any | Inconsistent Query Results Between Materialized Table and View with CHAR Function |
| 116873 | 2024-12-04 14:29 | 2024-12-04 15:12 | MySQL Server: Data Types | Verified (543 days) | S3 | 8.0 | Any | Any | When comparing SMALLINT and FLOAT, the type conversion logic is incorrect. |
| 116862 | 2024-12-04 5:11 | 2024-12-04 6:51 | MySQL Server: DML | Verified (543 days) | S2 | 8.4.1, 8.0.40, 8.4.3, 9.1.0 | Red Hat (Linux 3.10.0-1160.102.1.el7.x86_64) | x86 (x86_64) | After deleting the index, the same query produces inconsistent results compared to before. |
| 116852 | 2024-12-03 3:33 | 2024-12-03 6:17 | MySQL Server: JSON | Verified (544 days) | S3 | 8.0.34, 8.0.40 | Any | Any | Difference between JSONPath "$" vs "$[*]" |
| 116846 | 2024-12-02 14:42 | 2024-12-04 15:06 | MySQL Server: Data Types | Verified (543 days) | S3 | 8.0 | Any | Any | The logical error of the NULLIF function in the WHERE condition. |
| 116803 | 2024-11-27 11:29 | 2025-03-22 0:37 | MySQL Server: Optimizer | Verified (538 days) | S5 | 8.0.40 | Any | Any | MySQL 8.0.33 is slower than MySQL 8.0.28 with queries using JOINS |
| 116777 | 2024-11-25 19:50 | 2024-11-27 12:52 | MySQL Server: Optimizer | Verified (550 days) | S5 | 596f0d23 (9.0.0), 8.0.40 | Any | Any | Performance of TPC-DS Query 47 |
| 116776 | 2024-11-25 18:45 | 2024-11-28 7:53 | MySQL Server: Optimizer | Verified (549 days) | S5 | 596f0d23 (9.0.0), 8.0.40 | Any | Any | Performance of TPC-DS Query 19 |
| 116775 | 2024-11-25 18:34 | 2024-11-28 8:00 | MySQL Server: Optimizer | Verified (549 days) | S5 | 596f0d23 (9.0.0), 8.0.40 | Any | Any | Performance of TPC-DS Query 16 |
| 116774 | 2024-11-25 18:00 | 2024-11-28 8:02 | MySQL Server: Optimizer | Verified (549 days) | S5 | 596f0d23 (9.0.0), 8.0.40 | Any | Any | Performance of TPC-DS Query 15 |
| 116773 | 2024-11-25 17:40 | 2024-11-28 8:02 | MySQL Server: Optimizer | Verified (549 days) | S5 | 596f0d23 (9.0.0), 8.0.40 | Any | Any | Performance of TPC-DS Query 7 |
| 116765 | 2024-11-25 2:18 | 2024-11-25 13:34 | MySQL Server: Optimizer | Verified (552 days) | S3 | 8.0 | Any (22.04) | Any | Incorrect Operator Precedence of BETWEEN and Comparators in MySQL 8.4 |
| 116727 | 2024-11-20 8:27 | 2024-11-20 8:50 | MySQL Server: Optimizer | Verified (557 days) | S1 | 8.4.2, 8.0.40 | Any | Any | Issues with independent subqueries. |
| 116726 | 2024-11-20 8:22 | 2024-11-20 8:50 | MySQL Server: Optimizer | Verified (557 days) | S1 | 8.4.2, 8.0.40 | Any | Any | Issues with the combination of CAST and DATE. |
| 116725 | 2024-11-20 7:44 | 2024-11-20 8:54 | MySQL Server: Optimizer | Verified (557 days) | S1 | 8.4.2, 8.0.40 | Any | Any | Issues with CASE statements. |
| 116724 | 2024-11-20 7:44 | 2024-11-20 8:49 | MySQL Server: Optimizer | Verified (557 days) | S1 | 8.4.2, 8.0.40 | Any | Any | Issues with CASE statements |
| 116723 | 2024-11-20 7:35 | 2024-11-20 8:45 | MySQL Server: Optimizer | Verified (557 days) | S2 | 8.4.2, 8.0.40 | Any | Any | Issues with explicit type casting using CAST. |
| 116722 | 2024-11-20 7:11 | 2024-11-20 7:37 | MySQL Server: Optimizer | Verified (557 days) | S1 | 8.4.2, 8.0.40 | Any | Any | Issues with the COALESCE function. |
| 116721 | 2024-11-20 7:01 | 2024-11-20 7:37 | MySQL Server: Optimizer | Verified (557 days) | S1 | 8.4.2, 8.0.40 | Any | Any | Issues with combining COALESCE and DATE functions. |
| 116720 | 2024-11-20 6:48 | 2024-11-20 7:37 | MySQL Server: Optimizer | Verified (557 days) | S1 | 8.4.2, 8.0.40 | Any | Any | Issues with the combination of CASE and DATE. |
| 116710 | 2024-11-19 12:47 | 2024-11-20 11:02 | MySQL Server: Optimizer | Verified (557 days) | S3 | 8.0 | Any | Any | explain shows wrong cost value |
| 116703 | 2024-11-19 6:06 | 2024-11-19 6:28 | MySQL Server: JSON | Verified (558 days) | S3 | 8.0.33, 8.0.40, 8.4.3, 9.1.0 | Any | Any | `JSON_VALID` has inconsistent behavior for `NULL` |
| 116688 | 2024-11-18 3:23 | 2024-11-18 6:46 | MySQL Server: JSON | Verified (559 days) | S2 | 8.0.36, 8.0.40, 8.4.3, 9.1.0 | Any | Any | Unexpected Behavior in `CASE` Statement with JSON Null Values |
| 116636 | 2024-11-13 5:25 | 2024-11-15 15:26 | MySQL Server: Optimizer | Verified (562 days) | S2 | 8.4.3, 8.0.40, 9.1.0 | Any | Any | Optimizer incorrectly ignores all indexes with NO_INDEX() in some cases |
| 116624 | 2024-11-12 6:58 | 2024-11-27 8:24 | MySQL Server: Compiling | Verified (550 days) | S3 | latest commit | Windows (Windows 11) | x86 | [MSVC] Race condition occurs during msbuild with VS2022 |
| 116616 | 2024-11-11 15:37 | 2024-11-12 14:27 | MySQL Server: Compiling | Verified (566 days) | S3 | 9.0 | Any | Any | Documentation around AUTHENTICATION_CLIENT_PLUGINS in MySQL 9.0 is misleading |
| 116612 | 2024-11-11 11:46 | 2025-05-07 7:17 | MySQL Server: Optimizer | Verified (566 days) | S5 | 8.0.40, 8.0.41, 8.4.4 | Any | Any | Performance degradation of distinct operator from 5.7 to 8.0 |
| 116606 | 2024-11-10 6:44 | 2024-11-11 7:16 | MySQL Server: JSON | Verified (566 days) | S2 | 9.0, 8.0.40, 8.4.3, 9.1.0 | Any | Any | Incorrect Grouping in JSON_OBJECTAGG Aggregation for Case-Sensitive Column |
| 116594 | 2024-11-08 6:13 | 2024-11-26 7:51 | MySQL Server: Compiling | Verified (551 days) | S2 | 8.4, 8.0 | Windows | x86 | [MSVC] MySQL failed to build with msvc on Windows when add ASAN option |
| 116584 | 2024-11-07 11:58 | 2024-11-10 6:46 | MySQL Server: Charsets | Verified (570 days) | S2 | 8.0.36, 8.0.40 | Any (Redhat 7.4) | Any (Intel) | Query produces different resultset with force index |
| 116572 | 2024-11-06 19:58 | 2024-11-11 10:05 | MySQL Server: DML | Verified (569 days) | S3 | 8.0 | Any | Any | Inconsistent MATCH() Relevance Scores in BOOLEAN MODE When Grouping Results |
| 116547 | 2024-11-05 6:06 | 2024-11-05 8:08 | MySQL Server: DML | Verified (572 days) | S3 | 9 | Any | Any | Inconsistent WHERE Condition Handling for ELT Function |
| 116534 | 2024-11-03 10:40 | 2024-11-06 12:58 | MySQL Server: Optimizer | Verified (571 days) | S5 | 596f0d23 (9.0.0) | Any | Any | Another Performance of TPC-H Query 16 |
| 116492 | 2024-10-28 11:47 | 2024-11-06 13:48 | MySQL Server: Charsets | Verified (571 days) | S5 | 8.0, 8.0.40 | Any | Any | The utf8mb4 character set has worse performance |
| 116484 | 2024-10-26 20:54 | 2024-10-31 15:06 | MySQL Server: Optimizer | Verified (577 days) | S5 | 596f0d23 (9.0.0), 9.1.0 | Any | Any | Unexpected Performance Dropdown for Query 11 in TPC-H |
| 116456 | 2024-10-23 6:43 | 2024-11-06 13:57 | MySQL Server: Optimizer | Verified (577 days) | S5 | 596f0d23 (9.0.0), 9.1.0 | Any | Any | Performance of TPC-H Query 8 |
| 116453 | 2024-10-22 21:49 | 2024-10-23 17:27 | MySQL Server: Optimizer | Verified (585 days) | S1 | 9.0.0, 9.1.0 | Any | Any | query_rewrite.flush_rewrite_rules() does not honor binlog_row_metadata=FULL |
| 116438 | 2024-10-21 19:06 | 2024-10-23 10:12 | MySQL Server: Data Types | Verified (585 days) | S3 | 8.0 | Any | Any | Timestamp literals have deceptive behavior in operations |
| 116414 | 2024-10-19 6:27 | 2024-10-19 15:07 | MySQL Server: DML | Verified (589 days) | S1 | 8.4.2, 8.0.40 | Ubuntu | Any | BOLB type or operation |
| 116400 | 2024-10-18 4:06 | 2024-10-18 5:56 | MySQL Server: Optimizer | Verified (590 days) | S2 | trunk (9.1.0), 8.0.30, 8.4.3, 8.4.0 | Any | Any | Contribution by Tencent: crash on explain format=tree for conn with subquery |
| 116398 | 2024-10-17 14:34 | 2024-10-25 9:40 | MySQL Server: Optimizer | Verified (583 days) | S2 | 8.0 | Any | Any | Incorrect result with LEFT JOIN and small join_buffer_size |
| 116352 | 2024-10-14 2:57 | 2025-01-06 5:30 | MySQL Server: GIS | Verified (594 days) | S3 | 8.0.31, 8.0.39, 8.4.2 | Any | Any | spatial index cause check table wrong |
| 116338 | 2024-10-10 18:59 | 2024-10-11 7:55 | MySQL Server: DML | Verified (597 days) | S3 | 8.0.39 | Any | Any | INSERT fails on virtual date column referring to datetime column |
| 116335 | 2024-10-10 16:53 | 2025-09-10 1:54 | MySQL Server: Optimizer | Verified (597 days) | S5 | 8.0.39 | Any | Any | Multi-valued index isn't used with some range scans on composite indexes |
| 116322 | 2024-10-09 10:48 | 2024-10-09 11:59 | MySQL Server: DML | Verified (599 days) | S3 | 9.0.1, 8.0.39 | Any | Any | when log in mysql and do not select database, delete stmt returns error |
| 116309 | 2024-10-07 10:39 | 2024-10-22 11:32 | MySQL Server: Optimizer | Verified (586 days) | S5 | 596f0d23 (9.0.0), 9.1.0 | Ubuntu | Any | Performance of TPC-H Query |
| 116300 | 2024-10-04 13:44 | 2024-10-04 14:34 | MySQL Server: JSON | Verified (604 days) | S2 | 9.0 | Any | Any | TINYBLOB and BLOB with same value, stored as JSON, become different |
| 116241 | 2024-09-26 10:05 | 2024-10-25 11:03 | MySQL Server: Optimizer | Verified (583 days) | S5 | 596f0d23 (9.0.0), 9.1.0 | Any | Any | Potential Performance Improvement on TPC-H |
| 116227 | 2024-09-25 13:03 | 2024-10-09 11:58 | MySQL Server: DML | Verified (612 days) | S3 | 9.0.1 | Any | Any | Some incorrect time should be detected |
| 116211 | 2024-09-24 8:14 | 2024-09-26 11:19 | MySQL Server: DML | Verified (614 days) | S3 | 9.0.1, 8.4.2, 8.0.39 | Any | Any | zero value of year does not display as 4 characters in union clause |
| 116182 | 2024-09-20 13:39 | 2025-05-13 7:38 | MySQL Server: DML | Verified (618 days) | S3 | 9.0.1, 8.4.2, 8.0.39, 8.4.3 | Any | Any | recursive CTE handling of decimal is unexpected |
| 116173 | 2024-09-20 7:16 | 2024-09-23 14:25 | MySQL Server: Compiling | Verified (618 days) | S3 | 8.0.39 | Red Hat (9) | Any | Can't build Mysql 8.0.39 in Copr for EPEL9 |
| 116163 | 2024-09-19 14:08 | 2024-09-24 12:36 | MySQL Server: Optimizer | Verified (614 days) | S2 | 9.0 | Any | Any | COALESCE(BIT), IF(BIT) return a wrong result |
| 116160 | 2024-09-19 10:28 | 2024-09-20 8:58 | MySQL Server: JSON | Verified (618 days) | S3 | 8.0 | Any | Any | Precision loss of double value in JSON |
| 116050 | 2024-09-10 6:14 | 2026-01-28 2:13 | MySQL Server: Optimizer | Verified (123 days) | S2 | 8.0.39, 8.4.2 | Linux (centos7) | x86 | The query results are incorrect when using CTE, CONCAT, and IN. |
| 116043 | 2024-09-09 15:38 | 2024-09-12 1:22 | MySQL Server: Compiling | Verified (627 days) | S3 | 8.0.39 | Linux | Any | CMakeLists.txt Incorrectly Sets LINUX Flag |
| 116034 | 2024-09-08 16:54 | 2024-09-09 7:05 | MySQL Server: Optimizer | Verified (629 days) | S3 | 8.4.2, 8.0.39, 9.0.1 | Any | Any | Unexpected behavior when subquery returns an empty set |
| 116014 | 2024-09-05 15:43 | 2024-11-07 14:51 | MySQL Server: Optimizer | Verified (613 days) | S5 | 8.0.27+ | Any | Any | Performance Degradation in Query Execution Plans |
| 115969 | 2024-08-30 13:59 | 2024-09-02 10:36 | MySQL Server: Optimizer | Verified (636 days) | S5 | 8.0.39 | Any | Any | MySQL need not sort with ORDER BY primary_key on InnoDB on partial index match |
| 115893 | 2024-08-22 10:11 | 2024-08-22 12:55 | MySQL Server: Data Types | Verified (647 days) | S3 | 8.0 | Any | Any | Inconsistent Results When Using COALESCE |
| 115856 | 2024-08-18 12:56 | 2024-08-19 7:26 | MySQL Server: JSON | Verified (650 days) | S3 | 8.0, 8.4, 9.0 | Any | Any | Composite multi-valued index fails to be used for sorting |
| 115843 | 2024-08-15 8:26 | 2024-08-21 8:04 | MySQL Server: Optimizer | Verified (648 days) | S2 | 8.0.32, 8.0.39 | Any | Any | The incorrect calculation of 'select_limit' led to an incorrect index selection |
| 115842 | 2024-08-15 8:21 | 2024-08-20 7:37 | MySQL Server: DML | Verified (654 days) | S2 | 8.0.39, 8.4.2, 9.0.1 | Any | Any | The count distinct aggregation funciton of UUID returned an error value |
| 115840 | 2024-08-15 2:30 | 2024-08-26 7:58 | MySQL Server: Optimizer | Verified (654 days) | S2 | 8.0.39, 8.4.2, 9.0.1 | Any | Any | Contribute by Tencent:Incorrect Cost Display for Join with Materialized Subquery |
| 115830 | 2024-08-14 2:24 | 2024-08-14 6:06 | MySQL Server: DML | Verified (655 days) | S3 | 8.0.39, 8.4.2, 9.0.1 | Any | Any | `Replace into` may be invalid when functional key is unique |
| 115824 | 2024-08-13 7:36 | 2025-07-23 8:06 | MySQL Server: Charsets | Verified (650 days) | S3 | 8.0 | Any | Any | The same LOAD DATA 5.7 and 8.0 result in different |
| 115815 | 2024-08-12 2:56 | 2024-08-12 8:03 | MySQL Server: Optimizer | Verified (657 days) | S2 | 8.4.2 | Any | Any | Contribute by tencent: EXPLAIN FORMAT=TREE Incorrectly Shows Cost of Statement |
| 115804 | 2024-08-09 5:10 | 2024-08-15 11:02 | MySQL Server: Optimizer | Verified (660 days) | S3 | 8.0, 8.0.39 | Any | Any | Key not found error when executing query |
| 115796 | 2024-08-08 10:18 | 2024-08-08 10:23 | MySQL Server: Optimizer | Verified (661 days) | S3 | 8.0.30,8.4.0 | Any | Any | derived_merge affect exists-subselect condition pushdown |
| 115794 | 2024-08-08 1:54 | 2024-08-08 6:38 | MySQL Server: Optimizer | Verified (661 days) | S3 | 8.0.30,8.4.0 | Any | Any | wrong plan may occur when EXISTS-subselect displays its correlated cache item |
| 115782 | 2024-08-06 11:24 | 2024-08-06 11:55 | MySQL Server: Optimizer | Verified (663 days) | S3 | 8.0.30,8.4.0 | Any | Any | unfair comparison between materialization and EXISTS |
| 115778 | 2024-08-06 6:24 | 2024-08-07 7:17 | MySQL Server: DML | Verified (662 days) | S3 | 8.4.0, 8.0 | Any | Any | Cast DATE_ADD/SUB result as double get wrong result. |
| 115723 | 2024-07-30 5:02 | 2025-01-22 2:51 | MySQL Server: DML | Verified (494 days) | S3 | 9.0.1, 8.0.39 | Any | Any | For into exists strategy of subquery, table condition may be ignored |
| 115679 | 2024-07-24 9:04 | 2024-07-24 9:46 | MySQL Server: Optimizer | Verified (676 days) | S5 | 8.0.37 | Any | Any | Block Nested-Loops Join can sometimes slow down the query |
| 115676 | 2024-07-24 4:34 | 2024-07-24 9:46 | MySQL Server: Optimizer | Verified (676 days) | S5 | 8.0.37, 8.0.39 | Any | Any | The optimizer has chosen a poor execution plan. |
| 115671 | 2024-07-23 9:47 | 2024-07-23 13:49 | MySQL Server: Optimizer | Verified (677 days) | S5 | 8.0.37, 8.0.39 | Any | Any | The optimizer has chosen a poor execution plan. |
| 115661 | 2024-07-22 5:48 | 2024-08-15 14:22 | MySQL Server: Optimizer | Verified (678 days) | S2 | mysql 8.4.1, 8.0.38, 9.0.0 | Linux | Any | Query results are incorrect after semijoin is turned on |
| 115654 | 2024-07-20 14:01 | 2025-07-30 11:58 | MySQL Server: Optimizer | Verified (678 days) | S2 | 9.0.0, 8.0.38, 8.4.1, 9.3 | Ubuntu (Ubuntu 20.04.6 LTS) | x86 (5.15.0-113-generic) | Changing “internal_tmp_mem_storage_engine” returns incorrect results |
| 115565 | 2024-07-11 9:37 | 2024-07-11 13:11 | MySQL Server: Optimizer | Verified (689 days) | S3 | 8.0 | Any | Any | Partition tables:compare the field with null and return an incorrect result |
| 115560 | 2024-07-10 15:43 | 2024-07-12 8:14 | MySQL Server: Optimizer | Verified (688 days) | S3 | 8.0.38 | Linux | Any | JSON functional index not being considered for NULL check |
| 115559 | 2024-07-10 13:59 | 2024-07-11 13:10 | MySQL Server: Optimizer | Verified (689 days) | S3 | 8.0 | Any | Any | Row constructor comparison with nested join fails to match rows |
| 115555 | 2024-07-10 10:31 | 2024-09-16 9:49 | MySQL Server: Optimizer | Verified (636 days) | S5 | 8.4, 8.0.39 | Any | Any | Severe performance regression in filesort |
| 115551 | 2024-07-10 1:09 | 2024-07-27 0:12 | MySQL Server: Compiling | Verified (673 days) | S3 | 8.0 | Any | Any | comp_err hits AddressSanitizer: stack-buffer-overflow |
| 115519 | 2024-07-05 4:24 | 2024-07-16 13:34 | MySQL Server: Optimizer | Verified (684 days) | S2 | 8.2, 8.4.1 | Any | Any | INTERSECT within correlated subquery results in incorrect result |
| 115518 | 2024-07-05 3:26 | 2024-08-15 7:00 | MySQL Server: DML | Verified (695 days) | S3 | 8.0.38,5.7.44,8.4,9.0 | Any | Any | Lost a record while scanning in reverse order on cursor |
| 115507 | 2024-07-04 7:22 | 2025-07-11 5:10 | MySQL Server: Optimizer | Verified (696 days) | S3 | 8.4.0, 8.4.1, 8.0.38 | Any | Any | if set subquery_to_derived=on, unqualified_count could not be genereated |
| 115471 | 2024-07-01 5:04 | 2024-07-04 8:23 | MySQL Server: Compiling | Verified (696 days) | S3 | 8.0.37, 8.4.0 | MacOS (14.5) | ARM | Linker errors with enabled LTO |
| 115410 | 2024-06-23 16:02 | 2024-06-26 14:33 | MySQL Server: Data Types | Verified (705 days) | S3 | 8.0 | Any | Any | MySQL bit field index affects query results unexpectedly. |
| 115400 | 2024-06-21 4:14 | 2024-07-02 14:58 | MySQL Server: Optimizer | Verified (709 days) | S3 | 8.4.0 LTS | Any | Any | The hint /+ NO_BNL(t0)/ does not always work as expected |
| 115398 | 2024-06-20 23:58 | 2024-06-21 5:51 | MySQL Server: Charsets | Verified (709 days) | S3 | 8.4.0 | Any | Any | Contribution: Add \"Traditional Chinese\" collation for utf8mb4 |
| 115380 | 2024-06-19 8:21 | 2024-06-19 8:53 | MySQL Server: Optimizer | Verified (711 days) | S3 | 8.0.32, 8.0.37 | Any | Any | Update Multiple table failed when table is partitioned and using MRR path |
| 115353 | 2024-06-17 7:22 | 2024-10-14 15:29 | MySQL Server: Optimizer | Verified (713 days) | S2 | 8.0.37, 8.4.0 LTS | Any | Any | Setting index_merge_union leads to incorrect results. |
| 115327 | 2024-06-13 22:01 | 2024-06-19 12:26 | MySQL Server: Optimizer | Verified (711 days) | S5 | 8.0.37, 8.4.0 | Any | Any | Higher memory requirements for range optimizer in v. 8.0 vs 5.7 |
| 115283 | 2024-06-11 12:00 | 2024-10-31 10:16 | MySQL Server: Optimizer | Verified (719 days) | S2 | 8.0.37 | Any | Any | result not correct when using ‘<=>’ operator compare null value |
| 115279 | 2024-06-11 7:10 | 2024-06-11 11:52 | MySQL Server: Compiling | Verified (719 days) | S3 | 8.0.37 | Any | Any | Warning about YYSTYPE in mysql-8.0.37 |
| 115278 | 2024-06-11 6:54 | 2024-06-11 8:59 | MySQL Server: DML | Verified (719 days) | S2 | 8.0.36, 8.0.37 | Any (Tested on Windows and AWS RDS)) | Any (Tested on x64 and AWS Graviton (Arm)) | Missing records in result when nullablle field with a unique index<=>NULL |
| 115269 | 2024-06-10 12:53 | 2024-06-11 10:29 | MySQL Server: DML | Verified (720 days) | S3 | 8.0 | Any | Any | "INSERT SET column=column" inserts zero date |
| 115227 | 2024-06-05 10:45 | 2024-08-09 9:32 | MySQL Server: Optimizer | Verified (725 days) | S5 | 8.0 | Any | Any | prepared statement encounter performance degradation compared with normal select |
| 115208 | 2024-06-04 8:51 | 2024-06-04 9:08 | MySQL Server: Optimizer | Verified (726 days) | S3 | 8.0.33 | Any | Any | Last_query_cost could be negative number due to unmatched cost values in JOIN |
| 115191 | 2024-06-01 4:29 | 2024-06-01 9:04 | MySQL Server: Compiling | Verified (729 days) | S5 | 8.0.37 | Any | Any | optimize for net_write_buff |
| 115190 | 2024-05-31 22:12 | 2024-06-01 9:46 | MySQL Server: Optimizer | Verified (729 days) | S5 | 8.0.36 | Ubuntu (jammy) | Any | Failure to use index with subquery and tuples |
| 115161 | 2024-05-29 11:28 | 2024-05-29 12:18 | MySQL Server: Optimizer | Verified (732 days) | S2 | 8.4.0 | Any | Any | hint for join order doesn't work |
| 115156 | 2024-05-29 6:48 | 2024-05-29 7:49 | MySQL Server: Compiling | Verified (732 days) | S3 | mysql-trunk, 8.0 | Any | Any | Potential Nullptr Derefence in file `strings\ctype-ucs2.cc` |
| 115154 | 2024-05-29 5:40 | 2024-05-31 13:44 | MySQL Server: Charsets | Verified (730 days) | S2 | 8.0.37 | Any | Any | Dynamic Changes to the character_set_% are not honored duing the handshake |
| 115146 | 2024-05-28 2:38 | 2024-05-29 12:55 | MySQL Server: Optimizer | Verified (733 days) | S3 | 8.0 | Any | Any | Inconsistent Results in SQL Query |
| 115127 | 2024-05-26 5:51 | 2024-05-27 12:35 | MySQL Server: DML | Verified (734 days) | S3 | 8.0 | Any | Any | invalid result set with window function and generated rand value |
| 115123 | 2024-05-25 13:41 | 2024-05-25 15:49 | MySQL Server: DML | Verified (736 days) | S2 | 8.0 | Any | Any | Inconsistent Results with DATE_ADD and BETWEEN Clause |
| 115122 | 2024-05-25 11:17 | 2024-06-16 9:10 | MySQL Server: Optimizer | Verified (714 days) | S5 | 8.4 (Latest), 8.0.37 | Ubuntu (22.04 LTS) | ARM | Unneeded full table scan, although there is an index and condition |
| 115111 | 2024-05-24 7:33 | 2024-06-07 11:56 | MySQL Server: DML | Verified (737 days) | S3 | 8.4.0, 8.0.37 | Any | Any | last_insert_id evaluated twice if used nested |
| 115085 | 2024-05-22 20:39 | 2024-06-27 8:11 | MySQL Server: DML | Verified (738 days) | S2 | 8.0.34, 8.4.0 | Any (Docker Image) | x86 | INDEX using CAST (json_column) AS ARRAY drops rows containing empty array |
| 115075 | 2024-05-22 3:49 | 2024-05-22 7:00 | MySQL Server: Optimizer | Verified (739 days) | S3 | 8.0 | Any | Any | Unexpected subquery execution times |
| 115040 | 2024-05-16 12:09 | 2024-10-29 10:09 | MySQL Server: Optimizer | Verified (745 days) | S3 | 8.0 | Any | Any | Incorrect result from lateral join with group by month/monthname function inside |
| 115017 | 2024-05-15 14:44 | 2024-07-01 11:21 | MySQL Server: Optimizer | Verified (746 days) | S2 | 8.0 | Any | Any | Wrong row estimate for range scan |
| 114970 | 2024-05-13 3:42 | 2024-05-13 6:04 | MySQL Server: Optimizer | Verified (748 days) | S1 | 8.0.33 | Any | Any | prev_record_reads() use stale cardinality to calculate after plan enumeration |
| 114947 | 2024-05-09 23:54 | 2024-06-27 10:05 | MySQL Server: DML | Verified (751 days) | S3 | 8.0.37 | Any | Any | Right and Left functions do not work as documented within WHERE clauses |
| 114922 | 2024-05-08 9:25 | 2024-05-08 9:58 | MySQL Server: Optimizer | Verified (753 days) | S1 | 8.0.36 | Any | Any | Incorrect query results caused by different data conversion |
| 114917 | 2024-05-08 2:52 | 2024-05-23 12:10 | MySQL Server: Optimizer | Verified (748 days) | S3 | 8.0.35, 8.0.37, 8.4 | Any | Any | Incorrect query result |
| 114887 | 2024-05-05 9:20 | 2024-05-06 6:33 | MySQL Server: Optimizer | Verified (755 days) | S1 | 8.2.0, 8.0.37 | Any | Any | Incorrect Muti-table join with group by execution |
| 114886 | 2024-05-05 9:16 | 2024-05-06 6:30 | MySQL Server: Optimizer | Verified (755 days) | S1 | 8.2.0, 8.0.37 | Any | Any | Incorrect semi-join with group by execution |
| 114884 | 2024-05-05 9:03 | 2024-05-06 6:22 | MySQL Server: Optimizer | Verified (755 days) | S2 | 8.2.0, 8.0.37 | Any | Any | Incorrect inner join with group by execution |
| 114812 | 2024-04-29 9:55 | 2024-04-29 10:19 | MySQL Server: Optimizer | Verified (762 days) | S5 | 8.0.36,5.7.44 | Any | Any | in list values exceed eq_range_index_dive_limit cause index not used |
| 114807 | 2024-04-29 6:28 | 2024-04-30 3:06 | MySQL Server: DML | Verified (762 days) | S3 | 8.0.33 | Any | Any | Subquery returns more than 1 row |
| 114795 | 2024-04-26 10:05 | 2024-04-29 9:56 | MySQL Server: Optimizer | Verified (765 days) | S3 | 8.0 | Any | Any | Arithmetic overflow when calculating the length of used fields involving blob |
| 114794 | 2024-04-26 9:36 | 2024-04-26 12:23 | MySQL Server: Optimizer | Verified (765 days) | S3 | 8.0 | Any | Any | Incorrect query result |
| 114783 | 2024-04-25 11:32 | 2024-04-29 5:40 | MySQL Server: Optimizer | Verified (762 days) | S2 | mysql-8.0.35, 8.0.36 | Linux | Any | Backward scan partition table with multi-valued Indexes may lost some result. |
| 114775 | 2024-04-25 6:35 | 2024-04-25 12:38 | MySQL Server: DML | Verified (766 days) | S3 | 8.0.35, 8.0.36 | Ubuntu (AWS RDS) | x86 | Outer join condition filtering bug when using scalar subquery |
| 114762 | 2024-04-24 10:05 | 2024-04-25 14:23 | MySQL Server: Optimizer | Verified (767 days) | S3 | 8.0 | Any | Any | invalid result set with join lateral and group by on a generated field |
| 114751 | 2024-04-24 2:53 | 2024-04-24 7:24 | MySQL Server: Optimizer | Verified (767 days) | S1 | 8.0.36 | Any | Any | Incorrect query result |
| 114741 | 2024-04-23 9:43 | 2024-04-23 13:36 | MySQL Server: Optimizer | Verified (768 days) | S3 | 8.0 | Any | Any | Inconsistent query results caused by different execution of subqueries |
| 114719 | 2024-04-21 14:31 | 2024-04-22 7:46 | MySQL Server: Optimizer | Verified (769 days) | S1 | 8.0.36 | Any | Any | Incorrect results caused by different access types for an index |
| 114718 | 2024-04-21 12:09 | 2024-04-22 7:45 | MySQL Server: DML | Verified (769 days) | S1 | 8.0.36 | Any | Any | Incorrect query results |
| 114714 | 2024-04-20 3:54 | 2025-05-09 12:41 | MySQL Server: Optimizer | Verified (769 days) | S3 | 8.0.33 | Any | Any | Duplicate subquery explain plan output when explain format is tree |
| 114682 | 2024-04-18 11:57 | 2024-04-18 13:49 | MySQL Server: Optimizer | Verified (773 days) | S3 | 8.0 | Any | Any | Duplicate key error when executing query |
| 114599 | 2024-04-09 16:13 | 2024-12-04 10:41 | MySQL Server: Compiling | Verified (543 days) | S3 | 8.0 | Any | Any | Contribution: Fix: month\'s name Indonesia |
| 114581 | 2024-04-08 11:24 | 2024-04-08 12:37 | MySQL Server: Optimizer | Verified (783 days) | S2 | 8.0.36 | Any | Any | Constant-Folding optimization negative constant truncate gives wrong operator |
| 114568 | 2024-04-07 13:43 | 2024-04-08 7:28 | MySQL Server: Optimizer | Verified (783 days) | S1 | 8.0.36 | Any | Any | Different join orders cause inconsistent results |
| 114559 | 2024-04-05 12:12 | 2024-04-08 9:26 | MySQL Server: Optimizer | Verified (786 days) | S3 | 8.0 | Any | Any | Unexpected Results by the hint SUBQUERY(MATERIALIZATION) |
| 114539 | 2024-04-03 7:36 | 2024-04-03 8:14 | MySQL Server: Optimizer | Verified (788 days) | S1 | 8.0.36 | Any | Any | Unexpected Results by the hint NO_INDEX |
| 114534 | 2024-04-03 4:22 | 2024-04-03 8:22 | MySQL Server: DML | Verified (788 days) | S3 | 8.0.36 | Any | Any | Inconsistent result with index and symbol '̏ |
| 114524 | 2024-04-01 12:36 | 2025-06-16 11:58 | MySQL Server: Optimizer | Verified (789 days) | S3 | 8.3.0 | Any | Any | INSERT with JSON column error |
| 114512 | 2024-03-29 9:35 | 2024-06-17 9:54 | MySQL Server: Optimizer | Verified (713 days) | S5 | 8.3.0, 8.0.36 | Any | Any | MySQL 8: Order by with hash join incredibly slow |
| 114510 | 2024-03-29 6:42 | 2024-03-29 7:29 | MySQL Server: Optimizer | Verified (793 days) | S2 | 8.0.36 | Linux | x86 | Inconsistent results after dropping index on join column |
| 114462 | 2024-03-23 10:30 | 2024-04-04 9:20 | MySQL Server: DML | Verified (797 days) | S3 | 8.3.0, 8.0.36 | Ubuntu (Ubuntu 22.04) | x86 (x86_64) | Strange SQL_BUFFER_RESULT error |
| 114456 | 2024-03-22 14:54 | 2025-03-17 14:46 | MySQL Server: Compiling | Verified (443 days) | S3 | Any | Any | Contribution: Fix OpenSSL linking when only static libs are available | |
| 114418 | 2024-03-19 23:20 | 2024-03-20 7:25 | MySQL Server: DML | Verified (802 days) | S2 | 8.0.36 | Any | Any | Flaw in SOUNDEX implementation causing incorrect results |
| 114384 | 2024-03-17 14:33 | 2024-03-18 6:57 | MySQL Server: DML | Verified (804 days) | S3 | 8.0.15,8.0.35, 8.0.36 | Any | Any | Incorrect query result may caused by LOG |
| 114383 | 2024-03-17 14:11 | 2024-03-20 11:19 | MySQL Server: DML | Verified (804 days) | S2 | 8.0.23,8.0.35 | Any | Any | Incorrect query result may caused by DATE and window function |
| 114382 | 2024-03-17 13:58 | 2024-03-20 11:20 | MySQL Server: DML | Verified (804 days) | S2 | 8.0.11, 8.0.35, 8.0.36 | Any | Any | Incorrect query result may caused by LOW_PRIORITY |
| 114381 | 2024-03-17 13:47 | 2024-03-20 11:21 | MySQL Server: DML | Verified (804 days) | S3 | 8.0.19,8.0.35 | Any | Any | Incorrect query result may caused by EXISTS and TIMEDIFF |
| 114380 | 2024-03-17 13:19 | 2024-03-20 11:21 | MySQL Server: DML | Verified (804 days) | S3 | 8.0.13, 8.0.35, 8.0.36 | Any | Any | Incorrect query result may caused by TIMESTAMP |
| 114379 | 2024-03-17 13:01 | 2024-03-20 11:22 | MySQL Server: DML | Verified (804 days) | S3 | 8.0.27, 8.0.35, 8.0.21 | Any | Any | Incorrect query result caused by index and optimizer |
| 114378 | 2024-03-17 12:44 | 2024-04-23 16:37 | MySQL Server: DML | Verified (804 days) | S3 | 8.0, 8.0.35 | Any | Any | Incorrect query result caused by CONVERT_TZ |
| 114373 | 2024-03-15 16:32 | 2024-03-20 11:03 | MySQL Server: Data Types | Verified (802 days) | S3 | 8.0 | Any | Any | Incorrect result after transformation from "IN (SELECT)" to "materialization" |
| 114338 | 2024-03-13 16:41 | 2024-03-19 11:10 | MySQL Server: Prepared statements | Verified (808 days) | S3 | 8.0 | Any | Any | Client might receive incorrect data in ps-protocol |
| 114333 | 2024-03-13 10:50 | 2024-03-13 16:33 | MySQL Server: DML | Verified (809 days) | S3 | 8.0 | Any | Any | Lead/lag window functions returning BLOB instead of VARCHAR |
| 114312 | 2024-03-12 6:30 | 2024-03-19 2:26 | MySQL Server: DML | Verified (803 days) | S3 | 8.0 | Any | Any | Item_ref::used_tables wrong when ref to a rollup constant |
| 114301 | 2024-03-11 16:40 | 2024-03-12 16:23 | MySQL Server: Optimizer | Verified (810 days) | S3 | 8.0 | Any | Any | Incorrect result with IS NULL predicate in join condition |
| 114291 | 2024-03-10 7:20 | 2024-06-27 10:05 | MySQL Server: GIS | Verified (812 days) | S3 | 8.2.0, 8.0.36 | Any | Any | ST_Overlap gives an incorrect answer. |
| 114282 | 2024-03-08 13:10 | 2024-03-08 13:13 | MySQL Server: DML | Verified (814 days) | S2 | 8.35, 8.0.36 | Any | Any | Inconsistent result may caused by group by NULL |
| 114270 | 2024-03-07 23:23 | 2024-03-08 4:11 | MySQL Server: Compiling | Verified (814 days) | S3 | 8.0 | Any | Any | Contribution: Fix operator name keywords causing obscure errors on -fno-ope ... |
| 114237 | 2024-03-06 6:57 | 2024-03-06 8:30 | MySQL Server: Optimizer | Verified (816 days) | S5 | 8.2.0, 8.3.0 | Any | Any | Unexpected Cardinality by Index |
| 114218 | 2024-03-05 4:50 | 2024-03-05 7:01 | MySQL Server: DML | Verified (817 days) | S2 | 8.2.0, 8.3.0, 8.0.36 | Any | Any | Unexpected Results by MEMORY ENGINE |
| 114217 | 2024-03-05 4:48 | 2024-03-05 7:01 | MySQL Server: DML | Verified (817 days) | S2 | 8.2.0, 8.3.0, 8.0.36 | Any | Any | Unexpected Results by Minus Sign |
| 114204 | 2024-03-04 8:43 | 2024-03-04 8:58 | MySQL Server: DML | Verified (818 days) | S2 | 8.2.0, 8.3.0 | Any | Any | Unexpected Results by COALESCE |
| 114195 | 2024-03-02 15:24 | 2024-03-04 6:56 | MySQL Server: Charsets | Verified (818 days) | S3 | 8.0.36 | Any | Any | mysql doesn't show what collation was used sometimes |
| 114149 | 2024-02-28 3:20 | 2024-02-28 5:54 | MySQL Server: DML | Verified (823 days) | S3 | 8.0+ | Linux | Any | Incorrect query result caused by where optimization |
| 114092 | 2024-02-22 23:40 | 2024-02-26 14:58 | MySQL Server: Optimizer | Verified (827 days) | S5 | Ver 8.0.36-0 | Ubuntu (ubuntu 22.04.1) | x86 (Linux on x86_64 ((Ubuntu))) | WHERE statement on an indexed decimal column hangs |
| 114086 | 2024-02-21 19:41 | 2025-01-29 11:22 | MySQL Server: Charsets | Verified (825 days) | S3 | 8.0 | Any | Any | Item_singlerow_subselect::store may lead to memory corruption |
| 114027 | 2024-02-17 19:34 | 2024-02-19 6:29 | MySQL Server: Optimizer | Verified (832 days) | S3 | 8.0.36 & 8.3.0 | Windows (10 & 11) | ARM (x64) | Plans for inner hash join show that wrong table is hashed |
| 113992 | 2024-02-14 14:11 | 2025-02-01 11:59 | MySQL Server: Compiling | Verified (837 days) | S3 | 8.0 | Any | Any | Contribution: Improved the way my_plugin_log_message() handles plugin_ptr a ... |
| 113949 | 2024-02-09 19:55 | 2024-02-12 9:16 | MySQL Server: Parser | Verified (839 days) | S3 | 8.3.0, 8.0.36 | Any | Any | Backslash escaping inconsistency in LIKE operator |
| 113892 | 2024-02-05 10:39 | 2024-02-05 14:13 | MySQL Server: Optimizer | Verified (846 days) | S3 | 8.0 | Any | Any | FORCE INDEX reports wrong number of rows |
| 113888 | 2024-02-04 3:38 | 2025-02-01 11:58 | MySQL Server: GIS | Verified (847 days) | S2 | 8.0 | Linux | x86 | st_contains function result is obviously wrong |
| 113843 | 2024-02-01 2:49 | 2024-02-01 8:09 | MySQL Server: Prepared statements | Verified (850 days) | S3 | 8.0.32, 8.0.36 | Any | Any | prepared json query can not use index |
| 113800 | 2024-01-30 5:30 | 2024-01-31 8:28 | MySQL Server: DML | Verified (851 days) | S5 | 8.0.22, 8.0.36, 8.0.11 | Linux | x86 | Performance degradation of Blob operations comparing with MySQL 5.7 |
| 113768 | 2024-01-26 2:40 | 2024-01-26 8:53 | MySQL Server: DML | Verified (856 days) | S3 | 8.0.35 | Linux | Any | return error with cast |
| 113762 | 2024-01-25 17:05 | 2024-01-26 7:05 | MySQL Server: DML | Verified (856 days) | S3 | 8.0.36 | Any | Any | Unexpected results when using ASIN function with NULLIF |
| 113718 | 2024-01-23 4:42 | 2024-01-23 7:22 | MySQL Server: Optimizer | Verified (859 days) | S2 | 8.0.35, 8.0.36, 8.3.0 | Any | Any | left join + semijoin + materialization finds false matches |
| 113649 | 2024-01-16 10:17 | 2024-01-16 11:03 | MySQL Server: DML | Verified (866 days) | S3 | 8.0.31, 8.0.35 | Any | Any | the result of format function truncated when using cursor |
| 113641 | 2024-01-15 5:42 | 2024-01-15 5:50 | MySQL Server: JSON | Verified (867 days) | S2 | 8.0.28 | Any | Any | Multi-valued index can lead to incorrect result with implicit conversion |
| 113587 | 2024-01-09 3:31 | 2024-02-27 12:25 | MySQL Server: Optimizer | Verified (867 days) | S2 | 8.0 | Any | Any | SELECT DISTINCT makes ORDER BY ... DESC sort data to ascending |
| 113586 | 2024-01-09 3:13 | 2024-01-09 12:27 | MySQL Server: Optimizer | Verified (873 days) | S3 | 8.0 | Any | Any | IFNULL Incorrect query result |
| 113578 | 2024-01-08 13:06 | 2024-05-21 10:11 | MySQL Server: DML | Verified (872 days) | S3 | 5.7.44, 8.0.35 | Any | Any | AVG calculation bug |
| 113557 | 2024-01-04 15:29 | 2024-01-04 15:40 | MySQL Server: JSON | Verified (878 days) | S2 | 8.0.35 | Any | Any | Wrong query result on composite multi-valued index + empty array value |
| 113551 | 2024-01-04 10:04 | 2024-01-10 11:21 | MySQL Server: Optimizer | Verified (872 days) | S3 | 8.2.0 | Linux (mysql docker image 8.2.0) | Any | Discrepancy in MySQL 8.2.0 Documentation Regarding Subquery Scoping Rules |
| 113541 | 2024-01-03 9:17 | 2024-01-03 10:07 | MySQL Server: DML | Verified (879 days) | S3 | 8.2.0 | Any | Any | Regexp validation failure on empty table |
| 113537 | 2024-01-02 16:00 | 2024-01-04 10:44 | MySQL Server: Charsets | Verified (878 days) | S3 | 8.0.32 | Any | Any | False match of multibyte chars when checking existence of a control character |
| 113534 | 2024-01-02 8:27 | 2024-01-05 2:27 | MySQL Server: Optimizer | Verified (877 days) | S1 | 8.0.35 | Any | Any | table join return Unexpected result when drived table using include join index |
| 113513 | 2023-12-26 12:12 | 2023-12-27 5:20 | MySQL Server: Optimizer | Verified (886 days) | S3 | 8.0.33 | Any | Any | Join reordering regression and inconsistent behavior for SQL involving LEFT JOIN |
| 113462 | 2023-12-19 16:05 | 2023-12-20 15:06 | MySQL Server: Optimizer | Verified (893 days) | S3 | 8.0 | Any | Any | Incorrect result |
| 113446 | 2023-12-18 2:32 | 2024-10-22 4:28 | MySQL Server: DML | Verified (895 days) | S3 | 8.0.33 | Any | Any | Query with DISTINCT and ORDER BY on BIT data type returns wrong result |
| 113444 | 2023-12-16 16:23 | 2023-12-17 13:28 | MySQL Server: Compiling | Verified (896 days) | S3 | 8.2.0 | CentOS | x86 | Contribution by Tencent:-DBISON_EXECUTABLE may cause compile error |
| 113429 | 2023-12-14 21:13 | 2023-12-18 13:33 | MySQL Server: DML | Verified (895 days) | S5 | 8.0 | Any | Any | Function call duplicated in CTE |
| 113426 | 2023-12-14 17:21 | 2023-12-15 7:35 | MySQL Server: Compiling | Verified (898 days) | S3 | mysql-trunk | Oracle Linux | x86 | using -DWITH_INNODB_EXTRA_DEBUG results in compilation error |
| 113415 | 2023-12-14 6:27 | 2023-12-14 8:51 | MySQL Server: DML | Verified (899 days) | S3 | 8.0, 8.0.35 | Any | Any | Unknown column, but can get query result in CTE. |
| 113384 | 2023-12-09 8:05 | 2023-12-11 11:42 | MySQL Server: Data Types | Verified (902 days) | S3 | 8.0 | Any | Any | Queried with partitions,returned result is error |
| 113366 | 2023-12-08 1:39 | 2023-12-08 8:06 | MySQL Server: DML | Verified (905 days) | S3 | 8.0.35 | Any | Any | Incorrect query results involving the date type. |
| 113358 | 2023-12-07 7:09 | 2023-12-07 8:42 | MySQL Server: Optimizer | Verified (906 days) | S3 | 8.0, 8.0.35 | Any | Any | Wrong functional dependency in ONLY_FULL_GROUP_BY mode |
| 113320 | 2023-12-04 9:00 | 2023-12-04 11:30 | MySQL Server: Optimizer | Verified (909 days) | S2 | 8.0 | Any | Any (DarwinMatt.local 22.5.0 Darwin Kernel Version 22.5.0: root:xnu-8796.121.2~5/RELEASE_ARM64_T6020 arm6) | SELECT DISTINCT .. ORDER BY query yields wrong sort order |
| 113317 | 2023-12-04 5:29 | 2024-10-14 15:31 | MySQL Server: DML | Verified (909 days) | S1 | 8.0.35, 8.1.0, 8.2.0 | Any | Any | Unexpected Result by IF |
| 113316 | 2023-12-04 3:32 | 2023-12-04 7:21 | MySQL Server: Optimizer | Verified (909 days) | S3 | 8.0.35, 8.1.0, 8.2.0 | Any | Any | When the bit type has an index, the query result is incorrect. |
| 113303 | 2023-12-01 7:29 | 2023-12-05 4:54 | MySQL Server: Optimizer | Verified (912 days) | S5 | 8.0.35 | Any | Any | Explain plan takes forever when there are more joins |
| 113302 | 2023-12-01 7:29 | 2023-12-01 7:41 | MySQL Server: DML | Verified (912 days) | S1 | 8.2.0, 8.0.35 | Any | Any | Unexpected Result for an Index |
| 113298 | 2023-12-01 4:41 | 2023-12-01 4:55 | MySQL Server: Optimizer | Verified (912 days) | S3 | 8.0.33, 8.1.0, 8.0.35 | Any | Any | Unexpected Results when Using IN for Floating-Point |
| 113288 | 2023-11-30 6:58 | 2023-12-01 11:37 | MySQL Server: Optimizer | Verified (913 days) | S5 | 8.0.33 | Any | Any | Explain plan shows dynamic range, but bug causes no chance to use for LEFT JOIN |
| 113270 | 2023-11-29 0:18 | 2023-11-29 10:34 | MySQL Server: Compiling | Verified (914 days) | S3 | 8.0.35 | Any | Any | Unable to compile 8.0.35 with DISABLE_PSI_THREAD |
| 113211 | 2023-11-24 12:14 | 2023-11-24 12:34 | MySQL Server: Optimizer | Verified (919 days) | S2 | 8.0.35, 8.1.0, 8.2.0 | Any | Any | The latest version 8.0 returns abnormal results for complex queries |
| 113205 | 2023-11-24 3:06 | 2023-11-24 6:01 | MySQL Server: GIS | Verified (919 days) | S3 | 8.2.0, 8.0.35 | Any | Any | After swapping the X and Y coordinates, ST_Crosses gives the incorrect answer. |
| 113180 | 2023-11-22 10:12 | 2023-11-23 8:46 | MySQL Server: DML | Verified (921 days) | S3 | 8.0.33, 8.1.0, 8.0.35 | Any | Any | Unexpected Results when Using Math Function SIN |
| 113167 | 2023-11-21 14:17 | 2023-11-22 7:24 | MySQL Server: GIS | Verified (921 days) | S2 | 8.2.0, 8.0.35 | Any | Any | After creating the spatial index, ST_Disjoint gives the incorrect answer |
| 113154 | 2023-11-20 21:57 | 2023-11-21 6:25 | MySQL Server: DML | Verified (922 days) | S2 | 8.2.0, 8.1.0, 8.0.35 | Linux | Any | Join using ROW_NUMBER() returns incorrect records |
| 113135 | 2023-11-20 3:03 | 2023-11-20 15:34 | MySQL Server: DML | Verified (923 days) | S3 | 8.0 | Any | Any | DISTINCT JOIN ORDER BY statements ignore ORDER BY when tmp_table_size is small |
| 113113 | 2023-11-16 20:26 | 2025-10-28 10:13 | MySQL Server: Compiling | Verified (215 days) | S3 | 8.0.41 | MacOS | Any | Build failure with Homebrew LLVM 14-19 on macOS |
| 113060 | 2023-11-13 10:23 | 2025-03-16 20:45 | MySQL Server: DML | Verified (930 days) | S3 | 8.0 | Any | Any | The result of avg(distinct xx)is different between from primary and secondary |
| 113059 | 2023-11-13 8:29 | 2023-11-13 9:51 | MySQL Server: Optimizer | Verified (930 days) | S2 | 8.2.0 | Any | Any | Inconsistent results when using DUPSWEEDOUT |
| 113049 | 2023-11-10 15:28 | 2024-01-17 16:27 | MySQL Server: JSON | Verified (865 days) | S2 | 8.0.35, 8.2.0 | Any | Any | MTR test json.array_index fails with a result difference |
| 113045 | 2023-11-10 14:54 | 2024-05-24 10:12 | MySQL Server: Compiling | Verified (737 days) | S3 | 8.0 | Linux | Any (x86_64,arm64) | Build failure with Protobuf 24.2 in Linux |
| 113015 | 2023-11-09 3:25 | 2023-11-14 7:35 | MySQL Server: DML | Verified (934 days) | S3 | 8.0.35 | Any | Any | REGEXP curly brackets without escape character works on 5.7 but not in 8.0 |
| 112985 | 2023-11-07 8:33 | 2023-11-08 10:54 | MySQL Server: Optimizer | Verified (936 days) | S3 | 8.0, 8.1, 8.2 | Any | Any | Inconsistent results when switching hash join optimization |
| 112914 | 2023-11-01 9:43 | 2023-11-01 15:02 | MySQL Server: Optimizer | Verified (942 days) | S3 | 8.0 | Any | Any | different result related to zerofill and greatest() |
| 112912 | 2023-11-01 8:45 | 2023-11-01 14:47 | MySQL Server: Optimizer | Verified (942 days) | S3 | 8.0 | Any | Any | Parsing a string To BIT type got a wrong result |
| 112911 | 2023-11-01 8:21 | 2023-11-01 8:56 | MySQL Server: Optimizer | Verified (942 days) | S2 | 8.1.0, 8.0.35 | Any | Any | Inconsistent results when using PRIMARY and DUPSWEEDOUT |
| 112910 | 2023-11-01 7:20 | 2023-11-01 7:31 | MySQL Server: Optimizer | Verified (942 days) | S2 | 8.1.0, 8.0.35 | Any | Any | Incorrect results when add an uncorrelated row |
| 112902 | 2023-10-31 14:39 | 2024-06-10 11:08 | MySQL Server: Optimizer | Verified (825 days) | S5 | 8.0.31, 8.0.35 | Linux (n.a.) | x86 (x86_64) | Optimizer in MySQL 8 is significantly slower on dependent subqueries than 5.7 |
| 112853 | 2023-10-27 8:32 | 2023-12-18 2:17 | MySQL Server: DML | Verified (895 days) | S3 | 8.0 | Any | Any | Wrong functional dependency in ONLY_FULL_GROUP_BY mode |
| 112852 | 2023-10-27 7:42 | 2023-11-06 11:25 | MySQL Server: DML | Verified (937 days) | S3 | 8.0 | Linux | x86 | insert and insert onduplicate are executed concurrently, data update error |
| 112848 | 2023-10-27 2:28 | 2023-10-27 11:37 | MySQL Server: Data Types | Verified (947 days) | S3 | 8.0 | Any | Any | Item_func_set_user_var::get_string_value may have potion risk of memory access |
| 112826 | 2023-10-25 7:47 | 2023-10-25 8:27 | MySQL Server: DML | Verified (949 days) | S3 | 8.1.0, 8.0.34 | Ubuntu (22.04) | x86 (x86_64) | Decimal query with wrong result |
| 112816 | 2023-10-24 16:15 | 2023-12-13 12:00 | MySQL Server: Optimizer | Verified (940 days) | S2 | 8.0, 8.1 | Any | Any | Inconsistent results when JOINed in different order |
| 112802 | 2023-10-23 8:23 | 2023-10-27 9:46 | MySQL Server: Optimizer | Verified (951 days) | S3 | 8.1.0, 8.0.34 | Any | Any | Inconsistent results when using INDEX |
| 112729 | 2023-10-15 11:20 | 2023-10-16 6:13 | MySQL Server: Parser | Verified (958 days) | S3 | 8.1.0 | Any | Any | Two single quotes escaping inconsistency in index expression |
| 112728 | 2023-10-15 9:51 | 2023-10-18 15:43 | MySQL Server: Optimizer | Verified (956 days) | S3 | 8.0 | Any | Any | MySQL optimizer generated an incorrect execution plan |
| 112704 | 2023-10-12 12:19 | 2026-04-28 7:32 | MySQL Server: Optimizer | Verified (178 days) | S2 | 8.0, 8.4.7 | Any | Any | CTE query got internal table doesn't exist error with small tmp_table_size |
| 112703 | 2023-10-12 12:13 | 2025-08-25 7:23 | MySQL Server: Prepared statements | Verified (962 days) | S3 | Any | Any | prepare statment has no warning comping to not prepare statment. | |
| 112647 | 2023-10-06 9:28 | 2023-10-09 6:56 | MySQL Server: Compiling | Verified (965 days) | S3 | 8.0.34,8.1.0 | Any | Any | clang-format 17 errors out on .clang-format |
| 112642 | 2023-10-05 18:40 | 2023-10-09 10:17 | MySQL Server: Optimizer | Verified (967 days) | S3 | 8.0 | Any | Any | Wrong results when MRR is activated |
| 112597 | 2023-10-03 12:14 | 2023-10-05 14:13 | MySQL Server: Optimizer | Verified (969 days) | S5 | 8.0 | Any | Any | Slow performance |
| 112579 | 2023-09-30 8:37 | 2023-10-02 9:16 | MySQL Server: DML | Verified (972 days) | S2 | 8.0.14 - 8.0.34 | Any | Any | Inconsistent results of SELECT with <=> and NULLIF |
| 112572 | 2023-09-29 9:44 | 2023-09-29 12:27 | MySQL Server: Optimizer | Verified (975 days) | S3 | 8.0 | Any | Any | Inconsistent results of SELECT statement with HEX, REVERSE, and RPAD functions |
| 112543 | 2023-09-27 19:23 | 2023-10-03 12:05 | MySQL Server: Optimizer | Verified (971 days) | S3 | 8.0 | Any | Any | Query rewrite plugin can't be used to parse and change reserved words |
| 112527 | 2023-09-26 14:46 | 2023-09-27 7:25 | MySQL Server: DML | Verified (977 days) | S2 | 8.0.11, 8.0.34, 8.1.0 | Any | Any | Inconsistent results caused by REPEAT function |
| 112524 | 2023-09-26 13:32 | 2023-09-27 7:52 | MySQL Server: DML | Verified (977 days) | S2 | 5.7, 8.0.0, 8.0.34 | Any | Any | Inconsistent results of UNIX_TIMESTAMP with NULLIF and COALESCE |
| 112451 | 2023-09-25 6:35 | 2023-09-25 7:37 | MySQL Server: Optimizer | Verified (979 days) | S3 | 8.0,8.1 | Any | Any | Incorrect result if there are non-deterministic expressions in in-subquery |
| 112450 | 2023-09-25 6:25 | 2023-09-25 7:45 | MySQL Server: Optimizer | Verified (979 days) | S3 | 8.0.28 | Any | Any | Incorrect result |
| 112422 | 2023-09-22 1:54 | 2023-09-25 11:49 | MySQL Server: Optimizer | Verified (979 days) | S3 | 8.0 | Any | Any | The outer select group_concat(NULL) return an empty string |
| 112394 | 2023-09-20 13:13 | 2023-09-21 12:16 | MySQL Server: Optimizer | Verified (983 days) | S3 | 8.0 | Any | Any | Inconsistent results caused by subqueries in FROM and EXISTS |
| 112377 | 2023-09-18 23:01 | 2023-09-19 12:24 | MySQL Server: Optimizer | Verified (985 days) | S3 | 8.0 | Any | Any | Assert in AccessPath::index_merge() |
| 112346 | 2023-09-14 8:21 | 2023-10-11 7:24 | MySQL Server: JSON | Verified (963 days) | S5 | 8.0.34 | Any | Any | MEMBER_OF with multi-valued index on JSON not used in 99% of situations. |
| 112345 | 2023-09-14 7:53 | 2025-05-13 3:07 | MySQL Server: Optimizer | Verified (383 days) | S2 | 8.0.34 | Any | Any | Contribute by tencent: Repeated subquery plans were printed in format=tree. |
| 112293 | 2023-09-07 14:04 | 2023-09-08 6:54 | MySQL Server: DML | Verified (996 days) | S3 | 8.0, 8.0.34, 5.7.43 | Any | Any | Wrong result if non-breaking space is contained in varchar |
| 112280 | 2023-09-06 20:38 | 2023-09-07 4:27 | MySQL Server: Optimizer | Verified (997 days) | S3 | 8.0.34 | Any | Any | Incorrect costing of group by loose index scans |
| 112269 | 2023-09-06 2:51 | 2023-09-06 4:52 | MySQL Server: Optimizer | Verified (998 days) | S2 | 8.1.0, 8.0.34 | Any | Any | Unexpected Results by the hint JOIN_ORDER |
| 112264 | 2023-09-05 11:47 | 2023-09-05 12:15 | MySQL Server: Optimizer | Verified (999 days) | S2 | 8.1.0 | Any | Any | Unexpected Result by block_nested_loop |
| 112259 | 2023-09-05 9:44 | 2023-09-05 10:21 | MySQL Server: Compiling | Verified (999 days) | S3 | 8.0.33 | Any | Any | Assert when debug_sync_timeout is 0 |
| 112243 | 2023-09-04 4:54 | 2023-09-21 7:13 | MySQL Server: Optimizer | Verified (1000 days) | S3 | 8.0.34 | Any | Any | Unexpected Result by subquery_to_derived |
| 112242 | 2023-09-04 4:40 | 2023-09-04 8:34 | MySQL Server: Optimizer | Verified (1000 days) | S2 | 8.1.0, 8.0.34 | Any | Any | Unexpected Results by use_invisible_indexes |
| 112238 | 2023-09-01 16:08 | 2023-09-11 11:28 | MySQL Server: DML | Verified (1000 days) | S2 | 5.5, 5.6, 5.7.43, 8.0.34 | Any | Any | Inconsistent results caused by FIELD() |
| 112212 | 2023-08-29 16:01 | 2023-08-30 7:42 | MySQL Server: Optimizer | Verified (1005 days) | S3 | 8.0.34 | Any | Any | Subquery to derived result mismatch(HASH JOIN/BNL JOIN result mismatch) |
| 112198 | 2023-08-28 8:21 | 2024-03-05 6:06 | MySQL Server: Optimizer | Verified (1007 days) | S1 | 8.0, 8.0.34 | Any | Any | Incorrect multiple equality optimization causes performance degradation |
| 112194 | 2023-08-28 5:31 | 2023-09-06 9:03 | MySQL Server: DML | Verified (998 days) | S3 | 8.0.34 | Red Hat | Any | Incorrect result when using INNER JOIN with SELECT FROM VIEW together with OR co |
| 112192 | 2023-08-28 2:55 | 2023-08-30 11:05 | MySQL Server: Optimizer | Verified (1005 days) | S5 | 8.0.28 | Any | Any | In MySQL 8.0, one queries need 1000 times more data than MySQL 5.7 |
| 112191 | 2023-08-28 2:52 | 2023-08-29 9:45 | MySQL Server: Compiling | Verified (1006 days) | S3 | 8.0.31 | Any | Any | When we compile MySQL 8.0 with DEBUG, we have some warning of memory leak |
| 112175 | 2023-08-24 13:32 | 2025-07-24 7:07 | MySQL Server: Compiling | Verified (311 days) | S3 | 8.0 | Any | Any | Contribution: [performance optimization] |
| 112169 | 2023-08-23 15:41 | 2023-08-24 13:51 | MySQL Server: Optimizer | Verified (1011 days) | S3 | 5.7 | Any | Any | Using LOWER in HAVING clause falsifies result of GROUP_CONCAT |
| 112149 | 2023-08-23 4:09 | 2023-08-23 8:15 | MySQL Server: DML | Verified (1012 days) | S2 | 8.0.34, 5.7.43, 5.6, 5.5 | Any | Any | Inconsistent results caused by SPACE() function and ''||'' operations |
| 112147 | 2023-08-23 2:58 | 2023-08-24 7:31 | MySQL Server: JSON | Verified (1012 days) | S3 | 8.0.34 | Any | Any | Use/Ignore Mutil-value index for MEMBER OF function has differnet result |
| 112124 | 2023-08-21 15:10 | 2023-08-22 13:00 | MySQL Server: DML | Verified (1013 days) | S3 | 8.0 | Any | Any | Sometimes , ROW_COUNT() return wrong answer, which cause by index. |
| 112105 | 2023-08-18 2:51 | 2023-08-18 9:21 | MySQL Server: Prepared statements | Verified (1017 days) | S3 | 8.1.0, 8.0.34 | Ubuntu (22.04) | x86 (x86_64) | Create table from prepared statement issues |
| 112053 | 2023-08-12 19:55 | 2023-08-21 12:36 | MySQL Server: JSON | Verified (1019 days) | S3 | 8.0 | Any | Any | COALESCE a null value with a JSON object returns hex string |
| 112037 | 2023-08-11 3:45 | 2023-08-25 6:44 | MySQL Server: Optimizer | Verified (1024 days) | S3 | 8.0.32, 8.0.34 | Any | Any | Contribute by tencent: explain analyze show never executed for materialize |
| 112022 | 2023-08-10 1:56 | 2023-08-10 7:38 | MySQL Server: Compiling | Verified (1025 days) | S3 | 8.0.34 | CentOS (CentOS Linux 7) | x86 | Compiling with -DWITH_DEBUG=1 and using C++17 resulted in a failure. |
| 112011 | 2023-08-09 12:06 | 2023-08-17 12:21 | MySQL Server: Prepared statements | Verified (1025 days) | S3 | 8.0 | Any | Any | RESOURCE GROUP hint fails when used within a prepared statement |
| 112008 | 2023-08-09 10:41 | 2023-08-09 11:53 | MySQL Server: Compiling | Verified (1026 days) | S3 | 8.0.34, 8.1.0 | Any | Any | Unused macro DBUG_EVALUATE |
| 111991 | 2023-08-08 3:25 | 2023-08-10 5:53 | MySQL Server: Optimizer | Verified (1025 days) | S2 | 8.0.32,8.1.0 | Any | Any | index merge sometimes return incorrect result |
| 111952 | 2023-08-02 19:50 | 2026-03-02 20:31 | MySQL Server: Optimizer | Verified (90 days) | S2 | 8.0, 8.0.34, 8.0.45, 5.7.43, 8.1.0, 8.4, 8.4.8 | Any | Any | Row constructor inequality comparison on Primary Key results in full table scan. |
| 111921 | 2023-07-31 7:57 | 2023-08-11 12:14 | MySQL Server: Prepared statements | Verified (1034 days) | S3 | 8.0 | Any | Any | Reusing prepared statement for different data types, different outcomes are obse |
| 111918 | 2023-07-30 6:12 | 2023-07-31 6:33 | MySQL Server: Optimizer | Verified (1035 days) | S3 | 8.1.0, 8.0.34, 5.7.43 | Ubuntu (22.04) | x86 (x86_64) | Auto increment column query wrong result |
| 111917 | 2023-07-30 5:35 | 2023-07-31 6:31 | MySQL Server: Optimizer | Verified (1035 days) | S3 | 8.1.0, 8.0.34 | Ubuntu (22.04) | x86 (x86_64) | derived condition pushdown query with wrong result |
| 111892 | 2023-07-26 6:52 | 2023-11-13 10:14 | MySQL Server: Parser | Verified (1039 days) | S3 | 8.1 | Any | Any | Two single quotes escaping inconsistency |
| 111852 | 2023-07-23 12:46 | 2023-07-27 1:15 | MySQL Server: Optimizer | Verified (1042 days) | S3 | 8.0.30, 8.0.34 | Any | Any | An incorrect number of records is returned |
| 111851 | 2023-07-22 22:59 | 2023-07-26 6:55 | MySQL Server: GIS | Verified (1040 days) | S2 | 8.0.32, 8.0.34, 5.7.43 | Any (Linux & Mac) | Any (x86 & ARM) | Spatial index not used for join when field is used in MBRIntersects call |
| 111850 | 2023-07-21 23:40 | 2023-07-24 8:19 | MySQL Server: Compiling | Verified (1044 days) | S3 | 8.0 | Any | Any | Contribution: Architecture-agnostic fix for crashes caused by cache coheren ... |
| 111838 | 2023-07-21 10:51 | 2023-07-21 11:31 | MySQL Server: JSON | Verified (1045 days) | S3 | 8.10 | Any | Any | Evaluate JSON column default on table/column creation |
| 111739 | 2023-07-13 4:50 | 2023-07-13 9:32 | MySQL Server: DML | Verified (1053 days) | S3 | 8.0.33 | Any | Any | The query results are inconsistent. |
| 111728 | 2023-07-12 8:08 | 2023-07-12 8:42 | MySQL Server: Optimizer | Verified (1054 days) | S2 | 8.0.28, 8.0.33 | Any | Any | Incorrect result |
| 111706 | 2023-07-10 8:24 | 2025-03-17 9:33 | MySQL Server: Optimizer | Verified (1056 days) | S3 | 8.0.28, 8.0.33 | Any | Any | Incorrect result |
| 111700 | 2023-07-09 7:31 | 2023-07-12 5:55 | MySQL Server: Optimizer | Verified (1054 days) | S3 | 8.0.32, 8.0.33 | Any | Any | LIMIT values are not adequately handled in EXPLAIN. |
| 111699 | 2023-07-09 3:46 | 2023-07-10 5:51 | MySQL Server: Optimizer | Verified (1056 days) | S3 | 8.0.28, 8.0.33 | Any | Any | Incorrect results |
| 111681 | 2023-07-06 13:47 | 2023-10-23 10:29 | MySQL Server: Optimizer | Verified (1054 days) | S3 | 8.0 | Linux | Any | EXISTS query results in duplicate rows |
| 111669 | 2023-07-06 0:47 | 2023-07-12 13:04 | MySQL Server: Optimizer | Verified (1054 days) | S5 | 8.0.33 | Any | Any | Simple Query Times Out |
| 111659 | 2023-07-04 15:46 | 2023-07-05 13:28 | MySQL Server: Optimizer | Verified (1061 days) | S2 | 8.0 | Any | Any | Empty result of SELECT only when bigger LIMIT |
| 111607 | 2023-06-28 14:26 | 2023-07-12 9:03 | MySQL Server: Compiling | Verified (1056 days) | S3 | 8.0 | Any | Any | Contribution: Fix linkage of \'gen_keyword_list\' executable |
| 111560 | 2023-06-26 9:33 | 2023-06-26 13:53 | MySQL Server: Prepared statements | Verified (1070 days) | S3 | 8.0 | Any | Any | A Prepare statement with cursor on will hang when executed after cursor closed |
| 111559 | 2023-06-26 9:10 | 2026-03-20 12:36 | MySQL Server: Optimizer | Verified (1070 days) | S3 | 8.0.33 | Ubuntu (22.04) | x86 (x86_64) | View with CTE syntax error |
| 111511 | 2023-06-21 8:38 | 2024-04-12 15:00 | MySQL Server: Optimizer | Verified (1075 days) | S3 | 8.0.33 | Ubuntu (22.04) | x86 (x86_64) | CTE missing scope in set queries |
| 111508 | 2023-06-21 7:06 | 2023-06-21 8:24 | MySQL Server: Optimizer | Verified (1075 days) | S3 | 8.0.33 | Any | Any | The query results are inconsistent when different optimizer options are used. |
| 111493 | 2023-06-20 8:25 | 2023-06-20 13:01 | MySQL Server: Optimizer | Verified (1076 days) | S3 | 8.0 | Any | Any | sql return wrong results |
| 111485 | 2023-06-19 11:16 | 2023-06-19 11:40 | MySQL Server: Optimizer | Verified (1077 days) | S3 | mysql-8.0.33 | Linux | x86 | When subquery_to_derived is on, IN-subq to derived table transformed wrongly |
| 111484 | 2023-06-19 8:49 | 2023-06-19 9:10 | MySQL Server: Optimizer | Verified (1077 days) | S3 | mysql-8.0.33 | Linux | x86 | wrong result when rewriting scalar subquery in json function parameters |
| 111479 | 2023-06-19 4:24 | 2023-06-19 11:42 | MySQL Server: Optimizer | Verified (1077 days) | S3 | 5.7.42 | Any | Any | Optimizer estimated rows is always equal to 1 when using spatial index. |
| 111471 | 2023-06-17 14:28 | 2023-06-18 13:26 | MySQL Server: Optimizer | Verified (1078 days) | S2 | 8.0.33 | Ubuntu | x86 | Unexpected Error: Memory capacity exceeded |
| 111466 | 2023-06-16 19:18 | 2025-05-09 12:30 | MySQL Server: Optimizer | Verified (1079 days) | S3 | 5.7 | Any | Any | Contribution: Disable index hints on spatial indices |
| 111454 | 2023-06-16 2:24 | 2023-06-19 8:37 | MySQL Server: Optimizer | Verified (1077 days) | S3 | 8.0.33 | Any | Any | select query with json and time column has different results |
| 111453 | 2023-06-16 0:54 | 2023-06-19 10:09 | MySQL Server: Optimizer | Verified (1077 days) | S2 | 8.0.33 | Any | Any | sql query with "where time_col not between val1 and null' has diffrent results |
| 111432 | 2023-06-15 8:56 | 2023-06-16 13:42 | MySQL Server: Compiling | Verified (1080 days) | S3 | mysql-8.0.33 | Ubuntu (22.04.2) | x86 | c++ Undefined Behavior with clang-16 |
| 111431 | 2023-06-15 8:47 | 2023-06-26 14:48 | MySQL Server: Optimizer | Verified (1081 days) | S3 | 8.0.33 | Ubuntu (22.04) | Other (x86_64) | condition_fanout_filter optimizer wrong result? |
| 111429 | 2023-06-15 6:44 | 2023-06-21 14:02 | MySQL Server: Optimizer | Verified (1081 days) | S3 | 8.0.22, 8.0.33 | Any | Any | Incorrect result when timestamp col apply <=> to the result of subquery |
| 111418 | 2023-06-14 11:43 | 2023-06-15 14:04 | MySQL Server: Optimizer | Verified (1081 days) | S3 | 8.0 | Any | Any | Subquery with ROLLUP gives wrong result |
| 111415 | 2023-06-14 9:39 | 2023-06-19 14:12 | MySQL Server: Optimizer | Verified (1077 days) | S3 | 8.0 | Any | Any | Correlated group query wrong result |
| 111397 | 2023-06-13 13:32 | 2023-06-14 8:30 | MySQL Server: Optimizer | Verified (1083 days) | S3 | 8.0 | Any | Any | 表达式进行<=>比较并将结果进行与操作,执行结果错误 |
| 111367 | 2023-06-12 15:36 | 2026-03-02 20:23 | MySQL Server: Optimizer | Verified (90 days) | S5 | 8.0, 8.0.45, 8.4, 8.4.8 | Any | Any | OFFSET 99 LIMIT 1 on a compound PK takes ages to execute. |
| 111358 | 2023-06-12 8:41 | 2023-06-14 11:35 | MySQL Server: DML | Verified (1083 days) | S3 | 8.0 | Any | Any | delete handl error |
| 111318 | 2023-06-07 14:36 | 2023-06-07 14:55 | MySQL Server: Optimizer | Verified (1089 days) | S3 | 8.0 | Any | Any | block_nested_loop optimizer wrong result? |
| 111310 | 2023-06-07 6:51 | 2023-06-08 8:30 | MySQL Server: Prepared statements | Verified (1088 days) | S3 | 8.0.33 | Ubuntu (22.04) | x86 (x86_64) | Prepared statement with CTE memory leak |
| 111304 | 2023-06-06 21:15 | 2023-06-08 4:00 | MySQL Server: Optimizer | Verified (1088 days) | S2 | 8.0.33, 5.7.42 | Any | Any | The Query Rewrite Plugin mixes-up LIMIT and OFFSET. |
| 111272 | 2023-06-05 8:47 | 2023-06-05 8:51 | MySQL Server: Optimizer | Verified (1091 days) | S2 | 8.0.32, 8.0.33 | Any | Any | Inconsistent behaviors on string comparison with/without index |
| 111268 | 2023-06-04 17:21 | 2023-06-06 11:00 | MySQL Server: Charsets | Verified (1091 days) | S3 | 8.0.25, 8.0.33 | Any | Any | Different character_set_connection returns inconsistent results |
| 111241 | 2023-06-01 11:39 | 2023-06-01 13:57 | MySQL Server: DML | Verified (1095 days) | S3 | Last commit version in github https://gi | Any | Any | Wrong result of `IN` clause |
| 111215 | 2023-05-31 9:58 | 2023-06-02 11:53 | MySQL Server: DML | Verified (1094 days) | S3 | 8.0 | Any | Any | Query in transaction may return rows with same unique key column value |
| 111212 | 2023-05-31 8:30 | 2023-06-16 12:52 | MySQL Server: Compiling | Verified (1080 days) | S2 | 8.0.30, 8.0.33 | Debian (10) | Any (x86 and arm) | compile failed with gcc-10 when lto is enable |
| 111195 | 2023-05-30 7:34 | 2024-04-10 6:59 | MySQL Server: Optimizer | Verified (1097 days) | S3 | 8.0 | Any | Any | There is a logical error in source code |
| 111183 | 2023-05-29 9:46 | 2023-05-29 13:21 | MySQL Server: DML | Verified (1098 days) | S3 | 5.7 | Any | Any | When use ON DUPLICATE UPDATE syntax, TIMESTAMP in primary key, get wrong answer |
| 111159 | 2023-05-26 6:02 | 2023-11-06 11:17 | MySQL Server: Compiling | Verified (939 days) | S3 | 8.0 | CentOS | Any | Incomplete documentation on MySQL rpm rebuilds makes rebuilding packages hard |
| 111097 | 2023-05-22 6:40 | 2024-04-10 9:51 | MySQL Server: Optimizer | Verified (1105 days) | S1 | 8031, 5.7.42, 8.0.33, 8.0.36 | Linux | x86 | Query statement results with subqueries are unstable |
| 111094 | 2023-05-21 2:25 | 2024-04-10 9:55 | MySQL Server: Optimizer | Verified (1105 days) | S3 | 8.0.33, 8.0.36 | Ubuntu (8.0.33-0ubuntu0.20.04.2) | x86 | Results ordered incorrectly |
| 111072 | 2023-05-18 10:12 | 2024-04-10 10:04 | MySQL Server: JSON | Verified (1108 days) | S3 | 8.0.33, 5.7.42, 8.0.36 | Any | Any | The subquery involves JSON, and the execution result is incorrect. |
| 111067 | 2023-05-18 8:05 | 2023-05-19 12:55 | MySQL Server: Optimizer | Verified (1109 days) | S2 | 8.0.25, 8.0.33 | Any | Any | Query result error |
| 111037 | 2023-05-15 21:34 | 2023-05-16 12:57 | MySQL Server: Optimizer | Verified (1111 days) | S5 | 8.0 | Any | Any | MySQL not selecting or not using the index optimally for query |
| 111025 | 2023-05-13 18:22 | 2023-05-15 10:24 | MySQL Server: Optimizer | Verified (1112 days) | S3 | 8.0.33 | Any | Any | Different cost with index hint for same plan |
| 111011 | 2023-05-12 3:16 | 2023-05-15 10:27 | MySQL Server: Compiling | Verified (1112 days) | S3 | 8.0.33 | Any | Any | `mysql_config --libs` returns broken zlib reference |
| 111007 | 2023-05-11 20:30 | 2023-05-12 13:09 | MySQL Server: Optimizer | Verified (1115 days) | S3 | 8.0 | Any | Any | Incorrect rows estimate |
| 110998 | 2023-05-11 15:33 | 2023-12-01 6:49 | MySQL Server: Optimizer | Verified (1110 days) | S5 | 8.0.20+, 8.0.33 | Linux | Any | Performance regression with SELECT query when sorting on limited fields |
| 110988 | 2023-05-11 8:06 | 2023-07-10 13:11 | MySQL Server: Optimizer | Verified (1056 days) | S3 | 8.0.33 | Ubuntu (22.04) | x86 (x86_64) | VIEW call error |
| 110971 | 2023-05-10 3:21 | 2023-05-10 8:00 | MySQL Server: Optimizer | Verified (1117 days) | S5 | 8.0.33 | Any | Any | Optimizer: reverse index scan doesn't affect the cost |
| 110969 | 2023-05-09 23:33 | 2023-05-10 8:01 | MySQL Server: Optimizer | Verified (1117 days) | S3 | 8.0.33 | Any | Any | Functional indexes aren't covering |
| 110931 | 2023-05-05 11:22 | 2023-05-05 12:16 | MySQL Server: Optimizer | Verified (1122 days) | S3 | 8.0.33 | MacOS | Any | Optimizer Trace contradicts to EXPLAIN contradicts to SHOW STATUS |
| 110915 | 2023-05-04 16:28 | 2023-05-18 13:10 | MySQL Server: Optimizer | Verified (1122 days) | S3 | 8.0.33 | Any | Any | Having clause missing scope |
| 110848 | 2023-04-27 15:04 | 2023-05-03 9:59 | MySQL Server: Optimizer | Verified (1124 days) | S5 | 8.0.28, 8.0.33 | Any | Any | missing considering on order by and limit clause in cost calculation |
| 110825 | 2023-04-26 23:58 | 2023-04-27 8:29 | MySQL Server: Charsets | Verified (1130 days) | S3 | 8.0.32 | Any | Any | Explicit COLLATE clause output in SHOW CREATE TABLE incorrectly |
| 110819 | 2023-04-26 15:11 | 2023-05-08 22:48 | MySQL Server: Optimizer | Verified (1130 days) | S2 | 8.0.16+, 8.0.33 | Any | Any | EXISTS with dependent subquery can return incorrect results |
| 110779 | 2023-04-24 11:32 | 2023-05-12 5:49 | MySQL Server: Optimizer | Verified (1115 days) | S5 | 8.0.33, 5.7.42 | Any | Any | IN clause cause pick bad performan index |
| 110656 | 2023-04-11 16:02 | 2024-01-26 9:27 | MySQL Server: Optimizer | Verified (856 days) | S3 | 8.0.32 | Ubuntu (22.04) | x86 (x86_64) | Join query with wrong result |
| 110614 | 2023-04-05 8:32 | 2023-04-05 13:48 | MySQL Server: Optimizer | Verified (1152 days) | S3 | 8.0 | Any | Any | Left join query with wrong result |
| 110597 | 2023-04-04 4:20 | 2023-04-12 14:05 | MySQL Server: Optimizer | Verified (1153 days) | S2 | 8.0.32 | MacOS (12.4) | Any | Different results from equivalent queries |
| 110587 | 2023-04-03 7:51 | 2023-04-03 9:37 | MySQL Server: Optimizer | Verified (1154 days) | S1 | 8.0.27, 8.0.32, 5.7.41 | Any | Any | Bit with index range query may produce different results |
| 110579 | 2023-03-31 15:10 | 2023-04-05 12:34 | MySQL Server: Optimizer | Verified (1157 days) | S3 | 8.0.32, 5.7.41 | Ubuntu (22.04) | x86 (x86_64) | Right join query with BETWEEN wrong result |
| 110563 | 2023-03-30 8:21 | 2023-03-30 8:48 | MySQL Server: Optimizer | Verified (1158 days) | S3 | 8.0.32 | Ubuntu (22.04) | x86 (x86_64) | NULL safe equality operator query with wrong result |
| 110562 | 2023-03-30 8:05 | 2023-04-18 21:01 | MySQL Server: Parser | Verified (1143 days) | S2 | 8.0.32 | Windows (11) | x86 (64bit) | values statement |
| 110556 | 2023-03-30 2:46 | 2026-03-25 20:22 | MySQL Server: JSON | Verified (1158 days) | S2 | 8.0.28, 8.0.32 | Linux | Any | When we use json to build an index, we will get wrong results |
| 110488 | 2023-03-24 7:52 | 2023-03-24 9:17 | MySQL Server: Parser | Verified (1164 days) | S3 | all, 8.0 | CentOS (7.x) | x86 (64bit) | pound sign can not included in qb_name hint |
| 110487 | 2023-03-24 6:09 | 2023-03-24 9:20 | MySQL Server: JSON | Verified (1164 days) | S3 | 5.7,8.0.32 | Any | Any | json array field ignored in multi sort. |
| 110474 | 2023-03-22 23:09 | 2023-03-27 7:02 | MySQL Server: Optimizer | Verified (1161 days) | S5 | 8.0, 8.0.32 | Any | Any | Functional Index is not work like generated column and index |
| 110459 | 2023-03-22 8:09 | 2023-06-07 8:51 | MySQL Server: Optimizer | Verified (1089 days) | S3 | 8.0.32 | Ubuntu (22.04) | x86 (x86_64) | Derive_merge optimizer missing error |
| 110445 | 2023-03-21 3:11 | 2023-03-21 6:32 | MySQL Server: Optimizer | Verified (1167 days) | S5 | 8.0 | Linux | ARM (aarch64) | Optimize my_convert for Arm64 |
| 110406 | 2023-03-17 4:58 | 2023-03-20 14:08 | MySQL Server: Optimizer | Verified (1168 days) | S3 | 8.0 | Any | Any | Storing rows with null in join key in hash table for outer join is useless |
| 110356 | 2023-03-14 8:39 | 2023-03-14 9:37 | MySQL Server: Optimizer | Verified (1174 days) | S3 | 5.7, 8.0 | Any | Any | the presence of case when cause inconsistant columns mapping in order by |
| 110355 | 2023-03-14 7:40 | 2023-03-14 9:21 | MySQL Server: Compiling | Verified (1174 days) | S3 | Ver 8.0 | Any | Any | compiling source code error when cmake with -DWITH_JEMALLOC=true |
| 110354 | 2023-03-14 7:37 | 2023-03-14 9:51 | MySQL Server: Optimizer | Verified (1174 days) | S2 | 8.0.32, 5.7.41 | CentOS | Any | SELECT Query choose different index return different results |
| 110332 | 2023-03-10 7:16 | 2023-03-10 8:38 | MySQL Server: Optimizer | Verified (1178 days) | S2 | 8.0.32, 5.7.41 | Any | Any | Different result when using a user variable |
| 110322 | 2023-03-09 11:41 | 2023-03-09 12:31 | MySQL Server: Optimizer | Verified (1179 days) | S3 | 8.0.32 | Ubuntu (22.04) | x86 (x86_64) | Binary column primary key query with wrong result |
| 110310 | 2023-03-09 8:41 | 2023-04-29 15:24 | MySQL Server: Optimizer | Verified (1179 days) | S3 | 8.0.32 | Ubuntu (22.04) | x86 (x86_64) | BETWEEN query with wrong result |
| 110306 | 2023-03-08 22:08 | 2023-03-09 6:47 | MySQL Server: Optimizer | Verified (1179 days) | S3 | 8.0.32 | Any | Any | Incorrect costing in test_if_cheaper_ordering |
| 110301 | 2023-03-08 11:13 | 2023-03-09 12:30 | MySQL Server: Optimizer | Verified (1179 days) | S3 | 8.0.32 | Ubuntu (22.04) | x86 (x86_64) | Change column wrong result |
| 110291 | 2023-03-07 10:57 | 2023-03-07 13:17 | MySQL Server: Charsets | Verified (1181 days) | S3 | 8.0, 5.7 | Any | Any | SHOW CREATE TABLE breaks DEFAULT for 4 byte Unicode characters |
| 110250 | 2023-03-01 11:59 | 2023-03-24 11:16 | MySQL Server: Optimizer | Verified (1181 days) | S3 | 8.0.32 | Ubuntu (22.04) | x86 (x86_64) | Right join query with wrong result |
| 110244 | 2023-03-01 3:46 | 2023-03-01 6:30 | MySQL Server: Optimizer | Verified (1187 days) | S2 | 8.0.32 | Any | Any | Nesting queries in a projection results in different output |
| 110226 | 2023-02-27 18:39 | 2023-02-28 6:46 | MySQL Server: Compiling | Verified (1188 days) | S3 | 8.0.31 | Any | Any | Build fails when CMAKE_CXX_FLAGS_RELEASE is set because -DNDEBUG isn't set |
| 110217 | 2023-02-27 6:16 | 2023-02-28 17:01 | MySQL Server: Compiling | Verified (1188 days) | S3 | 8.0.32 | Debian | Any | failed to compile in mysql_release mode |
| 110209 | 2023-02-24 16:01 | 2023-02-28 15:17 | MySQL Server: DML | Verified (1188 days) | S3 | 8.0 | Any | Any | PRIMARY KEY should not change the query result. |
| 110174 | 2023-02-23 3:13 | 2023-06-07 15:17 | MySQL Server: Compiling | Verified (1193 days) | S3 | 5.7,8.0 | Any | Any | Re-run cmake may occur even though nothing is modified. |
| 110163 | 2023-02-22 7:22 | 2023-02-22 8:03 | MySQL Server: Compiling | Verified (1194 days) | S5 | 8.0 | Linux | Any | IPTOS_THROUGHPUT enabling code is bypassed on Linux |
| 110156 | 2023-02-21 14:24 | 2023-02-22 15:18 | MySQL Server: Optimizer | Verified (1195 days) | S3 | 8.0 | Any | Any | Incorrect query results caused by subqueries and JOIN |
| 110125 | 2023-02-19 8:48 | 2023-02-20 5:04 | MySQL Server: Optimizer | Verified (1196 days) | S1 | 8.0.32, 5.7 | Ubuntu | Any | Unexpected query result fetched from an indexed column |
| 110111 | 2023-02-17 12:53 | 2023-02-20 12:35 | MySQL Server: Optimizer | Verified (1196 days) | S5 | 8.0.31 | Any | Any | Optimizer chooses worst plan when index condition pushdown opportunity |
| 110017 | 2023-02-10 6:27 | 2023-02-16 4:47 | MySQL Server: Optimizer | Verified (1206 days) | S3 | 5.7.41 | Ubuntu | Any | SELECT returns incorrect value when ORDER BY a CASE WHEN value in left-joined su |
| 110015 | 2023-02-10 3:06 | 2023-11-20 11:24 | MySQL Server: Optimizer | Verified (1203 days) | S5 | 8.0.32 | Windows (11) | x86 | Multi-valued index on JSON array is not used when used in a join |
| 110003 | 2023-02-09 10:37 | 2023-02-13 12:29 | MySQL Server: DML | Verified (1207 days) | S3 | 8.0.32, 5.7, 5.6 | Any | Any | DELETE query does ot work for BIT columns |
| 109975 | 2023-02-08 1:19 | 2023-02-08 8:32 | MySQL Server: DML | Verified (1208 days) | S3 | 5.7, 8.0 | Any | Any | unique key cause wrong result |
| 109897 | 2023-02-02 10:08 | 2023-02-02 11:32 | MySQL Server: Optimizer | Verified (1214 days) | S3 | 8.0.31 | Any | Any | Field_double::val_str causes string truncation |
| 109893 | 2023-02-02 9:15 | 2023-02-02 10:11 | MySQL Server: JSON | Verified (1214 days) | S3 | 8.0.31, 8.0.32 | Any | Any | json_contains always return 1 if candidate array is empty array |
| 109891 | 2023-02-02 9:10 | 2023-02-03 7:55 | MySQL Server: DML | Verified (1213 days) | S3 | 8.0.30,8.0.31, 8.0.32, 5.7 | Any | Any | Contribution by Tencent: insert on duplicate key update would be abnormal |
| 109842 | 2023-01-30 13:51 | 2023-01-31 6:54 | MySQL Server: DML | Verified (1216 days) | S3 | 8.0.31, 8.0.32, 5.7.41 | MacOS | x86 | Problems when mod , division function and extremum function are used together |
| 109838 | 2023-01-30 12:27 | 2023-01-31 6:53 | MySQL Server: DML | Verified (1216 days) | S3 | 8.0.19, 5.7.41, 8.0.31 | Any | Any | Decimal division lose result precision in some specific scenarios |
| 109837 | 2023-01-30 12:24 | 2023-01-30 13:24 | MySQL Server: DML | Verified (1217 days) | S3 | 8.0.31, 8.0.32, 5.7.41 | MacOS | x86 | The representation of 0 in division function in computing string |
| 109824 | 2023-01-27 15:43 | 2023-01-28 8:04 | MySQL Server: Optimizer | Verified (1219 days) | S3 | 8.0.32 | Ubuntu (22.04) | x86 (x86_64) | Bit query with wrong result |
| 109820 | 2023-01-27 8:54 | 2023-01-28 12:55 | MySQL Server: Optimizer | Verified (1220 days) | S3 | 8.0.29, 8.0.32 | Any (rhel-7.4) | Any (x86-64) | optimizer hints in definition of views seem to be ignored |
| 109736 | 2023-01-23 10:41 | 2023-01-25 7:41 | MySQL Server: Optimizer | Verified (1222 days) | S2 | 8.0.32 | Ubuntu (22.04) | x86 (x86_64) | ANY query with wrong result |
| 109728 | 2023-01-21 19:27 | 2023-09-05 8:45 | MySQL Server: Optimizer | Verified (1195 days) | S1 | 8.0.30 | Any | Any | SELECT statement: Result is not proper with GROUP BY with LIMIT OFFSET |
| 109726 | 2023-01-20 21:35 | 2023-05-29 12:01 | MySQL Server: Optimizer | Verified (1224 days) | S2 | 8.0.31 | Ubuntu | x86 | Incorrect results with aggregated functions on correlated lateral joins |
| 109608 | 2023-01-12 15:11 | 2023-01-24 11:39 | MySQL Server: Optimizer | Verified (1223 days) | S3 | 8.0.31 | Ubuntu (22.04) | x86 (x86_64) | Exists query with wrong result |
| 109601 | 2023-01-12 9:00 | 2023-01-12 9:38 | MySQL Server: Optimizer | Verified (1235 days) | S3 | 8.0 | Any | Any | Apply partition pruning if all insert rows have non-null values on autoinc field |
| 109585 | 2023-01-11 12:06 | 2023-01-11 12:28 | MySQL Server: Optimizer | Verified (1236 days) | S2 | 8.0.31 | Any (Docker image) | x86 | Sub query not returning the right result |
| 109560 | 2023-01-09 20:12 | 2023-01-10 6:51 | MySQL Server: Compiling | Verified (1237 days) | S3 | 8.0.30 | Any | Any | "Reduce size of RelWithDebInfo" makes coredump useless for official binaries |
| 109507 | 2023-01-01 11:48 | 2025-07-31 13:10 | MySQL Server: Charsets | Verified (1245 days) | S3 | 8.0.31, 8.0.41 | MacOS | Any | Illegal mix of collations when selecting from a view with a calculated column |
| 109449 | 2022-12-21 9:48 | 2023-01-03 8:04 | MySQL Server: Optimizer | Verified (1257 days) | S3 | 8.0.26, 8.0.31 | Any | Any | functional index could produce wrong result |
| 109429 | 2022-12-19 15:59 | 2022-12-20 14:23 | MySQL Server: Compiling | Verified (1259 days) | S3 | 8.0 | Linux | ARM | Update the directories malloc-lib supports because ARM |
| 109407 | 2022-12-16 12:31 | 2022-12-16 12:38 | MySQL Server: Optimizer | Verified (1262 days) | S2 | 5.7.5, 8.0.31 | Any | Any | Extra line caused by NOT comparsion + ALL |
| 109406 | 2022-12-16 12:31 | 2022-12-16 12:38 | MySQL Server: Optimizer | Verified (1262 days) | S3 | 5.7.11, 8.0.31 | Any | Any | Value change after relaxing WHERE condition |
| 109396 | 2022-12-15 15:20 | 2022-12-16 5:48 | MySQL Server: Compiling | Verified (1262 days) | S3 | 8.0 | Any | Any | Contribution: cmake: fail fatally when sql/sql_yacc.h is missing and bison ... |
| 109367 | 2022-12-13 16:11 | 2022-12-14 5:58 | MySQL Server: Optimizer | Verified (1264 days) | S3 | 5.7.22, 8.0.31 | Any | Any | value changed caused by DISTINCT and JOIN |
| 109363 | 2022-12-13 13:08 | 2022-12-16 14:50 | MySQL Server: Optimizer | Verified (1262 days) | S3 | 8.0.4, 8.0.31 | Any | Any | 0 changed to -0 caused by DISTINCT and UNION ALL |
| 109362 | 2022-12-13 12:55 | 2022-12-13 13:20 | MySQL Server: Optimizer | Verified (1265 days) | S2 | 8.0.13, 8.0.31 | Any | Any | Extra line caused by DISTINCT and key |
| 109356 | 2022-12-13 7:01 | 2022-12-13 7:56 | MySQL Server: Optimizer | Verified (1265 days) | S2 | 8.0.16, 8.0.31 | Any | Any | Extra line caused by DISTINCT and IS TRUE |
| 109354 | 2022-12-13 5:43 | 2022-12-13 7:15 | MySQL Server: Optimizer | Verified (1265 days) | S3 | 8.0.21, 8.0.30, 8.0.31 | Any | Any | Numeric format change caused by DISTINCT, UNION and NULL |
| 109353 | 2022-12-13 5:24 | 2022-12-13 7:12 | MySQL Server: Optimizer | Verified (1265 days) | S2 | 8.0.22, 8.0.31 | Any | Any | Extra line caused by DISTINCT and a certain number of '0' |
| 109352 | 2022-12-13 5:00 | 2022-12-13 6:43 | MySQL Server: Optimizer | Verified (1265 days) | S3 | 8.0.23, 8.0.31 | Any | Any | Numeric format change caused by DISTINCT and UCASE |
| 109333 | 2022-12-11 13:13 | 2022-12-13 12:46 | MySQL Server: Optimizer | Verified (1265 days) | S3 | 8.0.31 | Any | Any | query with/without index get different result |
| 109311 | 2022-12-08 3:40 | 2022-12-09 3:36 | MySQL Server: Optimizer | Verified (1269 days) | S1 | 8.0.22 8.0.30, 8.0.31 | Any | Any | Wrong result |
| 109251 | 2022-11-30 16:06 | 2023-01-18 23:58 | MySQL Server: Compiling | Verified (1229 days) | S3 | 5.7.39, 5.7.40 | Ubuntu | x86 | Cannot compile 5.7.39 on Ubuntu 22.04 because ssl is not found |
| 109212 | 2022-11-27 8:34 | 2022-11-27 9:20 | MySQL Server: Optimizer | Verified (1281 days) | S1 | 8.0.30, 8.0.31 | Any | Any | Incorrect Hash Semijoin Execution |
| 109179 | 2022-11-23 9:47 | 2022-11-25 6:49 | MySQL Server: DML | Verified (1285 days) | S2 | 8.0.31, 5.7.40 | Linux | Any | unique key with null value acts abnormally in select statements |
| 109173 | 2022-11-23 7:51 | 2022-11-24 12:16 | MySQL Server: Optimizer | Verified (1284 days) | S5 | .31, 8.0.31 | Any | Any | Contribution: Offset pushdown to InnoDB and removal of redundant conditions |
| 109155 | 2022-11-22 5:43 | 2023-12-13 11:44 | MySQL Server: Optimizer | Verified (1286 days) | S5 | 8.0.18, 8.0.31, 8.0.35 | Any | Any | Invalid scan on left join tables of which columns not in distinct output fields |
| 109149 | 2022-11-20 5:01 | 2023-12-05 4:04 | MySQL Server: DML | Verified (908 days) | S3 | 8.0.31, 5.7 | Ubuntu | x86 | The representation of 0 in MOD function in computing string |
| 109107 | 2022-11-16 8:19 | 2022-11-22 14:06 | MySQL Server: DML | Verified (1292 days) | S5 | 8.0.31 | Any | Any | Non optimal query plan chosen for DELETE |
| 109076 | 2022-11-14 11:35 | 2023-04-06 13:15 | MySQL Server: Compiling | Verified (1293 days) | S3 | 5.7.40 | Linux | x86 | COMPILATION FAILURE IN 5.7 SERVER WITH GCC 7.5.0 |
| 109014 | 2022-11-07 2:56 | 2022-11-07 8:18 | MySQL Server: Optimizer | Verified (1301 days) | S3 | 5.7.40 | Any | Any | is null acts abnormally in select statements |
| 109003 | 2022-11-04 8:01 | 2024-04-29 7:46 | MySQL Server: Optimizer | Verified (1304 days) | S2 | 8.0.21, 8.0.31 | Windows (10 Pro) | x86 (64-bit) | Index intersection returns less results than expected |
| 109002 | 2022-11-04 6:23 | 2022-11-04 14:13 | MySQL Server: DML | Verified (1304 days) | S3 | 8.0 | Any | Any | filename_to_tablename() handles temp table's name "p0#tmp" incorrectly |
| 108996 | 2022-11-03 17:07 | 2022-11-07 16:51 | MySQL Server: Compiling | Verified (1301 days) | S3 | 8.0.31 | Windows (10.0.18363) | x86 | MySQL Client compilation errors on Windows when OpenSSL path contains spaces |
| 108981 | 2022-11-03 10:35 | 2025-11-14 5:59 | MySQL Server: Optimizer | Verified (1305 days) | S3 | 8.0 | Any (rhel-7.4) | Any (x86-64) | function NULLIF(ASCII()) acts abnormally in select statements |
| 108946 | 2022-11-01 3:35 | 2022-12-13 4:12 | MySQL Server: Optimizer | Verified (1265 days) | S3 | 8.0.30 | Any | Any | 0 changed to 0.0 caused by DISTINCT and UNION ALL |
| 108938 | 2022-10-31 13:59 | 2022-12-13 4:08 | MySQL Server: Optimizer | Verified (1265 days) | S3 | 8.0.30 | Any | Any | Date value change caused by ON |
| 108937 | 2022-10-31 13:30 | 2022-12-13 4:03 | MySQL Server: Optimizer | Verified (1265 days) | S3 | 8.0.30 | Any | Any | Date value change caused by HAVING |
| 108936 | 2022-10-31 12:58 | 2022-12-13 3:56 | MySQL Server: Optimizer | Verified (1265 days) | S2 | 8.0.30 | Any | Any | Value change caused by DISTINCT |
| 108934 | 2022-10-31 9:32 | 2022-10-31 12:00 | MySQL Server: Optimizer | Verified (1308 days) | S2 | mysql-8.0.18/5.7.25 | Any | Any | MySQL-8.0 select query about rand() in Subquery result is wrong |
| 108863 | 2022-10-24 16:40 | 2024-03-15 8:49 | MySQL Server: Optimizer | Verified | S5 | 8.0.31 | Any | Any | different index picked when row is not found, marginally slower |
| 108852 | 2022-10-22 2:45 | 2022-10-22 5:43 | MySQL Server: Optimizer | Verified (1317 days) | S5 | 8.0.31 | Ubuntu (20.04) | x86 | Suspicious Estimated Rows by DISTINCTROW |
| 108851 | 2022-10-22 1:55 | 2022-10-22 5:42 | MySQL Server: Optimizer | Verified (1317 days) | S5 | 8.0.31 | Ubuntu (20.04) | x86 | Suspicious Estimated Rows by JOIN |
| 108833 | 2022-10-20 10:11 | 2022-10-20 12:35 | MySQL Server: Optimizer | Verified (1319 days) | S5 | 8.0.31 | Ubuntu (20.04) | x86 | Suspicious Estimated Rows |
| 108828 | 2022-10-19 13:39 | 2024-10-31 7:17 | MySQL Server: DML | Verified (577 days) | S2 | 8.0.28, 8.0.31 | Any | Any | error DB_UNDO_RECORD_TOO_BIG when update json column |
| 108790 | 2022-10-15 16:46 | 2022-10-17 6:55 | MySQL Server: DML | Verified (1322 days) | S2 | 8.0.30 | Any | Any | Invisible column's default values is invalid if not specify other columns |
| 108788 | 2022-10-15 7:34 | 2022-10-17 7:00 | MySQL Server: Optimizer | Verified (1322 days) | S3 | 5.7.40 | Linux | Any | The temporary alias is incorrect when the SQL statement is executed. |
| 108787 | 2022-10-14 18:51 | 2022-10-17 6:51 | MySQL Server: DML | Verified (1322 days) | S3 | 8.0 | Any | Any | UNIX_TIMESTAMP(NOW()) is lossy |
| 108765 | 2022-10-13 13:52 | 2022-12-19 12:48 | MySQL Server: Data Types | Verified (1322 days) | S2 | 8.0.31 | Ubuntu | Any | comparison of INT column with DECIMAL value changes if index is used or not |
| 108659 | 2022-09-30 7:18 | 2022-09-30 9:54 | MySQL Server: Optimizer | Verified (1339 days) | S3 | 8.0.30 | Any | Any | multi-valued index get wrong result |
| 108630 | 2022-09-28 10:46 | 2022-09-28 11:33 | MySQL Server: JSON | Verified (1341 days) | S3 | 5.7 | Linux (centos 7.5) | x86 | json query bug |
| 108548 | 2022-09-20 6:37 | 2022-09-20 7:35 | MySQL Server: Optimizer | Verified (1349 days) | S2 | 5.7, 5.7.39 | Any | Any | GROUP_CONCAT NOT SET USED_TABLES WHEN DERIVED_MERGE. |
| 108528 | 2022-09-18 10:28 | 2022-09-20 5:25 | MySQL Server: Optimizer | Verified (1349 days) | S2 | 8.0.30 | Ubuntu (20.04) | x86 | Inconsistent read and write, which use the same predicate (WHRE clause) |
| 108520 | 2022-09-16 7:54 | 2022-09-16 8:05 | MySQL Server: Optimizer | Verified (1353 days) | S2 | 8.0, 8.0.30, 5.7.39 | Linux | Any | Return different result due to different optimizer switch |
| 108518 | 2022-09-16 1:56 | 2022-09-16 6:06 | MySQL Server: Compiling | Verified (1353 days) | S3 | 8.0.21 | Any | Any | Return value of flush_io_cache() not get checked |
| 108516 | 2022-09-16 1:50 | 2022-09-19 13:24 | MySQL Server: Optimizer | Verified (1353 days) | S2 | 8.0.21 | Any | Any | Return value of my_b_flush_io_cache(IO_CACHE*, int) not get checked |
| Showing 1-1000 of 2284 (Edit, Save, CSV, Feed) | Show Next 1000 Entries » |
