| Showing 1-30 of 8457 (Edit, Save, CSV, Feed) | Show Next 30 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 |
| 120577 | 2026-05-30 7:58 | 2026-05-30 7:58 | MySQL Server: MyISAM storage engine | Open | S3 | 8.0.45 | Any | Any | drop index can lead to different results |
| 120576 | 2026-05-30 7:15 | 2026-05-30 7:15 | MySQL Server: MyISAM storage engine | Open | S3 | 8.0.45 | Any | Any | drop index can lead to different 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 |
| 120564 | 2026-05-29 6:43 | 2026-05-29 6:46 | MySQL Server: InnoDB storage engine | Open | S3 | 9.7.0 | Any | Any | InnoDB FTS: Off-by-one error in fts_init_index() causes unsynced document to be lost after crash recovery |
| 120562 | 2026-05-28 12:53 | 2026-05-28 12:53 | MySQL Server: InnoDB storage engine | Open | S1 | 9.6.0 | Linux | Any | InnoDB crashes with assertion failure when UPDATE touches a table with many secondary indexes |
| 120561 | 2026-05-28 11:11 | 2026-05-29 4:41 | MySQL Server: DDL | Open (3 days) | S3 | 9.7/8.4/8.0 | Any | Any | tablespace marked missing after rollback of copy-style ALTER |
| 120558 | 2026-05-27 11:21 | 2026-05-27 11:41 | MySQL Server: InnoDB storage engine | Open (4 days) | S3 | 8.4.8 | Any | Any | Redo log archiving started by dead connection cannot be disabled later |
| 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 |
| 120540 | 2026-05-25 1:44 | 2026-05-29 5:20 | MySQL Server: Optimizer | Patch pending (4 days) | S2 | 9.7.0 | Ubuntu | x86 | A negated `IS TRUE` guard can still match a DECIMAL row for which the guarded predicate is true |
| 120539 | 2026-05-24 15:26 | 2026-05-24 15:26 | MySQL Server: FULLTEXT search | Open | S2 | 9.6.0 | Linux | Any | Duplicate FULLTEXT index on a column returns wrong MATCH...AGAINST results when combined with a STORED generated column |
| 120537 | 2026-05-24 10:19 | 2026-05-24 10:26 | MySQL Workbench | Open (7 days) | S3 | 8.0.46 | Windows (Windows 10 64-bit) | Other (x86_64) | MySQL Workbench Database Connection Not Loading – “Parameter is not valid” Error |
| 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 |
| 120529 | 2026-05-22 17:08 | 2026-05-27 16:48 | MySQL Server: InnoDB storage engine | Open | S3 | Any | Any | Contribution: Log a warning when history list length exceeds threshold | |
| 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 |
| Showing 1-30 of 8457 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
