| Showing all 7 (Edit, Save, CSV, Feed) |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 119379 | 2025-11-13 0:42 | 2025-11-13 0:42 | MySQL Server: DDL | Open | S3 | 8.0.41 | Linux (AlmaLinux 9.6) | x86 (XEON) | `AUTO_INCREMENT value ignored after CREATE TABLE in MySQL 8.0.41 (starts from 1 instead of specified value)` |
| 119378 | 2025-11-12 16:41 | 2025-11-12 16:41 | MySQL Server | Open | S3 | Any | Any | Bug issue | |
| 119381 | 2025-11-13 8:14 | 2025-11-13 8:14 | MySQL Server | Open | S2 | 8.0.43, 9.4.0 | Any | Any | Contribution by Tencent: Duplicate auto-increment values happened with partitioned tables and uk conflict |
| 119380 | 2025-11-13 5:58 | 2025-11-13 5:58 | MySQL Server | Open | S3 | Windows | Any | Eventually the Mysql gets struck while executing the query | |
| 119370 | 2025-11-12 10:07 | 2025-11-12 10:07 | MySQL Server | Open | S3 | 9.4.0 8.4.6 | Any | Any | FLOAT Value Returned by CASE Statement Evaluates Incorrectly in Bitwise Operation |
| 119369 | 2025-11-12 9:10 | 2025-11-12 9:52 | MySQL Server: SYS Schema | Open (1 day) | S3 | MySQL 8.0 | Any | Any | MySQL 8.0 sys.x$innodb_lock_waits has Unnecessary type conversion |
| 119376 | 2025-11-12 15:53 | 2025-11-12 15:53 | MySQL Server: Tests | Open | S7 | 8.4.7 | Ubuntu (Ubuntu devel release 26.04) | x86 (amd64v3) | Some upstream tests fail against amd64v3 architecture variant |
| Showing all 7 (Edit, Save, CSV, Feed) |
