| Showing all 8 (Edit, Save, CSV, Feed) |
| ID# | Date | Updated | Type | Status | Sev | Version | Target | OS | CPU | Summary | Assigned |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 37182 | 2008-06-04 5:50 | 2018-07-01 18:08 | MySQL Server: Archive storage engine | Verified (4202 days) | S3 | 5.1.24, 5.1.30 | Any (RH Linux 64, WinXP) | Any | Dumped Archive table with AUTO_INCRMENET PRIMARY KEY won't restore from dump | ||
| 55911 | 2010-08-11 13:01 | 2011-02-16 23:44 | MySQL Cluster: Cluster (NDB) storage engine | Verified (3403 days) | S2 | mysql-5.1-telco-7.0 | Linux (Red Hat 3.4.6-8) | Any | Error updating primary key on more than one entry | ||
| 73299 | 2014-07-16 14:59 | 2014-07-18 9:26 | MySQL Server: DDL | Verified (1967 days) | S2 | 5.6.19, 5.6.20 | Any | Any | DEFAULT value for PRIMARY KEY column depends on the way to declare it PRIMARY | ||
| 81926 | 2016-06-20 8:50 | 2016-07-09 10:45 | MySQL Server: mysqldump Command-line Client | Verified (1264 days) | S1 | 5.7.11, 5.7.13 | CentOS (6.5) | Any | mysqldump produce wrong sql on table with virtual json column as primary key | ||
| 82809 | 2016-08-31 7:20 | 2016-09-10 9:38 | MySQL Utilities | Verified (1182 days) | S3 | 1.6.4 | Red Hat | Any | mysqldbcompare output error SQL when 2 tables having different primary keys | ||
| 84374 | 2016-12-30 10:10 | 2017-02-03 13:14 | MySQL Cluster: Cluster (NDB) storage engine | Verified (1066 days) | S3 | 7.3.15, 7.4.13 & 7.5.4 | Any | Any | Primary key is the not the default sharding key anymore | ||
| 70297 | 2013-09-11 12:05 | 2019-07-13 10:10 | Connector / ODBC | Verified (146 days) | S2 | ODBC 6.3 and before | Microsoft Windows (Server 2008, 2012 R2) | Any | Foreign characters in primary key show #deleted in Access table through ODBC | Bogdan Degtyariov | |
| 97001 | 2019-09-25 0:35 | 2019-10-01 7:58 | MySQL Server: Optimizer | Verified (71 days) | S2 | 5.7, 5.7.27 | Any | Any | Dangerous optimization reconsidering_access_paths_for_index_ordering |
| Showing all 8 (Edit, Save, CSV, Feed) |
