| Showing 1-30 of 11415 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 120555 | 2026-05-27 8:22 | 2026-05-27 11:39 | MySQL Server: Optimizer | Verified | 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 | S2 | 8.4.8 | Any | Any | MySQL `MERGE` vs `TEMPTABLE` view evaluation changes `MAX(SET)` result |
| 120540 | 2026-05-25 1:44 | 2026-05-27 5:41 | MySQL Server: Optimizer | Verified | S2 | 9.7.0 | Ubuntu | x86 | A negated `IS TRUE` guard can still match a DECIMAL row for which the guarded predicate is true |
| 120538 | 2026-05-24 13:46 | 2026-05-26 13:22 | MySQL Server: Optimizer | Verified (1 day) | S2 | 9.7.0 | Ubuntu | x86 | A RIGHT JOIN predicate treats IFNULL(NULL, non-NULL DECIMAL ZEROFILL) as non-matching and drops obvious rows |
| 120535 | 2026-05-24 5:29 | 2026-05-26 12:42 | MySQL Server: Optimizer | Verified (1 day) | 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 (1 day) | 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 (1 day) | S2 | 8.0.45 | Ubuntu | x86 | A LEFT JOIN over DECIMAL ZEROFILL UNIQUE wrongly loses an obvious match |
| 120532 | 2026-05-23 12:34 | 2026-05-26 7:52 | MySQL Server: Optimizer | Verified (1 day) | S2 | 9.7.0 | Ubuntu | x86 | An unused derived subquery triggers a DISTINCT/IFNULL wrong-result in the original path |
| 120531 | 2026-05-23 12:33 | 2026-05-26 7:24 | MySQL Server: Optimizer | Verified (1 day) | 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 (1 day) | 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 (1 day) | 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 (1 day) | 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 |
| 120523 | 2026-05-22 9:13 | 2026-05-25 20:10 | MySQL Server: Optimizer | Verified (2 days) | S3 | 8.0.43 | Any | Any | Wrong result for arithmetic expression involving DAYNAME() and BIT column |
| 120520 | 2026-05-21 16:34 | 2026-05-25 19:58 | MySQL Server: Optimizer | Verified (2 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 (2 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 (2 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 (6 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 (6 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 (6 days) | S3 | 8.0.46 | Ubuntu | x86 | LEFT JOIN ON with IN (empty subquery) produces a spurious match |
| 120504 | 2026-05-20 11:53 | 2026-05-25 8:22 | MySQL Server: InnoDB storage engine | Verified (2 days) | S3 | 9.7 | Any | Any | Can't create some of tables with SPATIAL KEY because of ER_TOO_BIG_ROWSIZE |
| 120495 | 2026-05-18 16:12 | 2026-05-27 6:34 | MySQL Server: Optimizer | Verified | 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 (8 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 (9 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 (9 days) | S5 | 9.7.0 | Any | Any | Join Not Eliminated When Constant Table is Empty Due to PrimaryKeyCol IN (NULL) Condition |
| 120486 | 2026-05-17 8:52 | 2026-05-22 0:10 | MySQL Server: Charsets | Verified (9 days) | S4 | Any | Any | Proposal for Unicode 17 Support | |
| 120477 | 2026-05-14 15:50 | 2026-05-18 10:26 | MySQL Server: Optimizer | Verified (9 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 (9 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 (9 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 (9 days) | S3 | 8.0.43 | Any | Any | Wrong Result After Removing Semantically Redundant RIGHT JOIN ... ON FALSE |
| 120465 | 2026-05-13 8:31 | 2026-05-18 8:52 | MySQL Server: Optimizer | Verified (9 days) | S3 | 8.0.46 | Any | Any | AVG(ASCII()) result truncated to 99.9999 with SQL_BUFFER_RESULT due to incorrect decimal precision |
| Showing 1-30 of 11415 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
