Showing 1-30 of 247 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
118644 | 2025-07-11 11:17 | 2025-07-11 11:17 | MySQL Server: Archive storage engine | Open | S4 | 8.0.20 | Windows | x86 | ARCHIVE engine not supported by IMPORT TABLE |
118630 | 2025-07-10 9:05 | 2025-07-10 11:05 | MySQL Server: DML | Analyzing (2 days) | S3 | 9.3.0 | Any | Any | INSERT IGNORE failed but insert a different value |
118627 | 2025-07-10 7:26 | 2025-07-10 8:26 | MySQL Server: DML | Analyzing (2 days) | S3 | 8.0.41 | Any | Any | while exexuting prepare statement including 'order by ?', the sort of result set is not right |
118625 | 2025-07-10 3:04 | 2025-07-10 8:26 | MySQL Server: DDL | Analyzing (2 days) | S3 | 9.3.0 | Any | Any | index makes query generate incorrect result |
118624 | 2025-07-10 2:47 | 2025-07-10 8:15 | MySQL Server: InnoDB storage engine | Verified (2 days) | S1 | 8.3.0, 8.0.42, 8.3.0, 8.4.5, 9.3.0 | Any | Any | Wrong result when icp(push a 'like condition' into engine) |
118621 | 2025-07-09 12:39 | 2025-07-09 14:19 | MySQL Server: Optimizer | Verified (3 days) | S3 | 9.3.0, 8.0.42 | Any | Any | subquery_to_derived optimizer makes query produce incorrect result |
118611 | 2025-07-09 4:40 | 2025-07-09 8:27 | MySQL Server: DDL | Verified (3 days) | S3 | 8.4, 8.0.42 | Linux | Any | Creating an InnoDB table with a CONNECTION clause should not be allowed |
118607 | 2025-07-08 18:58 | 2025-07-09 10:02 | MySQL Server: Prepared statements | Verified (3 days) | S4 | 9.3.0 | Any | Any | Providing multiple values for a single parameter, e.g. id IN (?) |
118602 | 2025-07-08 10:26 | 2025-07-08 15:32 | MySQL Server: Replication | Analyzing (4 days) | S2 | 8.0.42 | Ubuntu (8.0.42-0ubuntu0.24.04.1) | x86 | SQL Thread cannot be stopped when last error was 1755 |
118601 | 2025-07-08 9:30 | 2025-07-09 8:47 | MySQL Server: Prepared statements | Not a Bug (3 days) | S3 | 8.0.42, 8.4.5 | Any | Any | Inconstant type between constants in prepare statement and SELECT statement |
118595 | 2025-07-07 15:16 | 2025-07-10 7:19 | MySQL Server: Prepared statements | Not a Bug (2 days) | S1 | 9.3.0 | Any | Any | NULL are transformed to false in certain expression in prepared statement |
118594 | 2025-07-07 14:16 | 2025-07-07 14:58 | MySQL Server: InnoDB storage engine | Verified (5 days) | S2 | 8.0.42 | Any | Any | In-place ALTER TABLE ... ADD FOREIGN KEY can sometimes fails with unwarranted error or even crashes |
118592 | 2025-07-07 12:12 | 2025-07-10 6:53 | MySQL Server: Prepared statements | Duplicate (2 days) | S1 | 9.3.0 | Any | Any | Unexpected result of prepared statement |
118591 | 2025-07-07 11:28 | 2025-07-10 7:11 | MySQL Server: Data Types | Duplicate (2 days) | S1 | 9.3.0 | Any | Any | empty string parse to 0 in SET statement, which is different from that in the SELECT query |
118585 | 2025-07-03 16:35 | 2025-07-04 6:42 | MySQL Server: Optimizer | Verified (8 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 |
118575 | 2025-07-02 11:06 | 2025-07-02 14:38 | MySQL Server: DML | Not a Bug (10 days) | S3 | 8.0.42 | Any | Any | Unexpected NULL Match in <=> Comparison When Subquery Returns No Rows |
118571 | 2025-07-02 7:27 | 2025-07-02 8:56 | MySQL Server: DML | Analyzing (10 days) | S3 | 8.0.41 | Any | Any | using index lookup, the query return a wrong result; |
118570 | 2025-07-02 2:29 | 2025-07-03 9:32 | MySQL Server: DML | Verified (10 days) | S5 | 8.0.42 | Linux (22.04) | x86 | Performance regression occurs with INSERT statements after c17d86b |
118560 | 2025-06-30 11:58 | 2025-06-30 13:01 | MySQL Server: DDL | Verified (12 days) | S3 | 8.0, 8.4 | Any | Any | drop full text can not instant |
118556 | 2025-06-29 19:07 | 2025-06-30 8:14 | MySQL Server: DML | Verified (12 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 (12 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 (12 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 (12 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 (12 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 (12 days) | S3 | 9.3.0 | Ubuntu | x86 | Inconsistant result after removing constraints on table |
118548 | 2025-06-28 7:56 | 2025-06-30 6:45 | MySQL Server: Optimizer | Verified (12 days) | S3 | 9.2.0, 9.3.0 | Linux | x86 | A potential bugs in Mysql Server |
118547 | 2025-06-27 17:26 | 2025-06-30 6:36 | MySQL Server: Information schema | Verified (12 days) | S3 | 8.0, 8.4, 8.0.42 | Any | Any | SET DEFAULT (expr) on PK column requires issuing command twice |
118544 | 2025-06-27 14:18 | 2025-06-30 6:43 | MySQL Server: Optimizer | Verified (12 days) | S3 | 9.2.0 , 9.3.0 | Linux | Any | A potential join operator bug |
118542 | 2025-06-27 8:35 | 2025-06-27 8:51 | MySQL Server: Documentation | Verified (15 days) | S3 | 8.0, 8.4 | Any | Any | The table reference in the performance_schema is incomplete |
118541 | 2025-06-27 8:31 | 2025-06-27 13:37 | MySQL Server: Optimizer | Verified (15 days) | S3 | 9.2.0 , 8.0.42 | Linux | Any | Inconsistent Results Between NATURAL JOIN and its Equivalent Form Using EXCEPT ALL with Implicit Type Casting |
Showing 1-30 of 247 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |