| Showing all 4 (Edit, Save, CSV, Feed) |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 71188 | 2013-12-20 13:05 | 2013-12-20 23:06 | MySQL Server: Data Types | Not a Bug (3770 days) | S3 | 5.5 - 5.6.15 | Linux | Any | Strange beheavior ON DUPLICATE KEY UPDATE when auto_increment reaches MAXINT |
| 73154 | 2014-07-01 1:44 | 2014-07-08 4:09 | MySQL Server: Command-line Clients | Verified (3570 days) | S3 | all, 5.5, 5.6, 5.7 | Any | Any | MySQL Doc doesn't specify "mysql -e" to disable --force and history file |
| 77180 | 2015-05-28 8:26 | 2016-07-15 13:58 | MySQL Server: InnoDB storage engine | Closed (2832 days) | S2 | 5.5.40 | Linux (CentOS release 6.5 (Final)) | Any | InnoDB get corrupted during a SELECT query cause by mydumper |
| 93326 | 2018-11-24 17:40 | 2018-11-25 1:30 | MySQL Server: InnoDB storage engine | Unsupported (1969 days) | S2 | 5.7.23-23 | Ubuntu (16.04.5 LTS) | x86 (NPTL 2.23) | InnoDB ACTIVE (PREPARED) threads were marked/converted to XA transactions |
| Showing all 4 (Edit, Save, CSV, Feed) |
