| « Show Previous 10 Entries | Showing 21-30 of 54 (Edit, Save, CSV, Feed) | Show Next 10 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 88633 | 2017-11-24 3:08 | 2017-12-19 13:02 | MySQL Server: DML | Verified (1655 days) | S3 | 5.7, 5.7.20 | Any | Any | Auto_increment value on a table is less than max(id) can happen |
| 88673 | 2017-11-28 6:11 | 2017-11-28 9:46 | MySQL Server: InnoDB storage engine | Verified (1676 days) | S3 | 5.7.20 | Any | Any | Regression CREATE TBL from 5.7.17 to 20 (part #1: innodb_file_per_table = ON). |
| 88674 | 2017-11-28 6:17 | 2017-11-28 9:37 | MySQL Server: InnoDB storage engine | Verified (1676 days) | S3 | 5.7.20 | Any | Any | Regression CREATE TBL from 5.7.17 to 20 (part #2: innodb_file_per_table = OFF). |
| 88694 | 2017-11-29 10:51 | 2017-12-04 7:23 | MySQL Server: Security: Privileges | Verified (1674 days) | S3 | 5.7.20 | Any | Any | MySQL accepts wildcard for database name for table level grant but won't use it |
| 88701 | 2017-11-29 21:18 | 2017-12-17 12:40 | MySQL Server: DML | Verified (1674 days) | S3 | 5.6.38, 5.7.20 | Any | Any | CHECKSUM TABLE returns ambiguous results for table/db names with dots |
| 88720 | 2017-11-30 14:52 | 2018-02-24 10:49 | MySQL Server: Replication | Verified (1673 days) | S3 | 5.6, 5.7, 8.0.3, 5.6.38, 5.7.20 | Any | Any | Inconsistent and unsafe FLUSH behavior in terms of replication |
| 88783 | 2017-12-06 11:39 | 2017-12-06 12:05 | MySQL Server: InnoDB storage engine | Verified (1668 days) | S2 | 5.7.20, 5.6.38 | CentOS (7) | Any | Incorrect table name error for given empty path with DATA DIRECTORY option |
| 88791 | 2017-12-06 15:38 | 2017-12-08 13:05 | MySQL Server: Row Based Replication ( RBR ) | Verified (1666 days) | S2 | 5.7.20 | Ubuntu | Any | Binary log for generated columncontains new value as WHERE clause, not old value |
| 88808 | 2017-12-07 10:03 | 2018-01-01 22:23 | MySQL Server: InnoDB storage engine | Verified (1642 days) | S1 | 5.7.20 | Any | Any | InnoDB errors on mysql db tables when using innodb-force-recovery |
| 88827 | 2017-12-08 1:30 | 2018-05-31 13:08 | MySQL Server: InnoDB storage engine | Verified (1551 days) | S3 | 5.6.35, 5.6.38, 5.7.20, 8.0.4 | Any | Any | innodb uses too much space in the PK for concurrent inserts into the same table |
| « Show Previous 10 Entries | Showing 21-30 of 54 (Edit, Save, CSV, Feed) | Show Next 10 Entries » |
