| Showing all 5 (Edit, Save, CSV, Feed) |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 33134 | 2007-12-11 10:57 | 2022-12-04 20:45 | MySQL Server: DDL | Verified (6207 days) | S3 | 5.0.51 | Any | Any | describe table output wrong for unique key when primary key is dropped |
| 42868 | 2009-02-15 20:00 | 2013-03-03 20:45 | MySQL Server: Memory storage engine | Verified (5775 days) | S3 | 5.0.74, 5.1.48 | Any | Any | unique prefixed indexes on varchar columns don't work in memory engine |
| 57782 | 2010-10-27 19:32 | 2021-05-02 20:45 | MySQL Cluster: Cluster (NDB) storage engine | Verified (3246 days) | S3 | mysql-5.1-telco-7.1 | Any | Any | ndb_restore does not warn of possible duplicate keys when using UNIQUE indexes |
| 84630 | 2017-01-23 23:27 | 2017-03-13 13:02 | MySQL Server: Replication | Verified (2827 days) | S3 | 5.6.x, 5.7.x | Any | Any | override master variables with init_slave |
| 106297 | 2022-01-26 22:39 | 2022-01-27 6:00 | MySQL Server: Optimizer | Verified (1046 days) | S2 | 8.0.27, 8.0.28 | Ubuntu (Ubuntu 20.04.3 LTS) | x86 (x86 (Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz)) | Incorrect outputs when combine unique index with NULL |
| Showing all 5 (Edit, Save, CSV, Feed) |
