Showing 1-1000 of 13230 (Edit, Save, CSV, Feed) | Show Next 1000 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
11839 | 2005-07-09 22:32 | 2005-07-10 1:56 | MySQL Server: Installing | Not a Bug (7175 days) | S4 | none | none | Any | kemal |
11840 | 2005-07-09 22:47 | 2005-07-10 1:53 | MySQL Server: Installing | Not a Bug (7175 days) | S4 | Any | install | ||
106153 | 2022-01-13 1:23 | 2022-01-13 18:21 | MySQL Server: mysqlpump Command-line Client | Verified (1144 days) | S3 | 5.7, 8.0 | Any | Any | mysqlpump should use CREATE TABLE IF NOT EXISTS |
20686 | 2006-06-25 15:20 | 2012-05-18 20:19 | MySQL Server | Duplicate (6663 days) | S2 | 4.1.20 and 5.0.22 | Linux (Linux) | Any | wrong date vs values(date) compare in on duplicate key |
25129 | 2006-12-18 4:12 | 2009-03-24 12:25 | MySQL Server: Installing | Can't repeat (5822 days) | S2 | 5.1.14 | Any | Any | 5.1.14 mysql_fix_privilege_tables does not update privilege tables from 5.0.22 |
11372 | 2005-06-16 9:19 | 2006-07-25 0:17 | MySQL Server: Installing | Closed (6795 days) | S3 | 5.0.7 beta | Linux (Linux) | Any | Invalid default value for 'sql_mode' when running mysql_fix_privilege_tables |
79665 | 2015-12-16 10:50 | 2017-05-31 20:02 | MySQL Server: Documentation | Closed (2832 days) | S3 | any | Any | Any | Manual does NOT explain locks set by INSERT ... ON DUPLICATE KEY UPDATE properly |
114836 | 2024-05-01 10:36 | 2024-07-02 16:45 | MySQL Server: Installing | Closed (247 days) | S2 | MySQL 8.4.0 | MacOS (macOS 14.4.1) | ARM | Couldn't load plugin named 'keyring_file' with soname 'keyring_file.so' |
2394 | 2004-01-14 21:21 | 2004-01-14 22:16 | MySQL Server | Can't repeat (7718 days) | S3 | 5.0.0 | Windows (winxp) | Any | Crash MySQL |
26427 | 2007-02-15 21:20 | 2007-09-18 14:01 | MySQL Server: Falcon storage engine | Can't repeat (6375 days) | S3 | 5.2.4-falcon-alpha-debug | Linux (suse 9.3 x86) | Any | Serial Log possible gap: 142463 - 115862 - Duplicate INDEXES.SYSTEM |
33066 | 2007-12-07 16:33 | 2007-12-25 14:06 | MySQL Server: DML | Not a Bug (6277 days) | S3 | 5.1.22-rc | Any | Any | last_insert_id(), wrong values, InnoDB, insert on duplicate key update |
28478 | 2007-05-16 17:05 | 2007-06-20 0:51 | MySQL Server: MyISAM storage engine | Closed (6465 days) | S2 | 5.0.42, * | Any | Any | Improper key_cache_block_size corrupts MyISAM tables |
66104 | 2012-07-30 20:48 | 2012-09-07 6:31 | MySQL Cluster: Cluster (NDB) storage engine | Closed (4559 days) | S2 | 7.2.7 | Linux (Debian 6) | Any | MySQL-Cluster Online backup error |
83921 | 2016-11-22 20:33 | 2017-01-04 7:22 | MySQL Server: Parser | Verified (2979 days) | S3 | 5.7.16 | CentOS (7) | Any | falsely Ambigous Column in On Duplicate Key Update using a subselect |
52419 | 2010-03-28 18:54 | 2011-02-16 23:44 | MySQL Server: General | Closed (5264 days) | S2 | 5.5.3-m3 | Linux (x86 icc) | Any | x86 assembly based atomic CAS causes test failures |
9092 | 2005-03-10 13:00 | 2005-07-26 4:40 | MySQL Server: Installing | Can't repeat (7159 days) | S3 | 4-1-10-standard-log | Linux (RedHat 9) | Any | after running mysql_fix_privilege_tables server still uses old password format |
66301 | 2012-08-10 8:46 | 2013-04-22 20:28 | MySQL Server: InnoDB storage engine | Closed (4332 days) | S2 | 5.1, 5.5 | Any | Any | INSERT ... ON DUPLICATE KEY UPDATE + innodb_autoinc_lock_mode=1 is broken |
45802 | 2009-06-27 17:19 | 2009-07-24 9:11 | MySQL Query Browser | Closed (5700 days) | S1 | 1.2.17 | Windows (Vista) | Any | Duplicate & Garbage indexes added to tables |
29851 | 2007-07-17 18:05 | 2016-02-25 12:24 | MySQL Cluster: Cluster (NDB) storage engine | Closed (6220 days) | S2 | 5.0.44 | Linux | Any | TRUNCATE causes error 4350 from cluster in INSERT... ON DUPLICATE KEY UPDATE |
27650 | 2007-04-04 13:24 | 2007-05-01 17:45 | MySQL Server | Closed (6515 days) | S1 | 5.0.38, 5.x | Any | Any | ON DUPLICATE KEY UPDATE fails when setting UNIQUE values with multi row inserts |
14131 | 2005-10-19 6:06 | 2012-05-18 20:19 | MySQL Server: Charsets | Verified (5988 days) | S4 | 5.0, 5.1, 6.0 | Linux (any) | Any | Report PAD attribute in SHOW COLLATION and INFORMATION_SCHEMA.COLLATIONS |
76931 | 2015-05-04 13:37 | 2015-05-21 22:38 | MySQL Cluster: Cluster (NDB) storage engine | Closed (3581 days) | S3 | 7.5.0 | Any | Any | Random warning order ndb_one_fragment |
28781 | 2007-05-30 17:24 | 2016-02-25 12:24 | MySQL Server: Documentation | Closed (5371 days) | S2 | 5.0.42 | Any | Any | InnoDB increments auto-increment value incorrectly with ON DUPLICATE KEY UPDATE |
38018 | 2008-07-10 14:43 | 2008-07-11 15:52 | MySQL Server: Maria storage engine | Closed (6078 days) | S3 | 5.1-maria | Linux | Any | Maria: INSERT SELECT ON DUPLICATE KEY UPDATE, LOAD DATA REPLACE wrong lock |
70460 | 2013-09-28 15:17 | 2016-12-30 9:20 | MySQL Cluster: Cluster (NDB) storage engine | Verified (4173 days) | S2 | 5.6.11-ndb-7.3.2-cluster-gpl-log | Linux (CentOS release 6.4 (Final)) | Any | Mysql Cluster and constraints |
98420 | 2020-01-28 19:50 | 2020-02-28 17:48 | MySQL Workbench | Duplicate (1859 days) | S2 | 8.0.19 | Windows (Microsoft Windows 10 Pro) | x86 | Will not start due to System.IO.FileNotFoundException |
98793 | 2020-03-02 2:01 | 2020-04-03 1:00 | MySQL Server: Windows | No Feedback (1795 days) | S2 | 8.0.18 - MySQL Community Server - GPL | Windows (Windows Server 2019 17763.973) | Any | Mysql Service Stop when database has large number of data and try to truncate |
109891 | 2023-02-02 9:10 | 2023-02-03 7:55 | MySQL Server: DML | Verified (758 days) | S3 | 8.0.30,8.0.31, 8.0.32, 5.7 | Any | Any | Contribution by Tencent: insert on duplicate key update would be abnormal |
69153 | 2013-05-06 10:40 | 2013-06-28 9:25 | MySQL Workbench: Modeling | Closed (4265 days) | S2 | 5.2.47 | MacOS (10.8.3) | Any | Synchronize database for column name change drops all foreign key constraints |
13587 | 2005-09-28 21:40 | 2005-10-20 6:59 | MySQL Server: Stored Routines | Closed (7073 days) | S3 | 5.0.13-rc-standard-log, 5.0.13-rc-nt | Linux (Linux, Solaris 9 64 bit, Windows) | Any | Server crash when SP is created without database selected |
93806 | 2019-01-03 17:41 | 2020-09-21 14:21 | MySQL Server: Documentation | Closed (2202 days) | S3 | all | Any | Any | Document error about "ON DUPLICATE KEY UPDATE " |
73190 | 2014-07-03 21:23 | 2017-04-17 13:36 | MySQL Server: mysqldump Command-line Client | Verified (3516 days) | S4 | Any | Any | [mysqldump] Support INSERT ... ON DUPLICATE KEY UPDATE for data dumps | |
37713 | 2008-06-28 10:27 | 2018-09-25 21:47 | Tests: Replication | Can't repeat (5865 days) | S7 | 6.0-rpl | Any | Any | rpl.rpl_known_bugs_detection failed in pushbuild |
78270 | 2015-08-29 22:50 | 2016-01-13 20:44 | MySQL Server: InnoDB storage engine | Closed (3336 days) | S3 | MySQL 5.6.26. | Any (CentOS release 6.6) | Any | Unexpected Memory Consumption for Bulk Index Creation in InnoDB. |
17801 | 2006-02-28 18:26 | 2006-03-13 12:51 | MySQL Cluster: Cluster (NDB) storage engine | Closed (6929 days) | S1 | 5.1.8 | Linux (Linux 32 Bit OS) | Any | INSERT ON DUPLICATE KEY UPDATE using NDB table cause core |
96328 | 2019-07-25 10:37 | 2019-07-25 13:04 | MySQL Server | Not a Bug (2047 days) | S3 | all | Any | Any | INSERT ... ON DUPLICATE KEY UPDATE |
73483 | 2014-08-06 10:18 | 2014-08-14 18:44 | MySQL Server | Not a Bug (3853 days) | S3 | 5.6.19 | Linux (debian6.0) | Any | innodb_autoinc_lock_mode, row based replication, duplicate primary key assigned |
29329 | 2007-06-25 3:37 | 2015-03-15 20:45 | MySQL Server: Stored Routines | No Feedback (6289 days) | S3 | 5.0.38 | Linux (Gentoo) | Any | Explicit commit complaints |
115496 | 2024-07-03 8:18 | 2024-07-03 9:00 | MySQL Server: Locking | Unsupported (242 days) | S3 | 5.6.16, 5.6.51, 5.7.1 | Any | Any | UPDATE and INSERT...ON DUPLICATE KEY UPDATE... cause dead lock |
111669 | 2023-07-06 0:47 | 2023-07-12 13:04 | MySQL Server: Optimizer | Verified (599 days) | S5 | 8.0.33 | Any | Any | Simple Query Times Out |
27955 | 2007-04-19 14:33 | 2015-03-15 20:45 | MySQL Server: MyISAM storage engine | No Feedback (6497 days) | S2 | 5.0.37 | Linux (FC5) | Any | error of unknown column 'xxx' in field list but column 'xxx' isnt in the query |
23647 | 2006-10-25 20:53 | 2006-11-02 21:44 | MySQL Server: Falcon storage engine | Closed (6695 days) | S3 | Linux (Linux 64-bit) | Any | Falcon crashes on update no-key test, 64 threads | |
52430 | 2010-03-29 11:01 | 2011-02-16 23:44 | MySQL Server: Data Types | Closed (5352 days) | S3 | 5.5.3-m3 | Any | Any | Incorrect key in the error message for duplicate key error involving BINARY type |
28904 | 2007-06-05 19:04 | 2011-03-16 16:36 | MySQL Server: Optimizer | Closed (6462 days) | S2 | 5.0.41 | Linux (SuSE 10.1) | Any | ON UPDATE CURRENT_TIMESTAMP does not work properly with ON DUPLICATE KEY |
69513 | 2013-06-19 14:22 | 2013-08-19 1:00 | MySQL Server: InnoDB storage engine | No Feedback (4214 days) | S3 | 5.6 | Windows (Windows 7 Ultimate 64-bit) | Any | InnoDB: Assertion failure in thread 5616 in file ut0lst.h line 271 |
27744 | 2007-04-11 1:41 | 2007-04-12 11:58 | MySQL Server | Can't repeat (6534 days) | S2 | 5.0.37-log | Linux | Any | command "insert .. on duplicate key update" does not update and/or AFR is wrong |
27006 | 2007-03-09 16:19 | 2007-03-20 16:34 | MySQL Server: Stored Routines | Closed (6557 days) | S1 | 5.0.36 | Any (All) | Any | AFTER UPDATE triggers not fired with INSERT ... ON DUPLICATE KEY UPDATE |
27307 | 2007-03-20 21:24 | 2007-03-20 21:31 | MySQL Server: General | Duplicate (6557 days) | S2 | 5.0.37-community | Linux (Linux (x86)) | Any | 'INSERT ... ON DUPLICATE KEY UPDATE' not performing update |
42975 | 2009-02-18 16:07 | 2011-02-16 23:43 | MySQL Server: General | Duplicate (5855 days) | S2 | 5.1.30 | Linux | Any | MySQL Crash: glibc detected double free or corruption |
83239 | 2016-10-02 4:16 | 2016-10-06 21:28 | MySQL Server: Optimizer | Not a Bug (3069 days) | S3 | 5.7.15-0ubuntu0.16.04.1 | Ubuntu (16.04) | Any | Inconsistent nonaggregated field in SELECT not in GROUP BY |
93141 | 2018-11-09 13:17 | 2018-11-20 14:42 | MySQL Server: DML | Can't repeat (2294 days) | S3 | 5.7.22-22-log | Linux | Any | Duplicate Records despite index |
11519 | 2005-06-23 5:17 | 2005-07-01 12:59 | MySQL Server | Closed (7184 days) | S2 | 5.0.8 | many | Any | type_timestamp fails on many platforms |
35457 | 2008-03-20 12:06 | 2008-04-26 20:58 | MySQL Workbench | No Feedback (6154 days) | S3 | 5.0.15 | Windows | Any | DROP TABLE comes after CREATE TABLE IF NOT EXISTS |
28505 | 2007-05-18 0:19 | 2007-06-19 0:56 | MySQL Server | Closed (6466 days) | S2 | 3.1.10, and 5.0.6 | Any | Any | Update count for an INSERT DUPLICATE KEY not correct when CLIENT_FOUND_ROWS set |
89147 | 2018-01-08 22:18 | 2018-01-11 9:52 | MySQL Server: Group Replication | Verified (2607 days) | S4 | 5.7.20,8.0.3 | Any | Any | The field end_log_pos in Group Replication error messages is ambiguous. |
51838 | 2010-03-08 17:29 | 2011-02-16 23:44 | MySQL Server: InnoDB storage engine | Won't fix (5462 days) | S2 | 5.0.84 | Any | Any | Innodb gets X lock for INSERT ON DUPLICATE KEY UPDATE but not INSERT SELECT |
100518 | 2020-08-13 15:08 | 2020-08-30 21:18 | MySQL Server: Replication | Can't repeat (1645 days) | S2 | 5.7.29 | CentOS | Any | Auto-increment value in UPDATE conflicts with internally generated values |
13385 | 2005-09-21 17:17 | 2005-09-21 17:55 | MySQL Server | Closed (7102 days) | S2 | 4.1.13 | Windows (Windows 2000) | Any | values() fails with 'Column specified twice' when ON DUPLICATE KEY UPDATE used |
50619 | 2010-01-26 11:02 | 2011-02-16 23:44 | MySQL Server: DML | Closed (5165 days) | S3 | 5.1.44,5.5.99-m3,6.0.14-alpha | Any | Any | assert in handler::update_auto_increment |
79634 | 2015-12-14 13:04 | 2016-01-18 10:02 | MySQL Server | Not a Bug (3331 days) | S2 | 5.6.25-log | Debian (7.8) | Any | transaction written to the binary log were not actually applied to the DB |
13392 | 2005-09-21 22:47 | 2005-10-31 20:13 | MySQL Server: Optimizer | Closed (7062 days) | S2 | 5.0.12-beta-nt-log | Any (All) | Any | values() fails with 'ambiguous' or returns NULL with ON DUPLICATE and SELECT |
73252 | 2014-07-10 7:18 | 2014-08-22 1:00 | MySQL Server: InnoDB storage engine | No Feedback (3846 days) | S3 | 5.6.13 | Any | Any | Duplicate foreign keys break insertions to a table |
117165 | 2025-01-09 6:53 | 2025-02-27 15:10 | MySQL Server: DML | Need Feedback (3 days) | S5 | 8.0.36 | Any | Any | load data local infile replace have poor performance |
61067 | 2011-05-05 9:55 | 2011-09-23 23:00 | MySQL Server: DML | No Feedback (4910 days) | S2 | 5.5.11 | Windows (Vista) | Any | Foreign key creation order is essential |
89802 | 2018-02-26 11:21 | 2018-02-27 12:04 | MySQL Server: DDL | Not a Bug (2560 days) | S3 | 5.6.35-81.0 | Any | Any | MySQL Table key/index position order - No possibility to change |
5320 | 2004-08-31 16:38 | 2004-08-31 21:40 | MySQL Cluster: Cluster (NDB) storage engine | Duplicate (7488 days) | S3 | 4.1.4-gamma (ndb) | Linux (SuSE 9.1) | Any | Cluster: different error message returned than under MyISAM/InnoDB |
54249 | 2010-06-05 2:32 | 2017-05-21 20:45 | MySQL Server: Row Based Replication ( RBR ) | Verified (5383 days) | S3 | 5.1 | Any | Any | More verbose RBR error logging |
85821 | 2017-04-06 7:11 | 2020-12-01 11:51 | MySQL Server: Optimizer | Closed (1552 days) | S3 | 8.0.2-DEBUG | Any | Any | partial update on views does not work |
41532 | 2008-12-17 9:06 | 2011-02-16 23:43 | Connector / J | Closed (5813 days) | S5 | 5.1.7 | Any | Any | Slower performance since 5.1.7 with rewriteBatchedStatements option |
115053 | 2024-05-17 16:34 | 2024-05-20 15:01 | MySQL Server: DDL | Verified (286 days) | S3 | 8.0 | Windows | Any | Infinite foreigns keys |
104608 | 2021-08-12 22:31 | 2021-11-10 13:24 | MySQL Server: InnoDB storage engine | Verified (1208 days) | S4 | 5.7.35, 8.0.26 | Any | Any | Improve error message for ALTER failing because concurrent Duplicate entry. |
83085 | 2016-09-21 18:15 | 2016-10-22 1:00 | MySQL Server: InnoDB storage engine | No Feedback (3054 days) | S1 | MYSQL 5.5.49 | Debian (x86_64) | Any | Insert after Left join generates duplicated rows in result |
62088 | 2011-08-04 22:53 | 2011-08-05 14:50 | MySQL Workbench: Modeling | Not a Bug (4958 days) | S3 | 5.2.31a | Windows | Any | Forward engineer ALTER script generates different SQL than CREATE |
11599 | 2005-06-28 0:07 | 2005-06-28 11:09 | MySQL Server: MyISAM storage engine | Not a Bug (7187 days) | S2 | 4.1.11a | Linux (Linux) | Any | I get a Duplicate entry error message even when the key doesn't exist yet |
23133 | 2006-10-10 11:27 | 2006-10-26 18:06 | MySQL Server: Documentation | Closed (6702 days) | S3 | 5.0.26-standard-log | Linux (Linux radium.net45.com 2.6.9-34.) | Any | LOAD INDEX INTO CACHE fails |
27123 | 2007-03-14 9:49 | 2007-05-09 6:05 | MySQL Server: Partitions | Closed (6507 days) | S2 | 5.1.17BK | Linux (suse 9.3 x86) | Any | partition + on duplicate key update + varchar = Can't find record in table |
4008 | 2004-06-04 15:12 | 2004-06-25 15:14 | MySQL Server | Closed (7555 days) | S3 | 4.1, 5.0 | Linux (Linux) | Any | insert on duplicate fails depending on MERGE table INSERT_METHOD |
74733 | 2014-11-07 13:02 | 2014-11-07 16:14 | MySQL Server: Security: Privileges | Verified (3768 days) | S3 | 5.5, 5.6, 5.7 | Any | Any | SELECT privilege is not checked for views on UPDATE which references to columns |
37411 | 2008-06-14 19:21 | 2017-05-14 20:45 | MySQL Server: InnoDB storage engine | No Feedback (5947 days) | S2 | 5.0.51a | Solaris | Any | Threads staying in the "Sending Data" for long periods of time |
39033 | 2008-08-26 6:10 | 2021-05-02 20:45 | MySQL Cluster: Cluster (NDB) storage engine | Duplicate (6030 days) | S2 | 5.1.24-ndb-6.3.16 | Linux | Any | Table disappear |
68772 | 2013-03-26 2:58 | 2013-05-02 1:00 | MySQL Server: MyISAM storage engine | No Feedback (4323 days) | S2 | Ver 5.5.29-0ubuntu0.12.04.2-log | Linux (Ubuntu 12.04) | Any | New tables corrupted: Table ... is marked as crashed and should be repaired |
86148 | 2017-05-01 13:19 | 2018-02-09 18:16 | MySQL Workbench | Closed (2578 days) | S3 | 6.3, 6.3.9 | Windows (7, 64 bit) | Any | MySQL Workbench 6.3 problems importing JSON files into MySQL 5.7.12 |
98077 | 2019-12-26 10:06 | 2020-01-15 13:53 | MySQL Server | Not a Bug (1873 days) | S3 | 5.7.23 | CentOS (CentOS Linux release 7.4.1708 (Core) ) | Any | alloc too much memory by a small table |
38041 | 2008-07-11 9:46 | 2008-09-30 20:31 | MySQL Server: Falcon storage engine | Closed (5997 days) | S1 | 6.0-falcon | Any | Any | Bizarre errors when ALTER ADD/DROP KEY on Falcon tables |
77572 | 2015-07-01 2:33 | 2018-10-29 21:17 | MySQL Server: DDL | Closed (3454 days) | S3 | 5.6.16 5.7.7 | Any | Any | The bogus duplicate key error in online ddl with incorrect key name |
61133 | 2011-05-11 13:29 | 2012-12-20 20:55 | MySQL Server: Replication | Can't repeat (4455 days) | S2 | 5.5.10 | Linux (SuSE Linux Enterprise 11.1) | Any | Master -> Slave : duplicate key error after running fine for days |
19478 | 2006-05-02 13:04 | 2008-01-29 10:02 | MySQL Server | Can't repeat (6242 days) | S3 | 5.0.20 | Windows (Windows 2003) | Any | SQL 'UPDATE' stops working |
45374 | 2009-06-08 13:24 | 2011-02-16 23:44 | MySQL Server: Documentation | Closed (5728 days) | S4 | Any | Any | Documentation: need to document that certain WHERE clauses require Select_priv | |
984 | 2003-08-03 12:15 | 2003-08-12 13:46 | MySQL Server: InnoDB storage engine | Closed (7873 days) | S1 | 3.23.48 | Linux (Linux) | Any | mysqld crashes when creating an innodb table with foreign key |
67367 | 2012-10-24 19:26 | 2013-03-26 1:00 | MySQL Workbench: Modeling | No Feedback (4360 days) | S2 | 5.2.44 | MacOS (Darwin 12.2.0) | Any | Synchronization requests to remove existing tables. |
32437 | 2007-11-16 14:41 | 2007-11-22 8:36 | MySQL Server: Replication | Not a Bug (6310 days) | S2 | 5.0.45 | Linux (CentOS) | Any | INSERT ... ON DUPLICATE KEY UPDATE replication 5.0.27 master & 5.0.45 slave |
33395 | 2007-12-20 9:24 | 2008-04-17 9:31 | MySQL Server: MyISAM storage engine | No Feedback (6163 days) | S1 | Ver 14.12 Distrib 5.0.51 | Linux (pc-linux-gnu (x86_64) ) | Any | [ERROR] /usr/sbin/mysqld: Incorrect key file for table '/tmp/#sql_77d3_0.MYI'; |
38484 | 2008-07-31 10:55 | 2008-11-07 15:59 | MySQL Server: Maria storage engine | Closed (5959 days) | S1 | 6.0.6-alpha, 6.0.7pre,6.0.7,6.0.8pre | Any | Any | maria: DELETE causes crash or index corruption |
53913 | 2010-05-22 15:12 | 2011-02-16 23:44 | MySQL Server: General | Closed (5398 days) | S2 | 5.1.45-1 | Linux (Debian/squeeze) | Any | Unknown column error for existing column |
57768 | 2010-10-27 11:58 | 2010-10-29 5:00 | MySQL Server: InnoDB storage engine | Not a Bug (5238 days) | S2 | 5.1.41 | Windows (Win 7) | Any | FOREIGN KEY ON UPDATE CASCADE does not work with self-reference |
116502 | 2024-10-30 4:31 | 2025-01-20 6:58 | MySQL Server: InnoDB storage engine | Verified (122 days) | S2 | 8.0.40 | Any | Any | Duplicate Detection Flaw for NULL Values in UK During DDL Rollback Operations |
68609 | 2013-03-08 0:28 | 2014-10-09 16:07 | MySQL Server: Replication | Won't fix (3797 days) | S3 | 5.5.30, 5.6.10 | Any | Any | MBR: Unique key updates are not marked unsafe, replication fails |
10538 | 2005-05-11 10:52 | 2022-08-21 20:45 | MySQL Server | Duplicate (7186 days) | S1 | 5.0.6bk | Linux (Linux) | Any | Triggers not locking tables |
27604 | 2007-04-03 1:29 | 2015-03-15 20:45 | MySQL Server: General | No Feedback (6474 days) | S1 | 14.12 Distrib 5.0.37, for pc-linux-gnu ( | Linux (Redhat 9 (Shrike)) | Any | Update query with Join crashes mysqld |
19243 | 2006-04-21 4:45 | 2006-09-13 17:45 | MySQL Server: Optimizer | Closed (6745 days) | S3 | 5.0.21-BK, 4.1.7 | Linux (Linux, Windows) | Any | wrong LAST_INSERT_ID() after ON DUPLICATE KEY UPDATE |
79937 | 2016-01-12 15:42 | 2016-01-13 12:15 | MySQL Server: DML | Not a Bug (3336 days) | S3 | 5.6.27 | Any | Any | Incorrect record updated using ON DUPLICATE KEY UPDATE processing |
24697 | 2006-11-29 15:13 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5174 days) | S3 | 5.0.24a-community-nt-log/4.1BK/5.0BK/5.1BK | Windows (Windows 2000 and Linux) | Any | insert .. select ....ON DUPLICATE KEY UPDATE fails with ambiguous column name |
71232 | 2013-12-26 11:34 | 2014-07-04 9:51 | MySQL Server: InnoDB storage engine | Verified (3894 days) | S3 | 5.6.15 | Any | Any | Wrong behaviour for auto_increment unsigned bigint column approaching max value |
36802 | 2008-05-19 15:42 | 2022-01-05 15:50 | MySQL Server: Optimizer | Closed (1152 days) | S3 | 5.0, 5.1, 6.0 BK | Any | Any | MySQL only use covered index when selecting from a view (or subquery) with union |
10936 | 2005-05-28 1:25 | 2005-08-27 7:44 | MySQL Cluster: Cluster (NDB) storage engine | Closed (7127 days) | S3 | 5.1.0 | Linux (Linux) | Any | Cluster engine shows wrong key value for duplicate key error. |
76927 | 2015-05-04 12:09 | 2016-06-18 21:26 | MySQL Server: InnoDB storage engine | Closed (3485 days) | S2 | 5.1, 5.5, 5.6, 5.7, 8.0 | Any | Any | Duplicate UK values in READ-COMMITTED (again) |
117237 | 2025-01-19 4:13 | 2025-01-21 11:41 | MySQL Server: InnoDB storage engine | Verified (40 days) | S2 | 8.0.40, 8.4.3, 9.1.0 | Any | Any | Unexpected Duplicate Error in DDL Row Log Apply |
13286 | 2005-09-16 22:01 | 2005-10-26 22:12 | MySQL Migration Toolkit | Can't repeat (7067 days) | S1 | Release 5.0.X | Windows (Windows, Linux) | Any | Tables in SQL Server having composite foreign keys not migrated |
49173 | 2009-11-28 3:26 | 2011-02-16 23:44 | MySQL Server: Errors | Closed (5573 days) | S2 | 5.1.30-community | Windows (xp media center sp3) | Any | create view fails: MySQL error 1060 "duplicate column name" |
98976 | 2020-03-17 15:35 | 2020-03-18 7:08 | MySQL Server: Information schema | Verified (1810 days) | S3 | 8.0.19, 5.7.29 | Debian (mysql:8.0.19 from Docker) | x86 | Case of referenced column of foreign key not corrected on import |
31239 | 2007-09-27 13:29 | 2008-02-25 17:17 | MySQL Cluster: Cluster (NDB) storage engine | Closed (6215 days) | S2 | 5.1.22-rc, 5.0.50 | Other (ICC / IA64) | Any | Test "ndb_views" returns NDB error 4259 "Invalid set of range scan bounds" |
71923 | 2014-03-04 12:23 | 2014-07-17 17:29 | Connector / J | Closed (3881 days) | S3 | 5.1.29 | Any | Any | Incorrect generated keys if ON DUPLICATE KEY UPDATE not exact |
99575 | 2020-05-14 15:26 | 2023-02-09 20:02 | Connector / Python | Closed (752 days) | S3 | 8.0.20, 8.0.25 | Ubuntu (20.04) | ARM | insert into t (c1,...) values(%s,...) as v on duplicate key update c1=v.c1 slow |
24601 | 2006-11-26 17:04 | 2016-01-03 20:45 | MySQL Server: InnoDB storage engine | No Feedback (6640 days) | S2 | 5.0.26 | MacOS (Mac OS X 10.4.8) | Any | MySQLd crashes upon creation of an index |
47955 | 2009-10-09 18:59 | 2016-02-25 12:24 | MySQL Cluster: Cluster (NDB) storage engine | Closed (5590 days) | S2 | mysql-5.1-telco-6.3 | Any | Any | UPDATEs using indexes that modify no rows return incorrect found rows |
21653 | 2006-08-15 12:06 | 2006-08-26 10:00 | MySQL Server | Duplicate (6763 days) | S2 | 5.0.19 | Linux (SuSE 10.0) | Any | Mysql appears to hang at bin log file rotation (not every rotation) |
78262 | 2015-08-28 15:19 | 2015-12-07 18:51 | MySQL Server: InnoDB storage engine | Closed (3373 days) | S5 | 5.6.26 | Any (CentOS release 6.6) | Any | Adding indexes on empty table is slow with large innodb_sort_buffer_size. |
26276 | 2007-02-12 6:07 | 2015-03-15 20:45 | MySQL Server: Errors | No Feedback (6565 days) | S2 | 5.0.26 | Linux (linux) | Any | Duplicate entry |
38391 | 2008-07-26 13:57 | 2008-07-27 16:19 | MySQL Workbench | Duplicate (6062 days) | S3 | 5.0.23 SE | Windows | Any | Synchronize after Forward enginieer creates ALTER statements every time |
67526 | 2012-11-08 18:51 | 2019-05-07 21:37 | MySQL Server: InnoDB storage engine | Closed (2126 days) | S3 | 5.5.28, 5.5.29, 5.7.0 | Linux (Debian/AMD64 6.0.5) | Any | Duplicate key error on auto-inc PK with mixed auto_increment_increment clients |
7975 | 2005-01-17 22:56 | 2005-04-18 10:22 | MySQL Server: InnoDB storage engine | Closed (7258 days) | S3 | 4.1.9, official 686 binary | Linux (debian amd64 pure64) | Any | deadlock without any locking, simple select and update |
67914 | 2012-12-16 10:36 | 2013-01-19 1:00 | MySQL Server | No Feedback (4426 days) | S2 | 5.5.20 | Linux (ubuntu) | Any | Timestamp auto update column not updated on each update statement |
37560 | 2008-06-20 22:56 | 2008-07-31 18:01 | MySQL Server: General | Closed (6058 days) | S3 | 5.0.45-community-log | Linux | Any | Autoincrement should not increment on duplicate key condition |
68446 | 2013-02-20 23:36 | 2013-02-22 14:56 | MySQL Server: DML | Closed (4391 days) | S3 | 5.5.29 | Any | Any | insert on duplicate key update with null autoincremented PK uses wrong pk value |
17744 | 2006-02-27 16:52 | 2006-03-24 13:56 | MySQL Server: Partitions | Closed (6918 days) | S1 | 5.1 | Any | Partitions: InnoDB, Trigger, rotten table leads to wrong result sets | |
80505 | 2016-02-25 9:43 | 2016-02-25 14:53 | MySQL Server: Optimizer | Duplicate (3293 days) | S5 | 5.7.11 | Windows | Any | mysql server 5.7.11 view performance issue |
44904 | 2009-05-15 14:19 | 2018-02-10 17:27 | MySQL Server: DML | Can't repeat (2577 days) | S3 | 5.0, 5.1 | Windows (XP SP3) | Any | LIMIT IN INSERT ... DUPLICATE KEY UPDATE DIFFER IN THE SMPLE LIMIT |
65889 | 2012-07-13 0:21 | 2012-07-16 10:18 | MySQL Server: InnoDB storage engine | Verified (4615 days) | S3 | <=5.5 | Any | Any | Appended primary key stored inefficiently in unique surrogate keys |
110717 | 2023-04-18 15:17 | 2023-09-13 13:01 | Connector / NET | Closed (544 days) | S2 | 8.0.33 | Windows (10) | Any | Opening two MySqlConnections simultaneously can crash |
32139 | 2007-11-06 9:11 | 2007-12-12 9:39 | MySQL Server | No Feedback (6290 days) | S2 | 5.0.45 | Linux (ubuntu 7.10) | Any | Computing crc32(group_concat(...)) on a very loaded table doesn't give result ok |
112587 | 2023-10-02 13:29 | 2023-10-17 9:58 | MySQL Server: Documentation | Closed (503 days) | S3 | 8.0 | Linux | x86 | Change in MySQL error message format for 1062 Duplicate Entry from v5.7 to v8.0 |
2556 | 2004-01-29 8:21 | 2004-03-06 12:31 | MySQL Server: Replication | No Feedback (7666 days) | S2 | 4.0.17 | Linux (Mandrake linux 9.2) | Any | Error in Log_event::read_log_event(): 'Event too big', data_len: 808333356, eve |
17385 | 2006-02-14 15:39 | 2006-02-22 18:46 | MySQL Server | Closed (6948 days) | S1 | 5.1.7 src | Any | duplicate key error interchangeble refers to attribute name name and number | |
57868 | 2010-10-31 7:07 | 2011-02-16 23:44 | MySQL Server: Errors | Unsupported (5235 days) | S2 | 4.0.27 | Linux (suse with kernel 2.6.16.60-0.21) | Any | replication,record error in log but the slave not stop. |
39432 | 2008-09-13 12:50 | 2011-02-16 23:43 | MySQL Server: Documentation | Closed (5755 days) | S3 | ndb-6.2+ | Any (debian) | Any | slave stops if master does insert ... on duplicate key update |
65678 | 2012-06-19 21:56 | 2012-06-30 10:09 | Connector / Python | Closed (4628 days) | S3 | 0.3.2-dev | Any | Any | On duplicate key UPDATE VALUE fails regex |
18808 | 2006-04-05 14:25 | 2013-10-06 20:45 | MySQL Cluster: Cluster (NDB) storage engine | Duplicate (6890 days) | S3 | 5.1.9 | Linux (Linux 32 Bit OS) | Any | "Rowid already allocated" Error duing update and not during node recovery |
87300 | 2017-08-03 10:18 | 2017-11-09 11:24 | Shell General / Core Client | Closed (2670 days) | S2 | mysqlsh Ver 1.0.10 for Linux on x86_64 | Any | Any | mysql-shell dba.checkInstanceConfiguration() |
58637 | 2010-12-01 19:44 | 2014-06-25 14:34 | MySQL Server: Replication | Closed (4699 days) | S2 | 5.1+, 5.0, 5.6.1 | Any | Any | Mark INSERT...ON DUPLICATE KEY UPDATE unsafe when there is more than one key |
54182 | 2010-06-02 13:33 | 2016-09-08 5:54 | MySQL Cluster: Replication | Can't repeat (3097 days) | S2 | mysql-5.1-telco-6.3 | Linux (debian etch) | Any | Unique constraint make the replication crash |
54560 | 2010-06-16 18:58 | 2011-02-16 23:44 | MySQL Server | Closed (5367 days) | S3 | 5.1, 4.1, 5.0, 5.6.99 | Any | Any | Docs for REPLACE are not accurate |
16630 | 2006-01-19 12:47 | 2007-03-06 19:42 | MySQL Server: Optimizer | Closed (6571 days) | S2 | 4.1 | Any | error, when INSERT t1 SELECT ... FROM t1 ON DUPLICATE | |
87352 | 2017-08-09 8:17 | 2017-08-09 9:37 | MySQL Cluster: Cluster (NDB) storage engine | Verified (2762 days) | S3 | 7.5.7 | Any | Any | "ndb_restore --print-sql-log" includes unnecessary SQL |
22006 | 2006-09-05 0:09 | 2006-09-05 0:20 | MySQL Server | Not a Bug (6753 days) | S2 | 5.0.24 | Windows (MS Server 2003) | Any | Simple math using floats yielding bad precision results. |
61213 | 2011-05-18 9:49 | 2014-06-10 7:08 | Connector / J | Closed (3937 days) | S2 | 5.1.16 | Any | Any | ON DUPLICATE KEY UPDATE breaks generated key list when extended INSERT is used |
1796 | 2003-11-10 11:40 | 2003-12-19 6:46 | MySQL Server | Closed (7744 days) | S1 | 4.0.16 | Any | "IN" Problem | |
43932 | 2009-03-28 18:04 | 2011-02-16 23:43 | MySQL Server: MyISAM storage engine | Closed (5770 days) | S1 | 5.1.32 | Windows (64-bit) | Any | myisam index corruption with large index and large key_buffer_size |
95678 | 2019-06-06 21:22 | 2019-07-08 12:38 | MySQL Server: Optimizer | Can't repeat (2064 days) | S2 | 5.6.33 | Ubuntu | x86 | query gives empty result when using index_merge |
38434 | 2008-07-29 19:15 | 2012-05-18 20:19 | MySQL Server: DDL | Verified (6052 days) | S1 | 5.0.51b-community-nt MySQL Community Ed, 5.0, 5.1 BZR | Any (Linux, MS Windows xp) | Any | unique key index length |
42994 | 2009-02-18 21:47 | 2022-04-10 20:45 | MySQL Server: InnoDB storage engine | Duplicate (5855 days) | S2 | 5.1.30, 5.1.31 | Any | Any | REPLACE INTO results in a DUPLICATE KEY error on the AUTO_INCREMENT primary key |
97027 | 2019-09-26 10:02 | 2021-01-15 16:47 | MySQL Server: Row Based Replication ( RBR ) | Verified (1507 days) | S2 | 5.7.* | Any | x86 | Bulk insert with ON DUPLICATE KEY UPDATE breaks replicaiton |
59042 | 2010-12-19 18:44 | 2010-12-19 18:44 | MySQL Server: Security: Privileges | Open | S4 | 5.1.52 | Any | Any | INSERT ... ON DUPLICATE KEY UPDATE shouldn;t need UPDATE access to key columns |
42309 | 2009-01-23 18:17 | 2011-02-16 23:43 | Connector / J | Closed (5877 days) | S3 | 5.1 | Any | Any | Statement.getGeneratedKeys() returns 2 keys when using ON DUPLICATE KEY UPDATE |
58086 | 2010-11-09 15:09 | 2011-11-30 18:40 | MySQL Server: Documentation | Closed (4841 days) | S3 | 5.1 | Any | Any | auto_inc in InnoDB have INSERT ... ON DUPLICATE KEY UPDATE != UPDATE |
43842 | 2009-03-24 20:19 | 2013-01-14 9:25 | MySQL Server: Federated storage engine | Won't fix (4430 days) | S4 | 5.0 | Any | Any | Support for ON DUPLICATE KEY UPDATE with FEDERATED |
53871 | 2010-05-21 2:57 | 2011-02-16 23:44 | MySQL Server: Documentation | Closed (5399 days) | S3 | 5.1 | Any | Any | X lock is taken by innodb on duplicate key error, insert on duplicate key update |
3276 | 2004-03-23 16:58 | 2004-03-26 2:33 | MySQL Server: MyISAM storage engine | Can't repeat (7646 days) | S1 | 4.0.16 | Linux (Redhat ES 3) | Any | Deadlock with MyISAM |
21000 | 2006-07-12 12:49 | 2006-07-17 11:07 | MySQL Query Browser | Closed (6803 days) | S1 | 1.1.20 | Windows (Windows XP) | Any | Stored proc crashes Query Browser & Admin |
34253 | 2008-02-02 20:20 | 2008-02-03 17:28 | MySQL Workbench | Not a Bug (6237 days) | S3 | 5.012.OSS Beta | Windows (XP ) | Any | import sql workbech script generates errno 121 |
116815 | 2024-11-28 3:51 | 2024-12-04 17:38 | MySQL Server: InnoDB storage engine | Analyzing (88 days) | S2 | 8.0.30 | Any | Any | INSERT locks primary key supremum after secondary index duplicate key collision |
38239 | 2008-07-19 9:46 | 2008-07-31 1:40 | MySQL Workbench | Not a Bug (6058 days) | S2 | 5.0.23 OSS Rev. 3198 | Windows (Vista) | Any | Error importing 'Forward Engineer SQL CREATE Script' - With constraints |
33025 | 2007-12-05 21:54 | 2007-12-07 18:08 | MySQL Server: Replication | Duplicate (6295 days) | S2 | 5.0.45 | Linux | Any | Replication breaks on "on duplicate key update": ids on master & slave differ |
51055 | 2010-02-10 10:43 | 2011-02-16 23:44 | MySQL Server: Replication | Closed (5368 days) | S3 | mysql-5.1 | Any | Any | Replication failure on duplicate key + traditional SQL mode |
27672 | 2007-04-05 16:35 | 2007-07-29 6:36 | MySQL Server: General | No Feedback (6426 days) | S3 | 5.0.37 Community Edition | Linux (Fedora 5 64-bit) | Any | insert on duplicate key update sometimes delayed |
28800 | 2007-05-31 9:16 | 2007-05-31 10:36 | MySQL Server: Stored Routines | Can't repeat (6485 days) | S2 | 5.0.37-community-nt | Windows (XP SP2) | Any | ON DUPLICATE KEY UPDATE doesn't run triggers |
44976 | 2009-05-20 9:09 | 2011-02-16 23:43 | MySQL Server: Replication | Duplicate (5294 days) | S2 | 5.0.77 | Any | Any | Incorrect INSERT_ID in binary log |
66540 | 2012-08-25 20:04 | 2013-01-23 1:00 | MySQL Server: DML | No Feedback (4422 days) | S4 | Any | Any | Redundant coding in ON DUPLICATE KEY UPDATE | |
390 | 2003-05-07 9:14 | 2003-05-13 11:10 | MySQL Server | Closed (7964 days) | S3 | 4.0.13 | Any (All) | Any | Discrepancy with ISO about primary key and NOT NULL (error 1171) |
9636 | 2005-04-05 6:45 | 2005-05-15 23:05 | MySQL Server | Can't repeat (7231 days) | S2 | 5.0.3 rpm | Linux (Linux Fedore Core 2) | Any | INSERT INTO table from a complex View |
86725 | 2017-06-16 6:59 | 2017-10-31 13:08 | MySQL Server: DDL | Closed (2679 days) | S3 | 5.7 5.7.17, 5.7.18 | Any | Any | Behavior is different. "ADD KEY" and "ADD UNIQUE KEY" for the TEXT columns |
26069 | 2007-02-05 5:24 | 2012-05-18 20:19 | MySQL Server: Falcon storage engine | No Feedback (6503 days) | S2 | 5.2.2 (20070204 tree) | Linux (ubuntu 6.06 x86_64) | Any | duplicate entries for unique keys (incl primary) |
24079 | 2006-11-08 9:39 | 2006-12-07 22:31 | MySQL Server: Falcon storage engine | Closed (6660 days) | S1 | 5.2 | Any | Any | strange errors around INSERT getting duplicate key, but one row is inserted |
4312 | 2004-06-28 17:59 | 2004-11-18 17:25 | MySQL Cluster: Cluster (NDB) storage engine | Closed (7409 days) | S2 | 4.1 | Linux (Linux) | Any | ndb table, wrong behaviour on insert .. on duplicate key .. |
10884 | 2005-05-26 14:10 | 2005-05-26 14:47 | MySQL Server | Duplicate (7220 days) | S2 | 5.0.4-nt | Windows (Windows XP sp2) | Any | Insert ... on duplicate key update does not recognize table alias |
89385 | 2018-01-24 15:14 | 2020-10-06 13:05 | MySQL Server | Not a Bug (1608 days) | S4 | Any | Any | INSERT IGNORE DUPLICATE KEY | |
30915 | 2007-09-08 14:33 | 2008-01-08 20:32 | MySQL Server: Documentation | Closed (6263 days) | S3 | 5.0.41 | FreeBSD (6.2) | Any | on duplicate key update: needs update privileges for primary key |
39352 | 2008-09-09 22:07 | 2011-05-12 6:42 | Connector / J | Closed (5987 days) | S3 | 5.0.x, 5.1.x | Any | Any | INSERT ON DUPLICATE returns 1 instead of 0 when nothing is changed |
61962 | 2011-07-23 21:43 | 2011-08-06 12:44 | MySQL Server | Not a Bug (4957 days) | S1 | 5.5.14 | Any (Tested on 5.5.8 and 5.5.14) | Any | 'ON DUPLICATE KEY UPDATE' bug incrementing ID (auto increment field) on Updates |
65130 | 2012-04-27 12:12 | 2013-05-23 19:20 | MySQL Cluster: Cluster (NDB) storage engine | Closed (4301 days) | S3 | 7.1.x, 7.2.5 | Linux | Any | "Transaction already aborted" hides real error msg on INSERT ... ON DUP UPDATE |
13571 | 2005-09-28 14:22 | 2006-04-14 14:45 | MySQL Server: Compiling | Closed (6897 days) | S3 | 5.0.13-rc, 5.0.14-rc | IBM AIX (AIX 5.2) | Any | Compiling problems on AIX |
71916 | 2014-03-03 16:52 | 2016-10-26 13:43 | MySQL Server: Documentation | Closed (3049 days) | S3 | 5.6 | Any | Any | Manual does NOT explain locks set for UPDATE ... WHERE PK='const' properly |
107026 | 2022-04-14 16:17 | 2022-04-15 12:13 | MySQL Server: DML | Closed (1052 days) | S3 | 5.7.36 | Debian | x86 | Update performs full table scan due to too many indexes |
18245 | 2006-03-15 2:23 | 2006-04-23 16:05 | MySQL Server | No Feedback (6888 days) | S3 | 4.1.16 | Linux (Linux) | Any | Slave executes query from old binlog following master binlog rotation |
41263 | 2008-12-05 15:18 | 2011-02-16 23:43 | MySQL Server: Replication | Duplicate (5823 days) | S2 | 5.1.30 | Linux | Any | Replication breaks after 'INSERT ... ON DUPLICATE UPDATE ...' |
30256 | 2007-08-06 14:27 | 2007-08-06 15:15 | MySQL Server | Can't repeat (6418 days) | S2 | 5.0.45 | Any | Any | Query cache not emptied after a INSERT ... ON DUPLICATE KEY UPDATE |
54914 | 2010-06-30 13:08 | 2011-02-16 23:44 | MySQL Server: InnoDB storage engine | Closed (5241 days) | S5 | 5.5.5 | Any | Any | InnoDB: performance drop with innodb_change_buffering=all |
21403 | 2006-08-01 19:21 | 2011-02-16 23:43 | MySQL Server: Errors | Verified | S4 | all | Any (all) | Any | more specific SQL states for 23nnn |
112852 | 2023-10-27 7:42 | 2023-11-06 11:25 | MySQL Server: DML | Verified (482 days) | S3 | 8.0 | Linux | x86 | insert and insert onduplicate are executed concurrently, data update error |
39248 | 2008-09-04 15:06 | 2009-01-09 15:28 | MySQL Server: Maria storage engine | Closed (5896 days) | S3 | 5.1-maria, 6.0-bk | Linux | Any | Maria: INSERT ON DUPLICATE KEY UPDATE gives error if using a view |
56593 | 2010-09-06 12:20 | 2010-09-06 16:24 | MySQL Server: Parser | Not a Bug (5291 days) | S3 | 5.1.41 | Linux | Any | scope issue in "ON DUPLICATE KEY UPDATE" when using aggregation functions |
71672 | 2014-02-11 15:02 | 2014-07-16 22:08 | Connector / J | Closed (3882 days) | S5 | 5.1.29 | Any | Any | Every SQL statement is checked if it contains "ON DUPLICATE KEY UPDATE" or not |
26464 | 2007-02-17 18:25 | 2007-03-15 2:54 | MySQL Server: Merge storage engine | Closed (6562 days) | S2 | 4.1.21, 5.0.36BK, 5.1.16BK, 5.2.4BK | Any (*) | Any | insert delayed + update + merge = corruption |
87796 | 2017-09-19 5:11 | 2021-09-01 13:10 | MySQL Server: Replication | Closed (1553 days) | S1 | 5.7.19 | Linux (Linux localhost 3.10.0-327.28.2.el7.x86_64 #1 SMP Wed Aug 3 11:11:39 UTC 2016 x) | Any | Commit_order_manager can't terminate MTS worker properly when deadlock happens |
11039 | 2005-06-02 15:07 | 2005-06-16 17:11 | MySQL Server: InnoDB storage engine | Closed (7199 days) | S3 | 5.0 | Any (any) | Any | InnoDB: Warning: using a partial-field key prefix in search. |
16635 | 2006-01-19 14:52 | 2007-08-03 1:44 | MySQL Server: Embedded Library ( libmysqld ) | Closed (6421 days) | S3 | 4.1.17 | Any (all Unix) | Any | Error messages wrong: absolute path names, "%s" format code |
32472 | 2007-11-17 17:17 | 2007-11-20 13:02 | MySQL Server: Errors | Closed (6312 days) | S3 | 5.0.45 | Linux (Fedora 6 2.6.22.9-61) | Any | Enabling keys after inserts: Warning: Enabling keys got errno 22 |
39786 | 2008-10-01 17:56 | 2012-10-12 10:59 | MySQL Server: Optimizer | Closed (4524 days) | S3 | 5.1.26 | Any | Any | Explain doesn't show key with order by in derived table. |
80506 | 2016-02-25 10:41 | 2016-03-26 1:00 | MySQL Workbench | No Feedback (3264 days) | S1 | 6.3.6 | Any | Any | Could not alter table |
106188 | 2022-01-17 20:54 | 2022-09-05 13:56 | MySQL Server: Packaging | Closed (909 days) | S1 | 8.0, 5.7 | Any | Any | The MySQL GPG key seems to be incorrect |
2725 | 2004-02-11 23:55 | 2004-03-05 0:31 | MySQL Server | Can't repeat (7667 days) | S2 | 4.0.17 | Tru62 | Any | KEY desc_idx (description(100)) being treated as UNIQUE KEY on Tru64 |
12299 | 2005-08-01 15:39 | 2005-09-02 7:54 | MySQL Server | No Feedback (7121 days) | S3 | 4.0.20 | Windows (win2000) | Any | show create tables lost referense information accidentally |
13429 | 2005-09-23 15:19 | 2005-10-06 12:06 | MySQL Server: InnoDB storage engine | Not a Bug (7087 days) | S3 | 5.0, 5.0.12-nt | Linux (Linux, Windows) | Any | Duplicate FOREIGN KEYs are allowed |
108729 | 2022-10-10 16:06 | 2022-10-14 13:28 | MySQL Server: FULLTEXT search | Can't repeat (871 days) | S3 | 8.0.30 | Linux | x86 | Adding fulltext index results in duplicate entry error for unrelated key |
44464 | 2009-04-24 18:05 | 2011-02-16 23:43 | MySQL Workbench | No Feedback (5739 days) | S1 | 5.0.30 | Windows | Any | Workbench SE Synch with collation difference fails |
12946 | 2005-09-02 8:55 | 2005-10-05 11:27 | MySQL Server | No Feedback (7088 days) | S2 | 4.0.18 | Linux (Red Hat Linux release 7.3 (Valha) | Any | Duplicate key for record |
14695 | 2005-11-07 9:53 | 2005-11-09 0:19 | MySQL Server | Can't repeat (7053 days) | S3 | 4.1.4 | Linux (Linux ibm171.iq2003.com 2.6.9-11) | Any | replication fail when reconnection |
33029 | 2007-12-06 0:59 | 2008-04-05 7:34 | MySQL Server: Replication | Closed (6175 days) | S2 | 5.0.52 / 5.1.22 | Any | Any | 5.0 to 5.1 replication fails on dup key when inserting using a trig in SP |
89938 | 2018-03-07 3:13 | 2018-07-11 9:47 | MySQL Server: Group Replication | Closed (2426 days) | S2 | 5.7.20,8.0.4 | Any | Any | Rejoin old primary node may duplicate key when recovery |
116503 | 2024-10-30 6:55 | 2024-10-31 14:25 | MySQL Server | Not a Bug (122 days) | S3 | 8.0 | Any | Any | duplicate-key error will hold gap lock when there are multi unique keys |
6978 | 2004-12-03 9:07 | 2004-12-03 11:36 | MySQL Server | Not a Bug (7394 days) | S3 | 4.1.8 & 5.0.3 | Linux (Linux 2.4.21-99 smp) | Any | Errors on multi table update and delete |
10886 | 2005-05-26 14:59 | 2005-06-22 2:36 | MySQL Server: Optimizer | Closed (7193 days) | S2 | 4.1.12 | Linux (Linux) | Any | INSERT ... SELECT ... ON DUPLICATE KEY UPDATE produces bad results |
34382 | 2008-02-07 14:55 | 2008-03-07 15:05 | MySQL Server: General | No Feedback (6204 days) | S3 | 5.0.32 | Any (Sorry none) | Any | Error when using ON DUPLICATE KEY UPDATE table1.field1 = table2.field1,.... |
36898 | 2008-05-22 22:24 | 2008-05-25 10:04 | MySQL Server: DML | Not a Bug (6125 days) | S3 | 5.0.51 | Any | Any | INSERT ... ON DUPLICATE KEY UPDATE seem to compute wrong, if a new row is insert |
40673 | 2008-11-12 19:10 | 2011-02-16 23:43 | Connectors: DBD::mysql ( Perl ) | No Feedback (5923 days) | S3 | 5.0.22 | Linux | Any | Perl affected row count incorrect for certain cases of ON DUPLICATE KEY UPDATE |
103417 | 2021-04-22 4:22 | 2022-11-25 23:34 | Connector / J | Not a Bug (828 days) | S3 | 8.0.24 | MacOS (big sur) | Any | jdbc . have an error in your SQL syntax |
92642 | 2018-10-02 19:08 | 2018-10-02 20:34 | MySQL Workbench | Duplicate (2343 days) | S2 | 8.0.12 | MacOS (macOS 10.13.x High Sierra x86_64) | Any | Results Grid does now show |
43311 | 2009-03-02 20:23 | 2011-02-16 23:43 | MySQL Server: General | Duplicate (5812 days) | S2 | 5.0.77 | Any | Any | Wrong number of affected rows returned for insert on duplicate key |
72162 | 2014-03-29 20:02 | 2014-04-29 20:07 | MySQL Server: Stored Routines | Closed (3960 days) | S2 | 5.5.35-0ubuntu0.12.04.2 (Ubuntu) | Linux (Linux 3.2.0-60-generic-pae i686) | Any | Insert fail caused by trigger |
8563 | 2005-02-17 6:30 | 2005-02-17 19:50 | MySQL Server: Replication | Not a Bug (7318 days) | S2 | 4.1.9 | Linux (Linux (RHEL 3, x86)) | Any | Replication of InnoDB table fails with Error_code: 1062 intermittently |
45163 | 2009-05-28 15:10 | 2014-02-18 15:53 | MySQL Server: Documentation | Closed (4030 days) | S3 | 5.1.30, 5.0.70 | Any | Any | Behavior different then expected from manual - ALTER w/ FK |
55157 | 2010-07-10 19:23 | 2011-02-16 23:44 | MySQL Workbench: Modeling | Duplicate (5347 days) | S1 | 5.2.25 | Windows | Any | Attempt to add existing foreing key |
43795 | 2009-03-23 5:28 | 2009-03-23 6:15 | MySQL Server: InnoDB storage engine | Not a Bug (5823 days) | S2 | 5.1.32-community | Windows | Any | Autoincrement increased by 2 on duplicate key condition |
40147 | 2008-10-19 17:29 | 2008-11-21 7:12 | MySQL Server: InnoDB storage engine | No Feedback (5945 days) | S1 | 5.0.18 | Linux (SuSe 10.1) | Any | InnoDB: All tables / databases Lock / Global Lock ??? - Please help |
79617 | 2015-12-12 15:16 | 2019-12-12 20:36 | MySQL Server: Locking | Closed (1907 days) | S3 | 8.0.18 | Windows (10) | Any | Foreign key causing deadlock for UPDATE together with simple transaction |
86205 | 2017-05-06 23:13 | 2017-06-10 1:00 | MySQL Server: Optimizer | No Feedback (2823 days) | S3 | 5.6/5.7 | Windows | Any | optimizer index using select where column in select |
3587 | 2004-04-28 12:30 | 2004-05-02 18:14 | MySQL Server | Closed (7609 days) | S2 | 5.0.0alpha | Windows (WinXP) | Any | Server crushes after executing query with connecting two subquery on two fields |
8924 | 2005-03-03 15:38 | 2005-04-12 15:16 | MySQL Server | Closed (7264 days) | S3 | 5.0.3 | Other (QNX) | Any | 'Explain' shows different strategy |
18596 | 2006-03-28 23:38 | 2012-05-18 20:19 | MySQL Cluster: Cluster (NDB) storage engine | Duplicate (6907 days) | S2 | 5.1.9 | Linux (Linux 32 Bit OS) | Any | binlog schema event auto push causes mysqld errors |
18644 | 2006-03-30 10:00 | 2006-05-26 20:41 | MySQL Server: Documentation | Closed (6855 days) | S2 | 5.0.18 | Linux (SuSE linux 9.2 pro) | Any | Documentation Errors for Create Table syntax |
25596 | 2007-01-12 21:13 | 2007-02-20 20:30 | MySQL Server: InnoDB storage engine | Closed (6585 days) | S2 | 5.0.32, 5.0.36-bk | Linux (Linux, Windows, Mac OS X 10.4.8) | Any | InnoDB Alter Table Failures |
32416 | 2007-11-15 17:15 | 2008-07-24 11:57 | MySQL Server: InnoDB storage engine | Not a Bug (6065 days) | S1 | 5.0.27, 5.0.37, 5.1.22 | Linux | Any | Foreign key constraint violation under concurrent load |
36845 | 2008-05-21 8:05 | 2008-06-27 16:37 | MySQL Server: Partitions | No Feedback (6092 days) | S2 | 5.1.23-rc-community | Linux (2.6.9-67.0.4.ELsmp #1 SMP Sun Feb 3 07:06:14 EST 2008 x86_64 x86_64 x86_64 GNU/Linux) | Any | Partition with composite keys and joins |
60850 | 2011-04-13 10:13 | 2011-04-28 17:22 | MySQL Server: MyISAM storage engine | Can't repeat (5057 days) | S2 | 5.5.10 | FreeBSD (amd64) | Any | myisamchk: Error reading file '/storage/5/tmp/STVhtaM4' (Errcode: 22) |
70115 | 2013-08-22 3:19 | 2013-10-01 1:00 | MySQL Server: Pluggable Authentication | No Feedback (4171 days) | S1 | 5.6.12 | Linux (OpenSUSE 12.3) | Any | MySQL corrupts sha256 password RSA keys on crash |
75287 | 2014-12-22 13:44 | 2015-03-30 15:58 | Connector / Python | Closed (3659 days) | S1 | 2.0 | Any | Any | Python does not work with HASH sahrding in MySQL Fabric |
99494 | 2020-05-08 21:53 | 2020-07-06 14:16 | Connector / NET | Can't repeat (1700 days) | S2 | 8.0 | Windows (10) | x86 | Unable to remove connector 8.0 .NET |
20494 | 2006-06-16 6:02 | 2006-06-22 12:51 | MySQL Server: Documentation | Closed (6828 days) | S2 | 5.1 | Any (All) | Any | Partitioning chapter contains dated info |
106818 | 2022-03-24 11:23 | 2022-06-07 2:29 | MySQL Server: Replication | Verified (999 days) | S2 | 5.7,8.0, 5.7.37 | Any | Any | Replication may fail when XA transactions use replace into statements |
39239 | 2008-09-04 11:56 | 2008-09-05 10:30 | MySQL Server: General | Closed (6022 days) | S2 | 5.1.26 | Linux (CentOS 5.2) | Any | Temporary server hang |
13108 | 2005-09-10 21:43 | 2005-12-18 5:20 | MySQL Server | Closed (7014 days) | S2 | 5.0.12/BK source 5.0 | MacOS (Mac OSX 10.4.2, Darwin 8.2.0) | Any | ALTER TABLE does not work on FEDERATED tables |
75253 | 2014-12-18 9:06 | 2014-12-22 9:36 | MySQL Server | Not a Bug (3723 days) | S3 | 5.5.32-log | Linux (CentOS) | Any | ON DUPLICATE KEY UPDATE not working when auto_increment reaches MAX_INT |
28842 | 2007-06-01 17:33 | 2007-06-18 15:08 | MySQL Server: Errors | Closed (6467 days) | S2 | 5.1-bk | Any | Any | Different 'duplicate key' error code between 5.0 and 5.1 |
36411 | 2008-04-29 19:46 | 2011-02-16 23:43 | MySQL Server: InnoDB storage engine | Closed (5371 days) | S3 | 5.1.24, 5.1.25 | Any | Any | "Failed to read auto-increment value from storage engine" in 5.1.24 auto-inc |
60808 | 2011-04-08 15:06 | 2011-04-08 16:35 | MySQL Server: General | Duplicate (5077 days) | S2 | 5.5.11, 5.1.54, 5.1.41 | Any (win7 64bit, ubuntu 10.04 64 bit) | Any | Duplicate entry for key 'group_key'; Can't write, duplicate key in table |
89196 | 2018-01-11 19:16 | 2018-01-19 9:50 | MySQL Server: Replication | Verified (2599 days) | S4 | 5.7.20, 8.0.3 | Any | Any | Please add GTID in applier error messages. |
12283 | 2005-07-30 7:45 | 2011-02-16 23:43 | MySQL Server: DML | Won't fix (5189 days) | S4 | 4.0.21-Max | Linux (SuSE Linux 9.2 pro) | Any | Multiple INSERT syntax? |
12631 | 2005-08-17 21:20 | 2005-08-18 22:45 | MySQL Server | Closed (7136 days) | S2 | 5.0.10 | Windows (Win XP) | Any | INSERT..ON DUPLICATE KEY UPDATE gives errror 1110 (42000) although it shouldn't |
27954 | 2007-04-19 14:23 | 2007-05-10 18:07 | MySQL Server: General | Closed (6506 days) | S1 | 5.0.38 | Any | Any | INSERT ... ON DUPLICATE KEY UPDATE fails with large multi-insert |
46788 | 2009-08-18 14:58 | 2011-02-16 23:44 | Connector / J | Closed (5646 days) | S2 | 5.1.8 | Linux (Fedora 10) | Any | While using ON DUPLICATE KEY UPDATE on a batchRewriteStatements I get exception |
50413 | 2010-01-18 13:54 | 2018-11-30 13:16 | MySQL Server: InnoDB storage engine | Closed (4128 days) | S1 | 5.0.91,5.1.50,5.6.0 | Any | Any | insert on duplicate key update sometimes writes binlog position incorrectly |
61134 | 2011-05-11 14:32 | 2011-05-17 14:17 | Connector / J | Duplicate (5038 days) | S2 | 5.1.16 | Any | Any | bad row affected values with INSERT ON DUPLICATE KEY UPDATE |
100252 | 2020-07-18 0:51 | 2020-07-19 5:53 | Connector / J | Duplicate (1687 days) | S3 | 8.0.21 | Ubuntu | x86 | PreparedStatements with rewriteBatchedStatements does not translate aliases well |
31975 | 2007-10-31 7:36 | 2009-09-01 13:19 | MySQL Server: Command-line Clients | Not a Bug (5661 days) | S4 | mysql-connector-java-3.1.8-bin.jar | Any | Any | LOAD DATA LOCAL INFILE - Duplicate entry error should come |
58493 | 2010-11-25 13:32 | 2010-11-26 8:17 | MySQL Server: Charsets | Not a Bug (5210 days) | S3 | 5.1.53 | Any | Any | Rows get skipped as primary duplicates, when they are in fact not. |
113276 | 2023-11-29 5:55 | 2023-11-29 13:00 | MySQL Server | Can't repeat (459 days) | S3 | 8.0.24 | CentOS (7.9) | x86 | MYSQL does not respond after applications are inserted in batches |
72476 | 2014-04-28 23:42 | 2014-09-16 1:00 | MySQL Workbench | No Feedback (3821 days) | S1 | 6.1 | Windows (8.1 64-bit) | Any | Modifying in Workbench causes update trigger to modify all records instead of 1 |
6287 | 2004-10-27 14:41 | 2004-12-21 17:55 | MySQL Server: Replication | Closed (7376 days) | S2 | 4.0.21-log | Linux (Linux) | Any | Slave skips auto_increment values in Replication with InnoDB |
33658 | 2008-01-03 16:46 | 2018-06-24 20:45 | MySQL Workbench | Duplicate (6263 days) | S2 | 5.0.11 SE Beta Rev 2342 | Windows (XP 32 bit) | Any | Workbench Generates Primary Keys That Are Unnecessary and Can't Be Edited |
73925 | 2014-09-16 9:34 | 2014-09-16 11:22 | MySQL Server: InnoDB storage engine | Not a Bug (3820 days) | S2 | 5.5.27 | Windows (7 64 bit) | Any | INSERT INTO ... ON DUPLICATE KEY UPDATE not taking into account multiple column |
25853 | 2007-01-25 16:20 | 2007-06-20 1:01 | MySQL Server: MyISAM storage engine | Closed (6465 days) | S1 | 5.0.27,5.0.40BK, 5.1.18BK | Linux (Linux Fedora Core 5) | Any | key_cache_block_size=4MB causes table corruptions + duplicate key errors |
48029 | 2009-10-13 19:30 | 2011-02-16 23:44 | MySQL Server: InnoDB storage engine | No Feedback (5588 days) | S3 | 5.1.34 | Linux | Any | Deadlock between INSERT...ON DUPLICATE KEY... and DELETE on InnoDB |
68332 | 2013-02-10 16:34 | 2013-02-11 21:32 | MySQL Server: General | Can't repeat (4402 days) | S2 | 5.5.30,5.6.10 | Any | Any | Value for mysql_affected_rows() became 1 for ON DUPLICATE KEY after 5.5.15 |
81578 | 2016-05-24 18:38 | 2016-05-24 18:51 | MySQL Server: DML | Duplicate (3204 days) | S3 | 5.5.49 | Any | Any | INSERT ON DUPLICATE KEY UPDATE statement returning 1062 instead of 1452 |
6205 | 2004-10-21 19:56 | 2004-10-21 21:29 | MySQL Server: InnoDB storage engine | Not a Bug (7437 days) | S3 | 4.0.14 | Linux (linux RedHat 7.3) | Any | Update killed MySQL server |
28190 | 2007-05-02 1:43 | 2020-05-03 20:45 | MySQL Server | Duplicate (6430 days) | S3 | 5.0.37,5.1BK | Linux (Fedora Core release 4 (Stentz)) | Any | ON DUPLICATE KEY UPDATE updates the record even if values are identical |
90398 | 2018-04-12 4:16 | 2020-02-06 13:34 | MySQL Server: Optimizer | Closed (2124 days) | S2 | 5.7.17 EE, 5.7.22 | Any | Any | Duplicate entry for key '<group_key>' error |
46864 | 2009-08-22 7:05 | 2011-02-16 23:44 | MySQL Server: Replication | Closed (5646 days) | S3 | 5.1.38, 5.0, 5.1, next bzr | Any | Any | Incorrect update of InnoDB table on slave when using trigger with myisam table |
104238 | 2021-07-07 15:16 | 2021-07-08 6:23 | MySQL Server: Security: Privileges | Duplicate (1333 days) | S3 | 8.0.24 | Any | Any | Grants in prepare with 2 triggers on the same table |
8058 | 2005-01-20 23:03 | 2005-02-21 16:50 | MySQL Server | Can't repeat (7314 days) | S1 | 5.0.3 built today | Linux (Linux/x86) | Any | Crashes and out of memory in SQL parsing of stored procs |
94541 | 2019-03-04 9:32 | 2019-09-04 15:47 | MySQL Server: InnoDB storage engine | Closed (2006 days) | S2 | 5.7.25 | Any | Any | Assertion on import via Transportable Tablespace |
91823 | 2018-07-29 18:25 | 2018-10-28 22:02 | MySQL Server: InnoDB storage engine | Closed (2317 days) | S3 | 8.0.12 | Ubuntu (14.04) | x86 | innodb.innodb test leads to crash on MySQL 8.0.12 |
111703 | 2023-07-10 6:40 | 2023-07-15 1:58 | MySQL Server: Documentation | Not a Bug (596 days) | S3 | 8.0.33, 5.7.42 | Any | Any | INSERT ON DUPLICATE KEY locks INSERT if table have many PRIMARY and UNIQUE key |
30278 | 2007-08-07 16:47 | 2012-05-18 20:19 | MySQL Server: InnoDB storage engine | No Feedback (5638 days) | S5 | 5.1.20 | Any | Any | InnoDB: performance regression for update_with_key_prefix operation(mysql-bench) |
74218 | 2014-10-03 23:02 | 2019-10-29 15:02 | MySQL Cluster: Cluster (NDB) storage engine | Closed (1951 days) | S3 | 5.6.19-ndb-7.3.6 | Any | Any | Missing table name in error message 1022 |
2438 | 2004-01-18 16:42 | 2004-02-02 9:34 | MySQL Server | Closed (7699 days) | S2 | 4.1.1 | Linux (Mandrake Linux 9.2/WindowsXP) | Any | Runaway memory consumption |
12707 | 2005-08-21 23:33 | 2022-12-04 20:45 | MySQL Server: DDL | Verified (5870 days) | S4 | 4.0, 5.1 | Windows (Windows and Linux) | Any | The ON UPDATE and DEFAULT constructs need an Enahncement |
45901 | 2009-07-02 9:24 | 2009-07-02 14:03 | MySQL Server: InnoDB storage engine | Not a Bug (5722 days) | S3 | 5,1.30, 5.1.33, 5.1.35, 5.1.36 | Windows (XP) | Any | Cannot do SELECT FOR UPDATE with small amount of records. |
5434 | 2004-09-06 16:32 | 2004-09-06 20:24 | MySQL Server | Not a Bug (7482 days) | S2 | 4.0.15-max-debug | Windows (win2k) | Any | constraint name not honored for foreign keys |
10923 | 2005-05-27 17:12 | 2006-04-04 8:10 | MySQL Cluster: Cluster (NDB) storage engine | Closed (6907 days) | S4 | 5.1-wl2325 | Linux (Linux) | Any | Slave cluster not always updated properly from master cluster with two mysqld |
22520 | 2006-09-20 14:26 | 2012-05-18 20:19 | MySQL Server | Duplicate (6716 days) | S3 | 5.0.26-BK, 5.0.22-max, 1.2.3rc, 1.2.4rc | Linux (Linux, Mac OS X) | Any | tables without a primary key but with a unique index report it is a primary key |
26126 | 2007-02-06 21:20 | 2011-02-16 23:43 | MySQL Server: Errors | No Feedback (6063 days) | S2 | 4.1.22 | Linux (Linux, 2.6.9 kernel) | Any | "Unknown error" during a long running query. |
32948 | 2007-12-04 1:09 | 2007-12-13 10:07 | MySQL Server: Partitions | Closed (6289 days) | S2 | 5.1 | Any | Any | FKs allowed to reference partitioned table |
40801 | 2008-11-17 19:52 | 2009-05-15 12:56 | MySQL Server: Falcon storage engine | Closed (5770 days) | S3 | 6.0.8 | Any | Any | Falcon garbage collection can erase valid key values |
43637 | 2009-03-13 16:53 | 2009-03-18 12:51 | Connector / J | Not a Bug (5828 days) | S2 | 5.1.31-community-log | Linux (inux version 2.6.18-92.1.22.el5) | Any | Unknown type '246 in column 10 of 24 in binary-encoded result set |
72745 | 2014-05-26 4:28 | 2014-05-26 5:48 | MySQL Server: Optimizer | Verified (3933 days) | S2 | 5.5.37, 5.5.38 | Any | Any | Wrong Results When Using Intersect |
69699 | 2013-07-09 15:31 | 2013-07-10 5:21 | MySQL Server: InnoDB storage engine | Duplicate (4253 days) | S2 | 5.6.11 | Linux | Any | add foreign key error |
21085 | 2006-07-16 21:33 | 2006-07-27 6:14 | MySQL Server: Charsets | Not a Bug (6793 days) | S3 | 5.0.25_BK, 5.0.21 | Linux (Red Hat Enterprise Linux ES rele) | Any | database collate set overriden by specifying only character set on column |
38749 | 2008-08-12 11:39 | 2008-08-13 18:29 | MySQL Server: DML | Not a Bug (6045 days) | S1 | 5.0.51a-6 | Linux (debian lenny) | Any | Duplicate error on INSERT - primary key auto increment column |
43674 | 2009-03-16 12:42 | 2009-03-16 12:54 | MySQL Server: Charsets | Not a Bug (5830 days) | S2 | 6.0.10-alpha-debug | Linux (suse-linux-gnu on i686 (Source distribution)) | Any | Duplicate entry 'а' with utf8mb3, while the same with utf8 in 5.1 is working. |
46976 | 2009-08-28 15:00 | 2013-01-29 23:30 | MySQL Server: Documentation | Closed (4415 days) | S3 | 5.1.33 | Any | Any | Duplicate erro output different for 5.1.33 from dev article |
70409 | 2013-09-24 15:35 | 2014-05-28 5:45 | Connector / NET | Closed (3931 days) | S1 | 6.7.4 | Windows (server 2008) | Any | MySqlSessionStateStore : exception "Duplicate entry" |
82544 | 2016-08-11 14:36 | 2016-08-17 14:57 | MySQL Server: Documentation | Closed (3119 days) | S3 | 5.7.14 | Any | Any | Duplicate entry '' for key '<group_key>' while doing group by |
86053 | 2017-04-24 9:20 | 2018-10-21 20:45 | MySQL Server | No Feedback (2839 days) | S3 | 5.7.11 | Any | Any | MySQL 1062 –Duplicate entry for key without duplicate value |
98600 | 2020-02-14 11:48 | 2024-10-16 7:40 | MySQL Server: DML | Verified (1843 days) | S3 | 5.7,8.0, 5.7.29, 8.0.19 | Any | Any | Optimize table fails with duplicate entry on UNIQUE KEY |
101706 | 2020-11-21 16:51 | 2020-12-03 14:25 | MySQL Server: InnoDB storage engine | Closed (1550 days) | S3 | 8.0 | Any | Any | check table can't find duplicate error in table |
104144 | 2021-06-29 12:14 | 2021-06-30 13:18 | MySQL Server: DML | Verified (1342 days) | S2 | 8.0.25, 5.7.34, 5.6.51 | Any | Any | REPLACE INTO removes the row |
58864 | 2010-12-10 12:13 | 2011-07-19 15:09 | MySQL Server: Documentation | Closed (4975 days) | S4 | 5.1 | Any | Any | Clarify LAST_INSERT_ID() behavior on update by INSERT ON DUPLICATE KEY UPDATE |
107656 | 2022-06-25 13:55 | 2022-07-01 12:09 | MySQL Server | Not a Bug (975 days) | S3 | 5.7.29 | Linux | x86 | insert into on duplicate key update with PRIMARY cause a deadlock |
115741 | 2024-08-01 11:13 | 2025-01-21 12:46 | MySQL Server: Replication | Verified (207 days) | S1 | 8.0 | Any | Any | Slave stops with HA_ERR_KEY_NOT_FOUND with HASH_SCAN and index used to search fo |
52473 | 2010-03-30 12:51 | 2021-05-02 20:45 | MySQL Cluster: Replication | Verified (5426 days) | S3 | mysql-5.1-telco-6.3 | Any | Any | NDB inserts row when updating slave's empty table (with PK) |
71735 | 2014-02-16 12:59 | 2016-10-27 13:34 | MySQL Server: Documentation | Closed (3048 days) | S3 | 5.6 | Any | Any | Manual does not explain locks set by SELECT ... FOR UPDATE properly |
18276 | 2006-03-16 11:04 | 2006-03-23 16:16 | MySQL Server | Won't fix (6919 days) | S3 | 5.0.19 | IBM AIX (AIX 4.2.1) | Any | does not build (failure to link) on AIX |
2669 | 2004-02-06 17:21 | 2004-02-09 15:34 | MySQL Server: InnoDB storage engine | Not a Bug (7692 days) | S1 | 4.0.16 | Linux (Linux - Mandrake 9.0) | Any | Update fails for no reason - Incorrect "1062 = Duplicate entry" |
55222 | 2010-07-13 16:52 | 2019-05-15 10:40 | MySQL Server: InnoDB storage engine | Closed (5165 days) | S2 | 5.1.x, 5.1.49-bzr | Any (Windows 7, Mac OS X) | Any | Mysqldump table names case bug in REFERENCES clause |
82809 | 2016-08-31 7:20 | 2016-09-10 9:38 | MySQL Utilities | Verified (3095 days) | S3 | 1.6.4 | Red Hat | Any | mysqldbcompare output error SQL when 2 tables having different primary keys |
88111 | 2017-10-16 17:19 | 2019-05-17 19:22 | MySQL Server: DDL | Closed (2116 days) | S3 | 5.7, 8.0 | Any | Any | generated column not accept foreign key for column included |
47175 | 2009-09-07 13:25 | 2011-02-16 23:44 | MySQL Server: Row Based Replication ( RBR ) | Closed (5474 days) | S3 | 5.1,5.4 | Any | Any | failing INSERT, transaction, replication out of sync |
24302 | 2006-11-14 15:33 | 2006-11-15 10:48 | MySQL Server | Not a Bug (6682 days) | S2 | 4.1.21 | Windows (Windows) | Any | INSERT ...SELECT...ON DUPLICATE KEY not recognizing source field(s) |
27033 | 2007-03-11 14:09 | 2007-03-20 17:43 | MySQL Server | Closed (6557 days) | S2 | 5.0.37 | Windows (Windows 2003/Linux) | Any | LAST_INSERT_ID returns 0 on using INSERT... ON DUPLICATE KEY UPDATE ... |
27387 | 2007-03-23 4:08 | 2007-03-30 17:06 | MySQL Server: General | Not a Bug (6547 days) | S2 | All 5.0 and 5.1, 4.1, 5.2 | Any (All) | Any | Error checking is incorrect in INSERT ... ON DUPLICATE KEY UPDATE |
36920 | 2008-05-23 15:27 | 2008-10-31 13:03 | MySQL Server | Can't repeat (5966 days) | S1 | 5.1.x | Windows (XP32, VISTA64) | Any | Server (5.1.x) stops error Can't write; duplicate key in table 'C\Windows\temp' |
106240 | 2022-01-21 22:00 | 2022-03-29 22:25 | Connector / J | Closed (1069 days) | S3 | 8.0.25, 8.0.28 | Any | Any | StringIndexOutOfBoundsException when VALUE is at the end of the query |
72407 | 2014-04-20 20:47 | 2014-04-24 17:30 | MySQL Server: Locking | Not a Bug (3965 days) | S1 | 5.6.10, 5.6.17 | Linux (Centos 6.5/6.3) | Any | Unclear Deadlock conditions with delete / update statement. |
80424 | 2016-02-18 9:14 | 2017-01-03 11:46 | MySQL Server: Optimizer | Duplicate (2980 days) | S3 | 5.6, 5.7.11 | Any | Any | EXPLAIN output depends on binlog_format setting |
14560 | 2005-11-02 2:30 | 2006-08-22 14:01 | MySQL Server: Row Based Replication ( RBR ) | Can't repeat (6767 days) | S2 | 5.1.2 | Linux (Linux) | Any | Cluster RBR: Slave stops after processing "Create Procedure" with Error in Writ |
52061 | 2010-03-15 10:36 | 2011-02-16 23:44 | MySQL Server: Documentation | Closed (5464 days) | S3 | mysql-5.1 | Any | Any | MySQL Cluster docs : Wrong parameter effect description |
78144 | 2015-08-19 22:34 | 2015-11-24 9:07 | MySQL Server: Stored Routines | Verified (3481 days) | S3 | 5.6.19-log | Linux (RDS) | Any | Error handler not being triggered for multi-table update |
2996 | 2004-02-27 11:57 | 2020-03-09 14:06 | MySQL Server | Closed (7661 days) | S2 | 4.0.18 | Linux (Linux 2.4.25 (Slackware 9.1+)) | Any | update on left join can change non matching record in second table. |
9313 | 2005-03-21 13:19 | 2005-03-21 13:34 | MySQL Server: Replication | Closed (7286 days) | S2 | 4.1.10 | FreeBSD (FreeBSD 4.11) | Any | Multi-line statements not replicated properly? |
59763 | 2011-01-27 0:16 | 2011-05-04 19:12 | MySQL Server: InnoDB Plugin storage engine | Not a Bug (5051 days) | S3 | 5.1,5.5 | Any | Any | when does innodb compact blocks on delete |
76808 | 2015-04-23 12:33 | 2016-05-25 17:28 | MySQL Server: Stored Routines | Closed (3203 days) | S3 | 5.1.73 | Linux | Any | function updating a view fails to find table that actually exists |
1728 | 2003-10-31 17:01 | 2003-12-13 4:44 | MySQL Server | Won't fix (7750 days) | S2 | 4.0.16 | Linux (Red Hat linux 8.0) | Any | lock timeout not consistently returned by mysql_query() |
11408 | 2005-06-17 8:30 | 2005-06-17 8:37 | MySQL Server: InnoDB storage engine | Not a Bug (7198 days) | S3 | 5.0.7 | Windows (win2000) | Any | show table status return wrong |
83045 | 2016-09-20 7:11 | 2016-09-20 8:55 | MySQL Server: InnoDB storage engine | Duplicate (3085 days) | S2 | 5.6.17 | CentOS (6.5) | Any | Unique index allows duplicates without null values |
101718 | 2020-11-23 12:35 | 2020-11-24 5:16 | MySQL Server: DML | Verified (1560 days) | S5 | 8.0, 8.0.22 | Linux | Any | all new.x in before trigger marked in write_set may cause update use temp table |
35634 | 2008-03-28 8:54 | 2008-10-01 15:08 | MySQL Server: Command-line Clients | Won't fix (5996 days) | S4 | 5.1-bk | Any | Any | 'mysql' client: 'source' should stop after first failed command |
46675 | 2009-08-12 13:35 | 2011-08-19 15:15 | MySQL Server: General | Closed (4944 days) | S3 | server 5.1.37 | Any (MS Windows, Mac, Linux) | Any | ON DUPLICATE KEY UPDATE and updateCount() possibly wrong |
23233 | 2006-10-12 22:28 | 2007-04-04 4:03 | MySQL Server | Closed (6542 days) | S3 | 5.1.11-beta and 5.0.26/5.0BK/5.1BK | Windows (WINDOWS) | Any | NO_AUTO_VALUE_ON_ZERO and INSERT...ON DUPLICATE cause insertion failure |
54115 | 2010-05-31 18:49 | 2011-02-16 23:44 | MySQL Server: Documentation | Closed (5276 days) | S3 | 5.1 | Any | Any | Cluster replication conflict resolution docs confuse me |
19861 | 2006-05-16 19:47 | 2016-01-03 20:45 | MySQL Server: InnoDB storage engine | Duplicate (6857 days) | S3 | 5.0.22-BK, 5.0.18 | Linux (Linux) | Any | [reference_definition] in [column_definition] section of create table statement |
47031 | 2009-08-31 23:43 | 2011-02-16 23:44 | MySQL Server: Tests | Can't repeat (5661 days) | S3 | 5.0.85 | Linux (Red Hat Enterprise Linux) | Any | view test case fails |
48270 | 2009-10-23 16:18 | 2011-02-16 23:44 | Tests | Can't repeat (5609 days) | S3 | 5.0.85 | Linux | Any | mysql-test view.test fails |
52176 | 2010-03-18 11:11 | 2011-02-16 23:44 | MySQL Server: InnoDB storage engine | No Feedback (5426 days) | S2 | 5.0.90 | Windows | Any | MYSQL-NT goes in crash under windowxp |
12799 | 2005-08-25 9:46 | 2020-05-03 20:45 | MySQL Server: Optimizer | Verified (5632 days) | S3 | 5.0.10-log, 4.1.13a-log on win, 4.1 on RHES3.0 | Windows (windows xp) | Any | one result returned when change from summer time causes dup unique key recs |
31087 | 2007-09-18 17:47 | 2007-10-18 18:09 | MySQL Server: Stored Routines | No Feedback (6345 days) | S1 | mysql-5.0.44-r1 | Linux (recent up2date Gentoo box) | Any | Second call to stored procedure crashed server |
59384 | 2011-01-10 5:05 | 2012-03-25 21:27 | MySQL Server: InnoDB storage engine | Closed (4725 days) | S4 | 5.5.8, 5.5.11 | Linux | Any | slow INSERTs, sometimes |
11080 | 2005-06-03 17:32 | 2005-06-07 10:52 | MySQL Server: Optimizer | Closed (7208 days) | S3 | 5.0.7 | Linux (Linux/x86) | Any | Multi-row REPLACE fails on a duplicate key error on an AUTO-INC column |
3512 | 2004-04-20 2:11 | 2004-04-27 16:26 | MySQL Server | Not a Bug (7614 days) | S3 | 4.0.18 | Windows (Win2K) | Any | mysterious failure of insert due to duplicate key |
10715 | 2005-05-18 15:32 | 2005-07-11 15:12 | MySQL Server: MyISAM storage engine | No Feedback (7174 days) | S1 | 4.1 | Linux (Linux) | Any | Primary key being violated by duplicate key entries |
53290 | 2010-04-29 15:31 | 2011-02-16 23:44 | MySQL Server: InnoDB Plugin storage engine | Closed (5164 days) | S3 | 5.1.46, plugin 1.0.7 | Any | Any | wrong duplicate key error when adding a unique index via fast alter table |
96049 | 2019-07-01 14:09 | 2019-07-02 8:21 | MySQL Server: DML | Verified (2070 days) | S4 | 8.0 | Any | Any | IGNORE clause which doesn't override strict mode |
2792 | 2004-02-14 6:03 | 2004-09-14 13:03 | MySQL Server: InnoDB storage engine | Not a Bug (7474 days) | S3 | 4.0.16 | Linux (Debian 3.0) | Any | 2nd foreign key behaviour "On * do-sth" is missing in comment of Table-Status |
8333 | 2005-02-05 7:52 | 2005-02-05 8:00 | MySQL Server | Can't repeat (7330 days) | S3 | 3.23.49 | Linux (Linux or Apache web server) | Any | accepting duplicate entries in a feild which is set primary |
10292 | 2005-05-01 16:10 | 2005-06-03 12:19 | MySQL Server: Optimizer | Closed (7212 days) | S2 | 5.0.4 max nt | Windows (windows 2000 sp4) | Any | Duplicate entry error in SELECT |
29240 | 2007-06-20 15:08 | 2007-08-07 7:03 | MySQL Server: Falcon storage engine | Closed (6417 days) | S3 | 6.0.1-alpha-debug | Linux (SUSE 10 64-bit) | Any | Falcon: duplicate-key error when there's no duplicate key |
102833 | 2021-03-05 18:04 | 2021-03-05 20:25 | MySQL Server: FULLTEXT search | Verified (1458 days) | S1 | 5.7.33 | Ubuntu | x86 | Fulltext index error [ERROR] InnoDB: Duplicate FTS_DOC_ID value on table |
13690 | 2005-10-02 16:28 | 2005-11-17 9:50 | MySQL Server | No Feedback (7045 days) | S3 | 4.1.12a-nt | Windows (WinXP Pro) | Any | ERROR 1216 (23000): Cannot add or update a child row: a foreign key constraint |
33664 | 2008-01-03 17:41 | 2008-01-28 18:44 | MySQL Workbench | Closed (6243 days) | S2 | 5.0.11 SE Beta Rev 2342 | Windows (XP 32 bit) | Any | Workbench Allows Foreign Relationships With Unmatching Data Definitions |
74609 | 2014-10-28 18:52 | 2019-04-18 10:15 | MySQL Server: InnoDB storage engine | Duplicate (2145 days) | S3 | 5.6.21/5.7 | Linux | Any | Unable to update Foreign Key created as NOT NULL to table named with a Dollar $ |
67375 | 2012-10-25 5:46 | 2014-01-13 17:58 | Connector / J | Not a Bug (4066 days) | S2 | 5.5 | Windows | Any | ON DUPLICATE KEY UPDATE produces wrong affectedRows |
78854 | 2015-10-16 1:21 | 2015-10-27 3:28 | MySQL Server: Documentation | Not a Bug (3414 days) | S3 | 5.6, 5.7 | Any | Any | "more than one unique or primary key" |
43454 | 2009-03-06 13:38 | 2009-03-06 15:09 | MySQL Server: Parser | Not a Bug (5840 days) | S2 | 5.1.30 | Linux | Any | GROUP BY makes columns unrecognized when doing INSERT SELECT ... ON DUPLICATE K |
103137 | 2021-03-29 10:03 | 2025-01-20 10:56 | MySQL Server: Documentation | Closed (1396 days) | S3 | 8.0.20 | Any | Any | Deprecated VALUES vs INSERT SELECT ON DUPLICATE KEY UPDATE |
18507 | 2006-03-25 11:33 | 2016-01-03 20:45 | MySQL Server: InnoDB storage engine | Duplicate (6917 days) | S3 | 5.0.19 and 5.1.7-beta | Windows (windows xp pro) | Any | foreign key |
50456 | 2010-01-19 20:17 | 2010-01-19 21:08 | MySQL Server: Partitions | Not a Bug (5521 days) | S2 | 5.1.42-community-log | Any | Any | MySQl partitioning does not use the correct partitions |
77798 | 2015-07-22 10:56 | 2016-03-24 16:45 | MySQL Cluster: NDB API | Can't repeat (3429 days) | S2 | 7.4.6-1.el7.x86_64 | Oracle Linux (7.1) | Any | ERROR 1553 (HY000): Cannot drop index needed by foreign constraint |
81250 | 2016-04-29 19:57 | 2016-11-16 15:59 | MySQL Server: Optimizer | Closed (3028 days) | S2 | mysql 5.7.9, 5.7.12 | Linux (centos6.5) | Any | sql plan is not right according to optimizer_trace |
26507 | 2007-02-20 17:59 | 2012-10-16 5:21 | MySQL Server: InnoDB storage engine | Not a Bug (4520 days) | S2 | 5.0.27-max-log, 5.1.36, 5.0, 5.1 bzr | Linux (Linux, Fedora Core 6) | Any | Error 121 upon creating InnoDB table (in replicated setup) |
62210 | 2011-08-19 11:47 | 2012-02-02 19:59 | MySQL Server: InnoDB Plugin storage engine | Can't repeat (4777 days) | S2 | 5.1.48 (1.0.9) | Linux (2.6.18-164.el5) | Any | memory corruption for THD after deadlock in foreign key reference constrain |
25826 | 2007-01-24 13:26 | 2022-12-04 20:45 | MySQL Server: Errors | Verified (6589 days) | S4 | 5.0.36-BK, mysql-5.2.0-falcon-alpha-win32 | Windows (Windows 2000/XP) | Any | Unique keys: show constraint name in error message |
41700 | 2008-12-23 0:40 | 2013-12-20 6:53 | MySQL Server: General | Won't fix (4090 days) | S3 | 6.1.0-alpha-debug | Linux (SUSE 10.0 / 32-bit) | Any | Foreign keys: failure with update cascade and duplicate key |
28000 | 2007-04-21 14:59 | 2007-05-17 14:24 | MySQL Server | Closed (6499 days) | S3 | 5.0.37,5.1, 6.0-falcon-bk | Any | Any | MySQL hangs when using INSERT IGNORE ... ON DUPLICATE KEY |
50439 | 2010-01-19 11:16 | 2011-09-30 18:19 | MySQL Server: Replication | Closed (4902 days) | S2 | 5.1+ | Any | Any | mark INSERT...SEL...ON DUP KEY UPD,REPLACE...SEL,CREATE...[IGN|REPL] SEL unsafe |
54201 | 2010-06-03 12:18 | 2015-08-26 20:25 | MySQL Server: Replication | Closed (4692 days) | S2 | 5.1.47 | Any | Any | "SET INSERT_ID" event must be ignored if corresponding event is ignored |
61850 | 2011-07-13 8:19 | 2011-07-13 8:55 | Connector / J | Closed (4981 days) | S3 | 5.1 | Linux (Squeeze) | Any | JDBC: return value of INSERT ON DUPLICATE KEY does not match command line client |
9725 | 2005-04-07 16:36 | 2005-07-12 5:06 | MySQL Server | Closed (7173 days) | S3 | 4.1.11 | Any (*) | Any | "disapearing query/hang" and "unknown error" with "on duplicate key update" |
11442 | 2005-06-20 2:25 | 2011-02-16 23:43 | MySQL Server: DML | Verified (6640 days) | S4 | 5.0 | Any (All) | Any | INSERT... ON DUPLICATE KEY UPDATE; w/ values taken from the INSERT part |
20916 | 2006-07-08 17:35 | 2006-10-30 19:08 | MySQL Server: Documentation | Closed (6698 days) | S3 | 4.1.13, 5.0.21 | Linux (Linux) | Any | ambigous field with INSERT ... SELECT ... ON DUPLICATE KEY UPDATE |
35856 | 2008-04-05 23:31 | 2008-10-16 4:30 | MySQL Server: InnoDB storage engine | Duplicate (5981 days) | S3 | 5.0.45 | Any | Any | false unique constraint violation on multiple updates |
40872 | 2008-11-19 23:09 | 2016-10-16 20:45 | MySQL Server: Replication | No Feedback (5916 days) | S2 | 5.0.45, 5.0.51a (ICC) | Linux | Any | Slave doesn't get replicated properly with ON DUPLICATE KEY UPDATE statements |
44566 | 2009-04-30 3:53 | 2023-03-10 7:52 | MySQL Cluster: Replication | No Feedback (5748 days) | S3 | mysql-5.1-telco-6.3 | Linux | Any | Error on Innodb to NDB replication with UPDATE statements |
70583 | 2013-10-10 8:14 | 2014-08-06 17:08 | MySQL Server: Replication | Closed (3896 days) | S2 | 5.6.14 | Any | Any | INSERT ON DUPLICATE KEY UPDATE failing after MySQL 5.6 upgrade. |
87371 | 2017-08-10 11:42 | 2017-10-05 18:16 | MySQL Server: Stored Routines | Closed (2705 days) | S2 | 5.7.17 | CentOS | Any | Bug in "INSERT... ON DUPLICATE KEY UPDATE" query |
60489 | 2011-03-16 13:44 | 2011-07-05 16:36 | MySQL Server: Documentation | Not a Bug (4989 days) | S3 | 5.5.10 | Windows (XP) | Any | Update returnd god result but CURRENT_TIMESTAMP field not updated |
3675 | 2004-05-06 9:33 | 2004-05-06 19:32 | MySQL Server | Not a Bug (7605 days) | S2 | 4.0+4.1 | Windows (Windows 2000) | Any | UPDATE on multiple tables doesn't work correctly when inner joining by a comma |
4666 | 2004-07-21 3:30 | 2004-08-06 16:14 | Connector / NET | Closed (7513 days) | S2 | 0.7.6.15073 | Windows (Win XP Pro) | Any | MySqlDataAdapter.Update does not update Database |
57153 | 2010-09-30 20:32 | 2018-02-11 13:02 | MySQL Server: DML | Can't repeat (2576 days) | S5 | 5.1.51 | Other (Centos 5.5) | Any | Performance of call to POWER(LOG(EXP(0.25)),0.5) slower than expected on 5.1.51 |
69659 | 2013-07-03 10:30 | 2015-04-22 17:53 | MySQL Server: Installing | Unsupported (4260 days) | S1 | 5.6.12 | Windows (XP SP3) | Any | MySQL server 5.6.12 configuration failed |
89101 | 2018-01-04 1:52 | 2020-03-30 12:12 | MySQL Server: DML | Verified (2600 days) | S2 | 5.7.20 | Any | Any | MySQL server hang when gtid_mode=on and innodb_thread_concurrency>0 |
117286 | 2025-01-24 3:11 | 2025-01-24 15:51 | MySQL Server: Documentation | Verified (37 days) | S3 | 8.0 | Any | Any | A example in transaction isolation levels part is not accurate |
10095 | 2005-04-22 12:38 | 2005-05-19 2:06 | MySQL Server: Optimizer | Closed (7227 days) | S1 | 4.0.24 | Linux (linux) | Any | AND/OR - get diff result |
10649 | 2005-05-15 23:19 | 2006-09-30 12:18 | MySQL Server | Duplicate (6728 days) | S3 | 4.1.11 | Linux (Red Hat Linux 9) | Any | "where not in" with subquery produces incorrect results |
20498 | 2006-06-16 10:25 | 2006-06-26 13:24 | MySQL Cluster: Cluster (NDB) storage engine | Closed (6824 days) | S2 | 5.1.12 | Linux (Linux/all) | Any | Wrong usage of mysys/hash.c |
38550 | 2008-08-04 21:47 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5981 days) | S5 | 5.0.60, 5.1 | Any | Any | multiple optimizer bugs for queries with references from preceding table |
64775 | 2012-03-27 9:53 | 2012-04-29 1:00 | MySQL Server: Federated storage engine | No Feedback (4691 days) | S2 | 5.1.61 | Linux (open suse 11.4) | Any | Left join on federated.varchar(15) = innodb.char(25) gives bad query plan, crash |
75052 | 2014-12-01 6:59 | 2019-05-15 12:56 | Tests: Server | Won't fix (2118 days) | S3 | 5.5, 5.5.42 | Any | Any | foreign-keys testcase mismerged in 5.5 |
99436 | 2020-05-04 11:51 | 2020-09-28 14:46 | MySQL Cluster: Cluster (NDB) storage engine | Not a Bug (1616 days) | S3 | 8.0.20 | Red Hat (8) | Any | NDB fully replicated tables only in node group 0, not in node group 1 |
7936 | 2005-01-16 1:15 | 2005-06-07 15:50 | MySQL Server: Memory storage engine | Open (7208 days) | S4 | 4.0.17 | FreeBSD (FreeBSD) | Any | HEAP table HASH not optimized for searches that usually do not match KEY |
102343 | 2021-01-22 11:08 | 2021-01-22 14:05 | MySQL Server: DML | Not a Bug (1500 days) | S4 | Any | Any | Use FOREIGN KEY description for JOIN tables | |
45052 | 2009-05-24 7:46 | 2011-02-16 23:44 | MySQL Server | Closed (5372 days) | S2 | 6.0.10-alpha,5.4 | Linux (OpenSuse 10.3) | Any | ALTER TABLE ADD COLUMN crashes server with multiple foreign key columns |
46525 | 2009-08-03 10:16 | 2011-02-16 23:44 | MySQL Server: InnoDB storage engine | Can't repeat (5347 days) | S5 | Linux | Any | 5.1.36: innodb: updates / alter table exremley slow | |
17086 | 2006-02-03 0:39 | 2006-07-03 14:42 | MySQL Cluster: Cluster (NDB) storage engine | Closed (6817 days) | S3 | 4.1 -> | Linux (Linux 32 Bit OS) | Any | rpl_auto_increment.test fix for ndb |
39155 | 2008-09-01 11:29 | 2008-10-01 14:50 | MySQL Server: Replication | No Feedback (5996 days) | S1 | 5.1.23 | Windows (2000 sp4) | Any | Replication error duplicate entry |
75189 | 2014-12-12 7:09 | 2014-12-19 22:15 | MySQL Server: Tests | Verified (3726 days) | S3 | 5.6 | Any | Any | engines suite tests depending on InnoDB implementation details |
67615 | 2012-11-16 16:21 | 2018-01-26 16:20 | MySQL Server: InnoDB storage engine | Not a Bug (2592 days) | S2 | 5.5.28 | Linux (6.2) | Any | Massive conccurent inserts and lock wait timeout |
70086 | 2013-08-19 16:06 | 2013-11-03 1:00 | MySQL Server: Optimizer | No Feedback (4138 days) | S2 | 5.6.13-log | Linux (2.6.16.33-xenU x86_64) | Any | Degraded performance for index_merge updates |
85353 | 2017-03-08 1:26 | 2017-03-09 8:34 | MySQL Server: Errors | Verified (2915 days) | S4 | 5.6,5.7.17 | Any | Any | Ambiguous Error Message in safe_updates mode |
6946 | 2004-12-02 14:31 | 2006-02-14 14:28 | MySQL Server | Won't fix (6956 days) | S4 | * | Any (*) | Any | INSERT ... ON DUPLICATE KEY UPDATE without INSERT |
64025 | 2012-01-13 14:21 | 2012-01-15 19:15 | MySQL Server: DML | Verified (4797 days) | S3 | 5.1.61, 5.5.15 | Any | Any | ON DUPLICATE KEY UPDATE sets auto_increment column value to 0 |
64139 | 2012-01-26 22:20 | 2021-09-05 20:45 | MySQL Cluster: Replication | Verified (4784 days) | S3 | mysql-cluster-gpl-7.2.2 | Any | Any | Duplicate INSERTs in binary log for NDB tables when binlog_format=STATEMENT |
76895 | 2015-04-30 6:06 | 2021-08-15 17:57 | MySQL Server: InnoDB storage engine | Not a Bug (3594 days) | S2 | 5.6.24 | Any | Any | Adding new column OR Drop column causes duplicate PK error |
56731 | 2010-09-11 14:43 | 2018-10-21 20:45 | Connector / ODBC | No Feedback (3534 days) | S2 | 5.1.6 | MacOS (likely other OSes) | Any | Second SQLSetPos(Update) not posting update to database |
14055 | 2005-10-16 4:18 | 2005-10-18 22:02 | MySQL Server | Won't fix (7075 days) | S2 | 4.1.16 | Any (any) | Any | AES_DECRYPT returns NULL on valid input |
106492 | 2022-02-17 14:37 | 2022-11-22 21:08 | MySQL Server: Installing | Won't fix (1082 days) | S3 | 5.7 | Debian (stretch) | Any | he following signatures were invalid: EXPKEYSIG 8C718D3B5072E1F5 |
3659 | 2004-05-05 10:34 | 2004-07-19 13:39 | MySQL Cluster: Cluster (NDB) storage engine | Closed (7531 days) | S1 | mysql-4.1.2-alpha bk | FermiLinux LTS 3.01 | Any | >1 concurrent update causes deadlock |
26743 | 2007-03-01 9:02 | 2007-04-30 9:06 | MySQL Migration Toolkit | Closed (6516 days) | S3 | 1.1.11, 1.1.10, 1.1.9 | Windows (Win XP) | Any | Created SQL Syntax failed for "DEFAULT USER" |
33656 | 2008-01-03 16:28 | 2008-02-04 20:49 | MySQL Workbench | Closed (6236 days) | S2 | 5.0.11 SE Beta Rev 2342 | Windows (XP 32 bit) | Any | Workbench Generates Invalid Foreign Index Statements |
28867 | 2007-06-04 7:45 | 2007-06-04 8:29 | MySQL Server | Not a Bug (6481 days) | S2 | 5.0.41 | FreeBSD (6.2 amd64) | Any | INSERT ...ON DUPLICATE KEY UPDATE,affected_rows diff between 5.0.18 and 5.0.41 |
51140 | 2010-02-12 12:06 | 2010-02-13 7:42 | MySQL Server: InnoDB storage engine | Not a Bug (5496 days) | S3 | 5.1.31 | Linux | Any | Deadlock instead of timeout when inserting the same row from two transactions |
54250 | 2010-06-05 3:18 | 2018-12-09 9:12 | MySQL Server: Replication | Verified (5383 days) | S4 | Any | Any | Feature request for RBR auto-fix slave functionality | |
64290 | 2012-02-10 6:24 | 2012-02-10 15:41 | MySQL Server: DML | Not a Bug (4769 days) | S3 | 5.5.15 | Windows | Any | INSERT ON DUPLICATE KEY UPDATE can't work with primary key value equals zero |
72921 | 2014-06-09 17:10 | 2014-06-25 15:27 | MySQL Server: Errors | Verified (3918 days) | S4 | 5.5+ | Any | Any | note 1592: unsafe statement...on duplicate key update issued for safe statements |
94582 | 2019-03-06 21:06 | 2019-03-06 22:10 | MySQL Server: DML | Closed (2188 days) | S3 | 8.0.12 | Any | Any | Primary key 1 causes ON DUPLICATE KEY UPDATE to use erroneous value |
114446 | 2024-03-21 14:30 | 2024-04-22 10:14 | MySQL Server: InnoDB storage engine | Not a Bug (346 days) | S3 | 8.0.* | Any | Any | A deadlock example cause by lock inherit |
81486 | 2016-05-18 11:43 | 2016-05-24 18:51 | MySQL Server: DML | Closed (3209 days) | S3 | 5.6.30, 5.5.49 | Debian | Any | ERROR 1452 throws as ERROR 1062 if query has ON DUPLICATE stament |
37016 | 2008-05-27 19:25 | 2011-02-16 23:43 | MySQL Server: DDL | Closed (5876 days) | S3 | 5.1, 6.0-bk | Any | Any | TRUNCATE TABLE removes some rows but not all |
53712 | 2010-05-17 16:13 | 2011-02-16 23:44 | MySQL Server: General | No Feedback (5371 days) | S2 | 5.1.46 | Solaris | Any | ORDER BY causes incorrect query result |
67304 | 2012-10-19 20:54 | 2012-11-24 1:00 | MySQL Workbench: Modeling | No Feedback (4482 days) | S3 | 5.2.44 win32.msi | Windows | Any | mySQL workbench is dropping foreign keys durring sycronize with DB when updating |
70245 | 2013-09-04 21:45 | 2013-09-05 16:57 | MySQL Server: Optimizer | Not a Bug (4196 days) | S2 | 5.6.13 | Linux (2.6.16.33-xenU x86_64) | Any | incorrect costing for range scan causes optimizer to choose incorrect index |
15045 | 2005-11-18 9:35 | 2018-06-14 16:56 | MySQL Server: InnoDB storage engine | Verified (5407 days) | S4 | 4.1 | Windows (windows xp) | Any | can't drop and recreate foreign key in a single ALTER TABLE statement |
73300 | 2014-07-16 18:03 | 2015-04-01 4:41 | MySQL Server: InnoDB storage engine | Closed (3853 days) | S3 | 5.7.5 | Any | Any | innodb.log_file_name fails sproadically on pb2 |
94068 | 2019-01-25 19:19 | 2019-03-06 14:33 | MySQL Server | Not a Bug (2188 days) | S2 | 8.0.13 | Linux | Any | Index performance degradation, ~50 times slower after 30 hours. reproduceable |
25673 | 2007-01-17 9:27 | 2007-03-15 2:46 | MySQL Server: MyISAM storage engine | Closed (6562 days) | S1 | 5.0.34,5.0.36-BK,5.1.15-BK | * | Any | spatial index corruption, error 126 incorrect key file for table |
41754 | 2008-12-26 12:03 | 2017-05-21 20:45 | MySQL Server: Replication | Duplicate (5822 days) | S2 | 5.0.70, 5.1.30, 6.0.9 | Any | Any | 'Cannot add or update a child row: a foreign key constraint fails' on SBR+Innodb |
105808 | 2021-12-06 12:18 | 2021-12-06 14:15 | MySQL Server: Optimizer | Not a Bug (1182 days) | S5 | MySQL 8.0.27 | Any | Any | Confusing partition pruning policy for `NULL condition` on DATATIME field. |
23842 | 2006-11-01 15:33 | 2006-11-02 3:52 | MySQL Server | Not a Bug (6695 days) | S3 | 5.0.27-community-nt | Windows (Windows XP) | Any | Unsigned check on "ON DUPLICATE KEY" query |
29180 | 2007-06-18 16:48 | 2007-06-26 12:57 | MySQL Server | Closed (6459 days) | S2 | 5.0.41-log | Linux | Any | INSERT ... ON DUPLICATE KEY don't work correctly |
42087 | 2009-01-13 15:52 | 2011-02-16 23:43 | MySQL Server: General | Verified (5828 days) | S2 | 5.1.30 | Any | Any | Statement.executeUpdate() gives strange update count with INSERT ...ON DUPLICATE |
65111 | 2012-04-26 9:31 | 2012-05-15 18:33 | MySQL Server: InnoDB Plugin storage engine | Closed (4674 days) | S2 | 5.6,5.5 | Linux | Any | Innodb sometimes fails to update rows inserted by a concurrent transaction |
76803 | 2015-04-23 8:42 | 2019-01-25 1:21 | MySQL Server: InnoDB storage engine | Closed (2228 days) | S3 | 5.1, 5.5, 5.6, 5.7, 8.0 | Any | Any | InnoDB: Unlock row could not find a 2 mode lock on the record |
15932 | 2005-12-22 9:31 | 2006-01-22 13:41 | MySQL Server | No Feedback (6979 days) | S3 | 5.0.17 | Linux (linux) | Any | why can't indexes updated? |
18468 | 2006-03-23 19:05 | 2012-05-18 20:19 | MySQL Cluster: Cluster (NDB) storage engine | Duplicate (6919 days) | S3 | 5.1.8 | Linux (Linux 32 Bit OS) | Any | Cluster is not optimizing on indexes provided. "Impossible WHERE noticed" |
44447 | 2009-04-23 21:25 | 2009-04-24 6:05 | MySQL Server: Information schema | Not a Bug (5791 days) | S3 | 5.0.51a | Any | Any | Incorrect clustered index in InnoDB table? |
60876 | 2011-04-15 6:20 | 2011-04-23 16:47 | MySQL Server | Not a Bug (5062 days) | S2 | mysql Ver 14.12 Distrib 5.0.45 | Linux (Red Hat Enterprise Linux Server release 5.3 ) | Any | A Floating Point Issue |
65701 | 2012-06-21 16:26 | 2014-10-10 18:52 | MySQL Server: InnoDB storage engine | Closed (4281 days) | S2 | 5.5.24, 5.5.26, 5.6.6 | Linux (CentOS 6.2) | Any | character set mismatch when altering foreign keys can lead to missing tables |
72033 | 2014-03-13 14:50 | 2014-03-14 8:24 | MySQL Server: MyISAM storage engine | Verified (4006 days) | S3 | 5.6.18 | Any | Any | No warning when setting KEY_BLOCK_SIZE on a MyISAM index, value silently ignored |
72690 | 2014-05-20 9:13 | 2014-07-15 8:59 | MySQL Server: Optimizer | Not a Bug (3925 days) | S2 | 5.6.17 | Any | Any | A 5.6's optimizer bug which is releated to 'or' operator's number |
77026 | 2015-05-13 12:20 | 2016-10-11 1:00 | MySQL Utilities | No Feedback (3065 days) | S2 | 5.6.24 | Windows | Any | mysqldbcompare and mysqldiff error updating |
100441 | 2020-08-06 10:38 | 2020-09-02 8:33 | MySQL Server: DDL | Not a Bug (1642 days) | S3 | 8.0.21 | Any | Any | The Foreign Key constraint is not updated after renaming |
111616 | 2023-06-29 6:19 | 2023-06-30 7:40 | MySQL Server: Data Dictionary | Verified (611 days) | S2 | 8.0.32 | Any | Any | Failed to upgrade from 5.7 to 8.0 because of spatial column with BTREE index |
20977 | 2006-07-11 22:07 | 2006-08-10 16:01 | MySQL Server: Views | Closed (6779 days) | S3 | 5.1.12 | Linux (Fedora core 5) | Any | confusing results after setting 'updatable_views_with_limit' to 'NO' |
80528 | 2016-02-26 13:09 | 2016-09-18 1:00 | MySQL Workbench: Modeling | No Feedback (3088 days) | S2 | 6.3.6 | Windows (Microsoft Windows 10 Pro) | Any | Copying a PK-column as reference into another table impossible to remove AI |
80529 | 2016-02-26 13:10 | 2016-02-26 14:05 | MySQL Workbench: Modeling | Duplicate (3292 days) | S2 | 6.3.6 | Windows (Microsoft Windows 10 Pro) | Any | Copying a PK-column as reference into another table impossible to remove AI |
11907 | 2005-07-13 10:04 | 2013-05-30 5:22 | Connector / ODBC | Can't repeat (4294 days) | S3 | 4.0.20-log | Linux (Mandrake 10.1) | Any | Duplicate entry NULL for key |
36621 | 2008-05-09 10:49 | 2008-06-20 21:43 | MySQL Server: Falcon storage engine | Not a Bug (6099 days) | S3 | 6.0.5 | Any | Any | Falcon allows a key to be named PRIMARY_KEY |
99780 | 2020-06-04 13:25 | 2020-06-05 2:49 | MySQL Workbench: Modeling | Not a Bug (1731 days) | S7 | 8.0.20 | MacOS (macOS 10.15.x Catalina x86_64) | Any | finally forget this bug....it is something else |
6592 | 2004-11-12 13:37 | 2004-12-16 3:42 | MySQL Cluster: Cluster (NDB) storage engine | No Feedback (7381 days) | S2 | 4.1.7 | Linux (Redhat Enterprise Linux AS 3) | Any | ndb table, insert, Duplicate entry '-1' for key 1 |
10852 | 2005-05-25 4:06 | 2011-07-12 20:52 | MySQL Migration Toolkit | Closed (7200 days) | S2 | 1.0.6beta | Windows (WindowsXP) | Any | Missing Tables / "Error 1061 Duplicate key name" migrating from Access97 |
11606 | 2005-06-28 9:53 | 2005-07-28 17:10 | MySQL Server: Optimizer | No Feedback (7157 days) | S2 | 4.1.11-standard-log | Linux (Fedora Core 2) | Any | Duplicate key error in SELECT query |
16677 | 2006-01-20 16:22 | 2006-02-17 12:53 | MySQL Server: Documentation | Closed (6953 days) | S3 | 4.1-> | Linux (Linux) | Any | Cluster returns different duplicate key error then other engines |
19133 | 2006-04-16 19:51 | 2006-04-17 13:07 | MySQL Server | Not a Bug (6894 days) | S2 | 4.1.14-Debian_6-log | Linux (Debian) | Any | ERROR 1062 (23000): Duplicate entry '127' for key 1 |
20820 | 2006-07-03 13:01 | 2006-07-07 3:45 | MySQL Cluster: Cluster (NDB) storage engine | Closed (6813 days) | S2 | 5.0 | Linux (Linux 32 bit OS) | Any | auto inc table not handled correctly when restored from cluster backup |
21335 | 2006-07-28 23:08 | 2007-07-05 20:30 | MySQL Server: Documentation | Not a Bug (6450 days) | S2 | 4.1.22 4.0.28 | Any | Any | UNIQUE index on TEXT columns allows trailing whitespace |
26803 | 2007-03-02 19:15 | 2007-04-13 9:04 | MySQL Server: Falcon storage engine | Closed (6533 days) | S3 | 5.1 | Any | Any | unique constraints on VARCHAR columns behave different in MyISAM and Falcon |
27022 | 2007-03-10 10:52 | 2007-04-06 18:06 | MySQL Server: Installing | Closed (6540 days) | S1 | 5.0.38, 5.1.17 | Linux (Linux) | Any | Install fails with Duplicate entry '%-test-' for key 'PRIMARY' |
27616 | 2007-04-03 13:45 | 2007-04-17 13:41 | MySQL Enterprise Monitor: Server | Closed (6529 days) | S2 | 1.1.0.4973 | Windows (Windows XP) | Any | MySQLIntegrityConstraintViolationException: Duplicate entry '...' for key 2 |
31349 | 2007-10-02 18:13 | 2007-12-20 0:43 | MySQL Server: Data Types | Closed (6282 days) | S3 | 5.1.23-debug, 5.0.48-debug | Any | Any | ERROR 1062 (23000): Duplicate entry '' for key 'group_key' |
33688 | 2008-01-04 11:33 | 2008-03-13 5:52 | MySQL Server: Replication | Closed (6198 days) | S1 | 6.0.4 | Any | Any | Falcon: replication fails on duplicate key error |
35807 | 2008-04-03 15:53 | 2008-09-15 16:09 | MySQL Server: Row Based Replication ( RBR ) | Closed (6012 days) | S3 | 5.1.24 | Any | Any | INSTALL PLUGIN replicates row-based, but not stmt-based |
36801 | 2008-05-19 15:02 | 2016-01-03 20:45 | MySQL Server: InnoDB storage engine | Verified (5407 days) | S4 | Any | Any | InnoDB should release the lock on a duplicate key under REPEATABLE READ | |
41026 | 2008-11-25 19:08 | 2011-02-16 23:43 | MySQL Server | Closed (5932 days) | S3 | 6.0.8-release | Any | Any | maria: Duplicate entry '...' for key 'PRIMARY' in sysbench OLTP_RW test |
42396 | 2009-01-27 21:35 | 2017-01-18 13:23 | MySQL Cluster: Replication | Can't repeat (2965 days) | S3 | mysql-6.0 | Any | Any | autoincrement insert into ndb fails with duplicate key |
47207 | 2009-09-09 7:21 | 2022-12-04 20:45 | MySQL Server: Errors | Verified (5653 days) | S3 | 5.1 | Any | Any | Not enough information in error Duplicate entry xxx for key 1 |
50198 | 2010-01-08 22:55 | 2011-02-16 23:44 | MySQL Server: Optimizer | Can't repeat (5492 days) | S3 | 5.1 | Any | Any | Server adding duplicate row with duplicate WHERE clause condition and Innodb |
50199 | 2010-01-08 22:56 | 2018-09-09 20:45 | MySQL Server: Optimizer | Duplicate (5532 days) | S3 | 5.1 | Any | Any | Server adding duplicate row with duplicate WHERE clause condition and Innodb |
50200 | 2010-01-08 22:56 | 2018-09-09 20:45 | MySQL Server: Optimizer | Duplicate (5532 days) | S3 | 5.1 | Any | Any | Server adding duplicate row with duplicate WHERE clause condition and Innodb |
60886 | 2011-04-15 20:56 | 2011-04-16 19:35 | MySQL Server | Duplicate (5069 days) | S2 | 5.5.11 | MacOS (10.7.0) | Any | ALTER IGNORE TABLE ADD PRIMARY KEY fails on duplicate key values |
65979 | 2012-07-22 12:12 | 2014-09-05 9:55 | MySQL Cluster: Cluster (NDB) storage engine | Can't repeat (3831 days) | S1 | 5.5.25a-ndb-7.2.7-gpl-log | Linux (CentOS release 6.3 (Final) 2.6.32-279.1.1.el6.x86_64) | Any | All SQL Nodes SIGSEGV when writing dupe data to tables where PK spans all cols |
69185 | 2013-05-09 15:23 | 2014-02-24 12:33 | MySQL Server: Replication | Verified (4024 days) | S2 | 5.1.69 | Any | Any | Replication breaks during concurrent INSERTs and LOAD DATA in a auto_inc table |
81101 | 2016-04-15 18:13 | 2017-10-13 23:49 | MySQL Server: InnoDB storage engine | Duplicate (2910 days) | S2 | 5.6.25 | CentOS | Any | Duplicate PRIMARY KEY errors after changing auto_increment settings |
81254 | 2016-05-01 7:53 | 2016-05-02 10:10 | MySQL Server: DML | Verified (3226 days) | S2 | 5.6, 5.6.30, 5.7.12 | Any | Any | Using INSERT_ID local variable, makes REPLACE fail when there is a duplicate key |
89143 | 2018-01-08 22:10 | 2018-07-02 14:06 | MySQL Server: Replication | Closed (2502 days) | S2 | 5.7.20 | Any | Any | Commit order deadlock + retry logic is not considering trx error cases |
95079 | 2019-04-23 2:32 | 2019-04-25 9:21 | MySQL Server: InnoDB storage engine | Verified (2140 days) | S3 | 5.7, 5.7.25 | Any | Any | False duplicate key check |
102683 | 2021-02-22 8:38 | 2021-04-24 14:56 | MySQL Server: Japanese Documentation | Closed (1408 days) | S3 | 8.0 | Any | Any | Proposal for the Japanese 8.0 document correction(Chap 10:Charset). |
103632 | 2021-05-08 12:23 | 2022-08-13 16:23 | MySQL Server: Optimizer | Verified (932 days) | S2 | 8.0.23, 8.0.24, 5.7.34 | Any (Windows, Ubuntu) | Any | Can't write; duplicate key in table |
112368 | 2023-09-17 14:39 | 2023-09-21 2:29 | MySQL Server: Group Replication | Can't repeat (528 days) | S1 | 5.7.36 | Debian (Debian GNU/Linux 10 (buster)) | Any | Mismatched SQL for the same GTID transaction across primary and secondary |
113229 | 2023-11-27 7:57 | 2023-11-27 11:11 | MySQL Server: Replication | Can't repeat (461 days) | S3 | 8.0.33 | Any (CentOS Linux 7) | Any | mysqld: Duplicate entry 'mysql/slave_worker_info' for key 'tablespaces.name' |
115511 | 2024-07-04 11:46 | 2025-01-16 17:07 | MySQL Server: InnoDB storage engine | Closed (45 days) | S3 | 8.0 | Any | Any | Inplace ALTER TABLE might fail with duplicate key error if concurrent insertions |
111530 | 2023-06-22 8:42 | 2023-06-23 4:01 | Connector / J | Not a Bug (619 days) | S3 | 8.0.29 | Any | Any | useGeneratedKeys bug When using on duplicate key update clause |
6270 | 2004-10-26 20:28 | 2004-12-01 19:44 | MySQL Server: MyISAM storage engine | Not a Bug (7396 days) | S2 | 4.1.7 | Linux (Linux) | Any | UPDATE report a duplicate key error whereas it shouldn't |
8732 | 2005-02-23 14:49 | 2012-05-18 20:19 | MySQL Server | Duplicate (7149 days) | S3 | 4.1.10 | Any (*) | Any | INSERT ... SELECT ...ON DUPLICATE KEY UPDATE problem |
8736 | 2005-02-23 17:31 | 2005-02-23 21:51 | MySQL Server | Closed (7312 days) | S3 | 4.1.10 | Any (*) | Any | on duplicate key update allows/ignores updates to read table |
27210 | 2007-03-16 12:31 | 2007-08-29 2:10 | MySQL Server | Closed (6395 days) | S2 | 5.0.36, 5.0.37 | Linux (Linux, Windows) | Any | INNODB ON DUPLICATE KEY UPDATE |
29728 | 2007-07-11 17:54 | 2007-08-13 20:21 | MySQL Server: Replication | Can't repeat (6411 days) | S2 | 5.0.36sp1-enterprise-gpl-log | Solaris (i386) | Any | INSERT ... ON DUPLICATE KEY UPDATE syntax fails on replication slaves |
30146 | 2007-07-31 12:59 | 2007-07-31 13:10 | MySQL Server: General | Closed (6424 days) | S3 | 5.0.42-enterprise-gpl | Any | Any | on duplicate key update does insert and update at the same time |
38046 | 2008-07-11 14:22 | 2012-08-03 15:34 | MySQL Server: Locking | Closed (4594 days) | S3 | 5.0, 5.1, 6.0 bzr | Any | Any | INSERT SELECT ON DUPLICATE KEY UPDATE, LOAD DATA REPLACE wrong lock |
43958 | 2009-03-30 13:07 | 2009-05-15 16:10 | MySQL Server: Falcon storage engine | Closed (5770 days) | S1 | 6.0.11-bzr | Solaris (Solaris 10 x64) | Any | Assertion (transState != NULL) failed in Transaction::waitForTransaction |
52455 | 2010-03-30 1:54 | 2011-02-16 23:44 | MySQL Server: Partitions | Closed (5253 days) | S3 | 5.1 | Any | Any | Subpar INSERT ON DUPLICATE KEY UPDATE performance with many partitions |
56935 | 2010-09-22 14:50 | 2010-09-23 5:24 | MySQL Server: Parser | Not a Bug (5274 days) | S3 | 5.021 | Any | Any | insert ... on duplicate key update .. update content may not contain ";" |
57880 | 2010-11-01 8:30 | 2011-02-16 23:44 | MySQL Server: MyISAM storage engine | Closed (5211 days) | S2 | 5.1.49, 5.1.52, 5.5.6rc | Any | Any | Difference between MyISAM and InnoDB when using pk + UPDATE |
66807 | 2012-09-13 12:34 | 2012-09-13 17:09 | MySQL Server: General | Not a Bug (4553 days) | S3 | 5.1.41 | Windows (Windows 7 32bit) | Any | Wrong AUTO_INCREMENT value when using ON DUPLICATE KEY UPDATE clause |
69718 | 2013-07-10 18:36 | 2016-01-10 20:45 | Connector / ODBC | Patch pending (4205 days) | S2 | 5.2.5 | Windows (window7 64bit) | Any | INSERT ON DUPLICATE KEY UPDATE does regularly report "-1" |
95096 | 2019-04-24 1:27 | 2019-04-24 6:03 | MySQL Server: DML | Not a Bug (2139 days) | S3 | Any | Any | INSERT INTO ... ON DUPLICATE KEY UPDATE returns wrong number of rows updated | |
107325 | 2022-05-18 10:03 | 2022-05-18 14:36 | MySQL Server: DML | Verified (1019 days) | S3 | 8.0 | Any | Any | Subquery gives wrong results in ON DUPLICATE KEY UPDATE ... part of INSERT |
2293 | 2004-01-06 3:17 | 2005-08-04 23:35 | MySQL Websites: bugs.mysql.com | Closed (7150 days) | S4 | Any | Enhance the marking of duplicate bug reports | ||
74496 | 2014-10-22 8:08 | 2014-10-24 8:44 | MySQL Server: DDL | Not a Bug (3784 days) | S3 | 5.6.21 | Windows | Any | View creation: error in checking duplicate column names |
76314 | 2015-03-13 13:17 | 2016-02-04 19:33 | MySQL Server: Optimizer | Closed (3441 days) | S3 | 5.7 | Any | Any | Semi-join duplicate elimination gives lower cost than no duplicate elimination |
101985 | 2020-12-13 15:03 | 2020-12-14 14:16 | MySQL Server: Optimizer | Not a Bug (1539 days) | S3 | Mysql 5.7 | Any | Any | cost planner doesn't know when DuplicateWeedout Strategy creates disk table |
103463 | 2021-04-24 19:30 | 2021-04-29 1:30 | MySQL Server: DDL | Unsupported (1403 days) | S2 | 5.7.32-log | Windows (Azure cloud instance) | Any (Unknown) | ALTER TABLE produces a duplicate table |
10396 | 2005-05-05 19:03 | 2011-02-16 23:43 | MySQL Server: Command-line Clients | Verified (7202 days) | S4 | 4.1 | Any (any) | Any | UPDATE... [ON NONE FOUND INSERT] |
34208 | 2008-01-31 21:55 | 2008-04-02 19:35 | MySQL Cluster: Cluster (NDB) storage engine | Closed (6178 days) | S2 | 5.1.23-rc | Linux (IA64, icc) | Any | Wrong select results returned by cluster |
17016 | 2006-02-01 16:51 | 2008-01-09 23:08 | Connector / ODBC | Can't repeat (6262 days) | S2 | 3.51 | Windows (Windows) | Any | I find some problem in MySQL (bugs) - 'update' command in C++ |
26320 | 2007-02-13 13:13 | 2007-02-21 18:41 | MySQL Enterprise Monitor: Installing | Closed (6584 days) | S2 | 1.1.0.4732 | Linux (RHEL4) | Any | Service Manager update installer fails on Linux |
42615 | 2009-02-05 10:59 | 2011-02-16 23:43 | MySQL Server: General | Verified (5852 days) | S4 | 5.0.27 | FreeBSD | Any | UPDATE statement workflow |
48663 | 2009-11-10 10:51 | 2011-02-16 23:44 | MySQL Server: Errors | Closed (5162 days) | S2 | 5.1.34 | Any | Any | STRICT_TRANS_TABLE causing an error when 0 rows found in an UPDATE trigger |
49070 | 2009-11-24 20:53 | 2016-02-25 12:24 | MySQL Workbench: Administration | Not a Bug (5506 days) | S2 | 5.2 r4753 | Windows (XP) | Any | WB creating strange GRANTs |
52350 | 2010-03-25 0:19 | 2022-11-15 23:59 | MySQL Workbench | Closed (5393 days) | S1 | 5.2.16 | Any | Any | cannot set ON UPDATE CURRENT_TIMESTAMP as default value |
53075 | 2010-04-22 18:12 | 2011-02-16 23:44 | MySQL Server: Replication | Closed (5412 days) | S3 | 5.6.99-m4 | Any | Any | SBR: Strange warning around CONNECTION_ID() |
107956 | 2022-07-25 7:11 | 2022-08-12 8:09 | MySQL Server: Row Based Replication ( RBR ) | Not a Bug (933 days) | S3 | 5.7.35 | Ubuntu | Any | log_slave_updates not respecting binlog_row_image |
1701 | 2003-10-29 6:48 | 2003-12-07 14:07 | MySQL Server: Replication | Closed (7756 days) | S3 | 4.0.15-std-log | Linux (Linux RH9) | Any | Update from multiple tables |
6254 | 2004-10-25 20:34 | 2016-01-03 20:45 | MySQL Server: InnoDB storage engine | Verified (6766 days) | S4 | 4.1.7-debug | Linux (SuSE 9.1) | Any | IGNORE: should allow transactional tables to do partial transactions |
32521 | 2007-11-20 13:51 | 2008-09-25 9:52 | MySQL Server: DDL | No Feedback (6002 days) | S3 | 5.0.46 | Windows | Any | MySQL fails to create table where keynames matches to the constraint names. |
60516 | 2011-03-17 15:26 | 2011-11-24 11:33 | MySQL Server: DML | Closed (4847 days) | S1 | 5.5.10 | Linux (Fedora 14) | Any | UPDATE within a function fails and causes infinite loop |
98345 | 2020-01-24 9:32 | 2020-02-17 13:26 | MySQL Workbench | Verified (1840 days) | S3 | 8.0.19 | Windows | x86 | MySQL Workbench crashes during update model |
108990 | 2022-11-03 14:59 | 2022-11-22 13:04 | MySQL Server: Charsets | Can't repeat (831 days) | S3 | 8.0.29 | Debian (11) | x86 | Update integer value via integer key raises collation error |
15189 | 2005-11-23 15:59 | 2011-02-16 23:43 | MySQL Server: DML | Verified (7039 days) | S4 | 5.0.17-BK | Any | Any | Optimise INSERT ... ON DUPLICATE KEY ... for identical column values |
25511 | 2007-01-10 0:03 | 2007-07-18 17:53 | MySQL Server: Federated storage engine | Closed (6437 days) | S3 | 5.2.0, 5.0.38-bk | Linux (SUSE 10.0 / 64-bit) | Any | Federated: INSERT failures |
29941 | 2007-07-20 19:19 | 2013-02-20 22:37 | Connectors: DBD::mysql ( Perl ) | Unsupported (4393 days) | S3 | 4.005 | Any (Sun Solaris 8, Mac OS X) | Any | Perl affected row count incorrect for certain cases of ON DUPLICATE KEY UPDATE |
37792 | 2008-07-02 3:55 | 2008-07-25 19:20 | MySQL Server: InnoDB storage engine | Not a Bug (6064 days) | S5 | mysql community 5.0.41 | Windows (XP sp2) | Any | dead lock and slow insert |
59248 | 2010-12-31 23:31 | 2013-01-22 19:06 | MySQL Server: DML | Closed (4422 days) | S2 | 5.5.8, 5.5.20 | Any | Any | code review: write_row() crashes on INSERT...DUPLICATE KEY UPDATE |
76551 | 2015-03-31 22:31 | 2016-01-16 20:31 | MySQL Server: InnoDB storage engine | Verified (3623 days) | S1 | 5.6 | Linux (centos) | Any | Query hangs on INSERT INTO...SELECT... ON DUPLICATE KEY UPDATE |
92813 | 2018-10-17 4:54 | 2018-10-17 9:47 | MySQL Server: InnoDB storage engine | Verified (2328 days) | S3 | 5.7.15-log MySQL Community Server (GPL) | CentOS | Any | insert ..on duplicate key update return 0 rows affected |
53079 | 2010-04-22 19:04 | 2023-02-12 20:45 | MySQL Server: Replication | Duplicate (5233 days) | S2 | 5.1.45, 5.1, 5.6.99 | Any | Any | due to a trigger, replication fails with DUPLICATE KEY error for an UPDATE |
62225 | 2011-08-22 9:28 | 2011-08-22 10:36 | MySQL Server: Errors | Not a Bug (4941 days) | S2 | 5.1.53 | Windows (7) | Any | Update with unique column of type TIMESTAMP |
241 | 2003-04-07 17:24 | 2003-04-23 2:27 | MySQL Server: InnoDB storage engine | Closed (7984 days) | S2 | 4.0.12 | sparc-sun-solaris2.8 | Any | UPDATE ... ORDER BY does not work with InnoDB |
16494 | 2006-01-13 20:09 | 2006-08-18 17:07 | MySQL Server: Federated storage engine | Closed (6771 days) | S1 | 5.0.18/5.0.19 BK/5.0.24 | Linux (Linux) | Any | Updates that set a column to NULL fail sometimes |
32471 | 2007-11-17 16:01 | 2007-11-29 15:37 | MySQL Server: General | Not a Bug (6303 days) | S3 | 5.0.45, 4.1, 5.0, 5.1 BK | Any (Linux, Windows) | Any | Conditional update statement not working as expected |
13778 | 2005-10-05 18:41 | 2011-02-16 23:43 | MySQL Server: InnoDB storage engine | Closed (5371 days) | S1 | 5.0/4.1.15 | Windows (Windows XP Professional SP2 Engl) | Any | If FOREIGN_KEY_CHECKS=0, one can create inconsistent FOREIGN KEYs |
32764 | 2007-11-27 11:43 | 2014-05-15 22:33 | MySQL Workbench | Not a Bug (3944 days) | S2 | 5.0.9 | Windows (Vista) | Any | Forward Engineer fails to create foreign key constraints |
48753 | 2009-11-13 8:27 | 2021-05-02 20:45 | MySQL Cluster: Cluster (NDB) storage engine | No Feedback (5536 days) | S3 | mysql-5.1-telco-7.0 | Linux | Any | Search an ordered index after update sometimes fails |
89094 | 2018-01-02 14:06 | 2018-01-03 8:07 | MySQL Server: DML | Can't repeat (2615 days) | S2 | 5.7.19 | Debian | Any | Data inconsistency on master after upgrading to 5.7.19 |
100023 | 2020-06-28 16:31 | 2023-06-12 12:27 | MySQL Server: Documentation | Verified (1705 days) | S3 | 8.0.20 | Any | Any | Foreign Key Update Cascade FAILS on 2+ Tables Where BOTH are Parent and Child |
108015 | 2022-07-28 17:02 | 2022-07-29 12:04 | MySQL Server | Duplicate (947 days) | S2 | 8.0.29,8.0.30 | Linux (Ubuntu/CentOS) | x86 | select under repeatable read isolation level returns stale version of data |
103287 | 2021-04-12 13:57 | 2021-06-04 6:32 | Connector / ODBC | Closed (1367 days) | S3 | 8.0.23 | Any | Any | SQLSetPos(SQL_DELETE) does not produce diagnostic for duplicate key |
9689 | 2005-04-06 17:37 | 2005-04-22 21:10 | MySQL Server: Optimizer | Not a Bug (7254 days) | S3 | 4.1.11 | Any (*) | Any | wrong result for subselect in on duplicate key update (query cache) |
14887 | 2005-11-11 21:33 | 2011-02-16 23:43 | MySQL Server | Duplicate (5191 days) | S4 | 5.0.15-standard-log | Linux (Linux) | Any | Allow Insert Trigger to call simple UPDATE on same table trigger is based |
20104 | 2006-05-27 10:03 | 2006-12-29 18:30 | Connectors: DBD::mysql ( Perl ) | Closed (6638 days) | S3 | 3.0004, older versions | Linux (SuSE 9.3, Debian, Ubuntu) | Any | DBD::MySQL loses data (with dbh->do in subroutine) |
31724 | 2007-10-20 7:54 | 2015-03-15 20:45 | MySQL Server: MyISAM storage engine | No Feedback (5329 days) | S3 | mysql-5.1.22-rc-linux-x86_64-icc-glibc23 | Linux (Debian 2.6.18-5-amd64) | Any | UPDATE not properly using indexes |
40113 | 2008-10-17 15:51 | 2011-02-16 23:43 | MySQL Server: Locking | Closed (5686 days) | S2 | 5.0, 5.1, 6.0 bzr | Any (Linux, Win XP SP2 32bit) | Any | Embedded SELECT inside UPDATE or DELETE can timeout without error |
64779 | 2012-03-27 16:52 | 2012-08-24 23:52 | Connector / NET | Closed (4573 days) | S3 | 6.5.4 | Any | Any | Cascading delete using CreateDatabase in Entity Framework |
93410 | 2018-11-29 16:57 | 2019-02-21 2:39 | MySQL Server: DML | Closed (2201 days) | S1 | 8.0.13 | CentOS | Any | Insert is fine but "On Duplicate Update" updating wrong data |
1812 | 2003-11-11 22:54 | 2003-12-13 16:43 | MySQL Server: MyISAM storage engine | Closed (7750 days) | S2 | 4.0.16 | Windows (Windows XP) | Any | Table Corruption possibly due to "DELETE FROM TABLE" |
10931 | 2005-05-27 20:54 | 2005-06-21 11:00 | MySQL Server | Closed (7194 days) | S2 | 4.1.x | Any (All) | Any | Hostname cache completely broken in 4.1 |
13024 | 2005-09-06 23:04 | 2011-02-16 23:43 | MySQL Server: Optimizer | Verified (7116 days) | S4 | 4.1.14, 5.0.11 | Any | Any | optimizer does not use index when where has (field1,field2,..)=(value1,value2,. |
22838 | 2006-09-29 18:21 | 2016-02-25 12:24 | MySQL Cluster: Cluster (NDB) storage engine | Closed (6695 days) | S3 | 5.1.11-beta | Linux (Linux) | Any | NDB INSERT fails on table with unique key for ERROR 1296 |
33134 | 2007-12-11 10:57 | 2022-12-04 20:45 | MySQL Server: DDL | Verified (6291 days) | S3 | 5.0.51 | Any | Any | describe table output wrong for unique key when primary key is dropped |
34078 | 2008-01-26 14:19 | 2020-05-03 20:45 | MySQL Server: Optimizer | Verified (6218 days) | S3 | 4.1,5.0,5.1,6.0-BK | Any (Linux) | Any | ref access is not used for varchar column |
46041 | 2009-07-08 14:32 | 2011-02-16 23:44 | MySQL Workbench | No Feedback (5685 days) | S3 | 5.1.16 OSS | Windows (XP SP3) | Any | Problem on the export alter SQL script : error 1025 |
47770 | 2009-10-01 17:46 | 2012-05-18 20:19 | MySQL Server: Locking | Duplicate (5608 days) | S3 | 6.0 | Any | Any | 100% CPU loop in the MDL_context::wait_for_locks hash |
60884 | 2011-04-15 20:31 | 2011-04-27 12:05 | MySQL Server: Logging | Verified (5065 days) | S4 | Ver 14.12 Distrib 5.0.91 | Linux (CentOS 5.5) | Any | Enable logging of all errors to the error log |
67831 | 2012-12-06 20:48 | 2017-03-01 1:00 | MySQL Workbench: Migration | No Feedback (2924 days) | S3 | 5.2.44 CE | Windows (TypeError: cannot concatenate 'str' and 'NoneType' objects) | Any | TypeError: cannot concatenate 'str' and 'NoneType' objects |
77538 | 2015-06-29 11:06 | 2015-06-29 11:35 | MySQL Server: MyISAM storage engine | Verified (3534 days) | S2 | 5.1/5.5/5.6/5.7 | Linux | Any | MyISAM accepts table definition that is no longer considered as correct |
78369 | 2015-09-08 14:48 | 2015-09-14 9:16 | Connector / NET | Can't repeat (3457 days) | S2 | 6.9.3 | Windows | Any | Connector/NET 6.9.7 (Upgrading Connector/NET 6.9.3) Failed |
90573 | 2018-04-23 13:14 | 2018-10-09 16:07 | MySQL Server | Can't repeat (2336 days) | S1 | 5.6.40 | FreeBSD (11.1) | Other (amd64) | MySQL crash |
104712 | 2021-08-24 16:55 | 2021-10-08 16:16 | MySQL Server: Replication | Verified (1241 days) | S3 | 5.7.35 | Any | Any | IMPLICITLY added NOT NULL constraint missing in the binary log |
115843 | 2024-08-15 8:26 | 2024-08-21 8:04 | MySQL Server: Optimizer | Verified (193 days) | S2 | 8.0.32, 8.0.39 | Any | Any | The incorrect calculation of 'select_limit' led to an incorrect index selection |
86078 | 2017-04-25 19:14 | 2018-04-12 7:51 | MySQL Server: Replication | Closed (2516 days) | S2 | 8.0.1 | Any | Any | Bad Write Set tracking with UNIQUE KEY on a DELETE followed by an INSERT. |
31089 | 2007-09-18 21:20 | 2007-09-19 1:04 | MySQL Server: Compiling | Not a Bug (6374 days) | S3 | 5.0.45 | Linux (Debian Sarge) | Any | InnoDB unsafe binlog test fails with wrong error |
69939 | 2013-08-06 12:49 | 2013-08-12 3:02 | MySQL Server: InnoDB storage engine | Duplicate (4220 days) | S2 | MySQL-server-5.6.10 | Any (RHEL6 64-bit , kernel 2.6.32-71.el6.x86_64) | Any | ALTER TABLE for Adding Foreign Key crashes MySql Server after disabling FK Check |
2518 | 2004-01-26 11:10 | 2005-03-21 22:18 | MySQL Server: Replication | Not a Bug (7286 days) | S2 | 4.0.17 | Linux (Linux) | Any | Replication |
25828 | 2007-01-24 14:01 | 2007-01-24 16:13 | MySQL Server: Falcon storage engine | Closed (6612 days) | S2 | mysql-5.2.0-falcon-alpha-win32 | Windows (Win XP) | Any | Falcon compound primary key problem |
44170 | 2009-04-08 22:55 | 2011-02-16 23:43 | MySQL Server | No Feedback (5757 days) | S2 | 5.1.30 | Solaris (OpenSolaris December 2008 build) | Any | Unexpected errors with certain selects |
59952 | 2011-02-04 17:20 | 2014-03-16 11:44 | MySQL Server: Optimizer | Verified (5105 days) | S3 | 5.1.55-community, 5.6.3 | Any | Any | distinct ,distinct_key,group_key |
92530 | 2018-09-21 15:48 | 2023-01-18 1:58 | MySQL Server: Errors | Closed (2064 days) | S3 | 5.6.35 | Any | Any | Contribution by Facebook: Add more information to duplicate key error |
110092 | 2023-02-16 6:43 | 2023-02-23 13:17 | MySQL Server | Not a Bug (738 days) | S3 | 5.7.34-log | CentOS (CentOS Linux release 7.6.1810 (Core)) | Any | unique key has duplicate data. |
573 | 2003-06-03 6:45 | 2003-07-03 5:36 | MySQL Server: Replication | Closed (7913 days) | S3 | 4.0 | Any (all) | Any | slave prints an incomplete error message when LOAD DATA INFILE gives dup entry |
5263 | 2004-08-27 20:12 | 2004-09-06 13:41 | MySQL Server | Closed (7482 days) | S3 | 5.0.2-alpha-debug | Linux (SuSE 8.2) | Any | Views: crash if INSERT ... ON DUPLICATE KEY |
6126 | 2004-10-16 9:19 | 2004-11-22 18:10 | MySQL Server: InnoDB storage engine | Closed (7405 days) | S3 | 4.1.5 | Any | innodb index with duplicate column gives missleading error message | |
10855 | 2005-05-25 8:56 | 2005-06-26 6:35 | MySQL Server | Can't repeat (7189 days) | S1 | 5.0.4 | Windows (Windows XP sp2) | Any | Duplicate key error in select AFTER RESET QUERY CACHE |
12083 | 2005-07-21 14:31 | 2005-07-22 10:23 | MySQL Server | Closed (7163 days) | S2 | 4.0.20 | Windows (XP, Debian, SuSE) | Any | Error 'Duplicate entry' on REPLACE INTO on replication slave |
14446 | 2005-10-28 22:52 | 2005-11-29 16:00 | MySQL Server | No Feedback (7033 days) | S3 | 5.0.15 | Windows (WIN XP SP1) | Any | 230000 DUPLICATE ENTRY 'xxxxxxx' FOR KEY 1 |
22337 | 2006-09-14 10:28 | 2012-05-18 20:19 | MySQL Server: Charsets | Duplicate (6711 days) | S4 | 5.0.x, 4.1.21, 4.1.10 | Linux (Linux, Windows) | Any | Collation change results in duplicate key ("e" and "é" mixup) |
24762 | 2006-12-01 21:41 | 2011-02-16 23:43 | MySQL Server | Verified (5608 days) | S1 | 4.1.20,5.0.60,5.1.38,5.1.40 | Linux (CentOS,Mac OSX) | Any | Failure to import data (timestamp) |
30282 | 2007-08-07 18:42 | 2021-05-23 20:45 | MySQL Server: Falcon storage engine | Duplicate (5918 days) | S2 | 6.0-falcon | Any | Any | Falcon: duplicate-key error for value that ends with 0x00 |
38701 | 2008-08-10 17:50 | 2011-02-16 23:43 | MySQL Server | Closed (5980 days) | S1 | 5.1.28,6.0.7 | Any | Any | Crash in String::append when inserting duplicate empty strings an uft8 SET col |
39186 | 2008-09-02 13:49 | 2008-10-18 15:56 | MySQL Server | Closed (5979 days) | S3 | 6.0 | Any | Any | Crash in String::append when inserting duplicate empty strings an uft8 SET col |
46144 | 2009-07-13 10:32 | 2010-05-26 18:01 | MySQL Server: Falcon storage engine | Unsupported (5394 days) | S2 | falcon-team | Any | Any | Falcon indexes may become corrupt |
57782 | 2010-10-27 19:32 | 2021-05-02 20:45 | MySQL Cluster: Cluster (NDB) storage engine | Verified (3330 days) | S3 | mysql-5.1-telco-7.1 | Any | Any | ndb_restore does not warn of possible duplicate keys when using UNIQUE indexes |
102928 | 2021-03-11 14:14 | 2021-04-24 15:43 | MySQL Server: Japanese Documentation | Closed (1408 days) | S3 | 8.0.23 | Any | Any | 1.3 MySQL 8.0 の新機能(InnoDB の拡張機能(途中)~) |
4386 | 2004-07-02 20:41 | 2004-07-07 18:02 | Connector / NET | Closed (7543 days) | S2 | Any | Inserted data doesn't update properly | ||
44849 | 2009-05-13 16:04 | 2013-05-29 6:08 | Connector / ODBC | Closed (4295 days) | S1 | 5.1 | Windows | Any | Cannot update records in a table with a column of type CHAR(3) UNICODE PRIMARY |
66127 | 2012-07-31 18:00 | 2012-09-08 1:00 | MySQL Server: Information schema | No Feedback (4560 days) | S2 | 5.5.25a | Solaris (S11 - MySQL built from source) | Any | SHOW FULL COLUMNS: Behaviour change:-( |
23383 | 2006-10-17 17:42 | 2006-11-30 20:21 | MySQL Server: C API (client library) | Closed (6667 days) | S3 | 5.0.26/4.1/5.1BK | Linux (SuSE 10.1, 2.6.16.21-0.25-def) | Any | mysql_affected_rows() returns different values than mysql_stmt_affected_rows() |
5686 | 2004-09-21 19:37 | 2005-11-30 17:43 | MySQL Server: MyISAM storage engine | Closed (7032 days) | S1 | 4.1.8 | Linux (linux 2.4.26) | Any | #1034 - Incorrect key file for table - only utf8 |
35334 | 2008-03-17 12:48 | 2022-09-04 20:45 | MySQL Server: Optimizer | Verified (6158 days) | S4 | 5.0 all | Any | Any | For MyISAM select * from table order by key_field does not use index |
43895 | 2009-03-26 18:45 | 2014-07-14 15:31 | MySQL Server: DML | Closed (3884 days) | S3 | 5.1 bzr | Any | Any | Multi-DELETE IGNORE does not report warnings |
25009 | 2006-12-12 14:33 | 2007-02-22 14:10 | Connector / J | Closed (6583 days) | S3 | Any | ResultSet is from UPDATE. No Data | ||
43360 | 2009-03-04 10:10 | 2011-02-16 23:43 | MySQL Server: Optimizer | Closed (5214 days) | S3 | 6.0-bzr | Linux (Ubuntu 8.04) | Any | Server crash with a simple multi-table update (InnoDB table) |
96205 | 2019-07-15 9:05 | 2019-07-15 15:11 | MySQL Server: InnoDB storage engine | Not a Bug (2057 days) | S3 | Any | Any | not in expect, two versions row datas in a some transaction | |
98088 | 2019-12-28 5:54 | 2020-02-25 14:47 | MySQL Server: DML | Can't repeat (1832 days) | S3 | 8.0.18 | Any | x86 | Unique index is functioned unexpectedly when entire records are updated target |
10400 | 2005-05-06 2:39 | 2005-05-23 2:10 | MySQL Server: MyISAM storage engine | Closed (7223 days) | S1 | 4.1.12 forward | Any | Improperly-defined MERGE table crashes with INSERT ... ON DUPLICATE KEY UPDATE | |
12054 | 2005-07-20 13:44 | 2014-03-13 13:34 | MySQL Cluster: Cluster (NDB) storage engine | Won't fix (7153 days) | S3 | 4.1.12 (max) | Linux (Linux) | Any | ON DUPLICATE KEY UPDATE fails in ndb table |
13460 | 2005-09-24 14:22 | 2019-10-10 21:42 | MySQL Server: DML | Won't fix (1970 days) | S4 | * | Any (*) | Any | Allow delayed insert with on duplicate key update |
18260 | 2006-03-15 17:08 | 2015-08-10 14:33 | MySQL Server: mysqldump Command-line Client | Verified (6926 days) | S4 | 5.0.18 | Linux (Debian) | Any | mysqldumpslow doesn't properly handle multi-row inserts/updates |
23200 | 2006-10-12 8:18 | 2006-11-02 10:00 | MySQL Cluster: Cluster (NDB) storage engine | Closed (6695 days) | S2 | 4.1, 5.0, 5.1 | Linux (FC 5 / Suse 10.1) | Any | Cluster INSERT INTO .. ON DUPLICATE KEY UPDATE locks and memory leaks |
25831 | 2007-01-24 15:32 | 2007-03-06 19:54 | MySQL Server | Closed (6571 days) | S3 | 5.0.36-bk, 5.1.15-bk | Linux (Linux Suse 10.1) | Any | Deficiencies in INSERT ... SELECT ... field name resolving. |
26261 | 2007-02-10 20:17 | 2007-03-19 17:41 | MySQL Server | Closed (6558 days) | S3 | 5.0bk, 5.1.15 | Windows (Windows XP) | Any | Missing default value isn't noticed in insert ... on duplicate key update |
27968 | 2007-04-20 0:47 | 2007-04-20 7:47 | MySQL Server: General | Duplicate (6526 days) | S3 | 5.0.36 | Any | Any | On Duplicate Key Update Fails |
28638 | 2007-05-23 23:11 | 2007-07-26 22:03 | MySQL Server | No Feedback (6429 days) | S3 | 5.0.37-community-nt | Windows (Windows Vista, 32bit) | Any | INSERT ... ON DUPLICATE KEY UPDATE broken |
29212 | 2007-06-19 13:42 | 2007-06-20 5:00 | MySQL Server: InnoDB storage engine | Duplicate (6465 days) | S2 | 5.0.37 | Linux | Any | LAST_INSERT_ID doesn't work for innodb on "on duplicate key update" |
31892 | 2007-10-26 21:48 | 2007-10-26 22:47 | MySQL Server: Query Cache | Closed (6337 days) | S3 | 5.0.37-community-nt-log | Windows (Windows 2000 5.00.2195 SP4) | Any | ON DUPLICATE KEY UPDATE does not refresh query cache. |
34973 | 2008-03-01 18:05 | 2008-03-04 8:36 | MySQL Server: Federated storage engine | Not a Bug (6207 days) | S2 | 5.1.23-rc-community | Windows | Any | Insert ... on duplicate key update problem with federated tables |
39584 | 2008-09-22 11:10 | 2008-09-22 19:52 | MySQL Server: Data Types | Not a Bug (6005 days) | S3 | 5.0.45 | Windows | Any | Treating unsigned BIGINT as signed BIGINT in INSERT ON DUPLICATE KEY UPDATE |
45081 | 2009-05-25 22:10 | 2014-11-28 6:21 | MySQL Server: DML | Not a Bug (5759 days) | S3 | 5.1.34-community | Any | Any | Insertion anomaly for ON DUPLICATE KEY UPDATE |
60838 | 2011-04-12 2:01 | 2011-05-12 23:00 | MySQL Server: DML | No Feedback (5043 days) | S2 | Ver 14.12 Distrib 5.0.91 | MacOS | Any | on duplicate key update -- lost data |
65544 | 2012-06-06 20:56 | 2012-08-26 16:13 | Connector / J | Closed (4571 days) | S3 | Any | Any | launchpad is out of date for the connector/j branhc | |
71188 | 2013-12-20 13:05 | 2013-12-20 23:06 | MySQL Server: Data Types | Not a Bug (4090 days) | S3 | 5.5 - 5.6.15 | Linux | Any | Strange beheavior ON DUPLICATE KEY UPDATE when auto_increment reaches MAXINT |
77087 | 2015-05-19 8:32 | 2015-06-02 12:47 | MySQL Server: InnoDB storage engine | Closed (3569 days) | S3 | 5.7.8 | Any | Any | INNODB FTS: error duplicate entry in FTS_DOC_ID_INDEX ON UPDATE CASCADE |
83090 | 2016-09-22 2:13 | 2016-09-22 7:26 | MySQL Server: Row Based Replication ( RBR ) | Verified (3083 days) | S1 | 5.7.13, 5.7.15 | Any | Any | AUTO_INCREMENT not updated when using INSERT ON DUPLICATE KEY UPDATE |
84365 | 2016-12-29 2:44 | 2021-12-18 22:54 | Connector / J | Closed (1170 days) | S3 | 8.0.26 | Any | Any | INSERT..VALUE with VALUES function lead to a StringIndexOutOfBoundsException |
96521 | 2019-08-13 12:10 | 2019-08-22 12:47 | MySQL Server: Optimizer | Not a Bug (2027 days) | S3 | 8.0.17 | Any | Any | on duplicate key update [1048] [23000]: Column 'NAME' cannot be null |
96540 | 2019-08-14 20:19 | 2019-08-29 20:14 | MySQL Server: Errors | Can't repeat (2012 days) | S2 | 5.6.22, 5.6.34 | Any | Any | Error 1022 on INSERT/UPDATE to InnoDB table with a fulltext index defined |
99604 | 2020-05-16 19:04 | 2022-12-21 18:05 | Connector / J | Closed (836 days) | S3 | 8.0.20 | Any | Any | Add support to row alias on INSERT... ON DUPLICATE KEY UPDATE on batch mode |
101304 | 2020-10-24 4:58 | 2020-10-24 14:19 | MySQL Server: DML | Verified (1590 days) | S2 | 5.7 thru 8.0.21 | Debian (Buster) | x86 (KVM VM) | mysql 5.7, 8 insert on duplicate key update on view inserts nothing without err |
104211 | 2021-07-05 20:54 | 2021-07-08 11:35 | MySQL Server: Parser | Not a Bug (1334 days) | S3 | 8.0.x | Any | Any | ON DUPLICATE KEY UPDATE and table alias for new VALUES function replacement |
108379 | 2022-09-05 7:58 | 2022-09-20 22:29 | Connector / J | Duplicate (894 days) | S3 | 8.0.29, 8.0.30 | Any | Any | Recognize "ON DUPLICATE KEY UPDATE" in "INSERT SET" Statement |
111183 | 2023-05-29 9:46 | 2023-05-29 13:21 | MySQL Server: DML | Verified (643 days) | S3 | 5.7 | Any | Any | When use ON DUPLICATE UPDATE syntax, TIMESTAMP in primary key, get wrong answer |
111441 | 2023-06-15 18:53 | 2023-06-22 17:57 | MySQL Server: DML | Closed (619 days) | S6 | 8.0.33 | Ubuntu (20.04 LTS) | x86 (Intel(R) Core(TM) i7-10700 CPU) | bool Sql_cmd_dml::prepare(THD*): Assertion `thd->is_error()' failed. |
5573 | 2004-09-14 16:58 | 2018-09-09 20:45 | MySQL Server: InnoDB storage engine | Verified (6172 days) | S4 | Any | Any | Wrong/undocumented behaviour on UNIQUE column mass update | |
34228 | 2008-02-01 13:55 | 2018-09-09 20:45 | MySQL Server: DML | Verified (6237 days) | S4 | * | Any | Any | Bulk Update statement |
236 | 2003-04-06 13:56 | 2003-05-15 7:59 | MySQL Server | Can't repeat (7962 days) | S2 | 4.0.11-gamma-max | FreeBSD (FreeBSD 4.7-RELEASE) | Any | Multi-table update denied to user who has all privleges |
6211 | 2004-10-22 11:04 | 2004-11-01 14:33 | MySQL Server: InnoDB storage engine | Not a Bug (7426 days) | S2 | 4.0.18 | Linux (linux) | Any | Problem with InnoDB and Locking on Update |
14412 | 2005-10-27 21:46 | 2007-11-06 15:27 | Connector / NET | Duplicate (6326 days) | S4 | 1.0 | Windows (Windows 2000) | Any | MySqlCommandBuilder does not automatically open connections for update |
15166 | 2005-11-23 0:39 | 2006-02-14 3:15 | MySQL Server | Closed (6956 days) | S2 | Any | Wrong update [was: select/update] permissions required to execute triggers | ||
17399 | 2006-02-14 20:47 | 2006-05-05 16:39 | MySQL Server | No Feedback (6876 days) | S1 | 5.0.16 | Windows (Windows Server 2003) | Any | Multi-table DELETE statement fails, identical SELECT statement works |
18269 | 2006-03-16 7:01 | 2006-04-26 4:33 | MySQL Server | Not a Bug (6885 days) | S3 | 4.1.12-log | Linux (Red Hat Enterprise Linux ES) | Any | update query's problem (about atomical property) |
29883 | 2007-07-18 23:48 | 2023-02-19 20:45 | Connector / ODBC | Duplicate (6234 days) | S2 | 3.51.17 | Windows (xp sp 2) | Any | MyODBC 3/ADO recordset update if SQL includes a Limit clause |
41509 | 2008-12-16 14:25 | 2018-09-25 21:50 | Tests: Engine | Can't repeat (5918 days) | S7 | 6.0 | Any | Any | falcon_bug_22212 fails sporadically: query 'reap' succeeded - should have failed |
46044 | 2009-07-08 15:38 | 2011-02-16 23:44 | MySQL Server: Locking | Closed (5474 days) | S3 | 5.4 | Any | Any | MDL deadlock on LOCK TABLE + CREATE TABLE HIGH_PRIORITY FOR UPDATE |
47010 | 2009-08-31 9:36 | 2013-05-29 6:07 | Connector / ODBC | Closed (4295 days) | S3 | 5.1 | Windows (windows 2008 web server) | Any | Mysql mediumtext update problem on ADDNEW method |
53779 | 2010-05-19 7:17 | 2011-02-16 23:44 | MySQL Server: Logging | Duplicate (5401 days) | S3 | 5.1-bugteam, pe | Any | Any | mtr --debug was broken by bugfix 52629 |
55440 | 2010-07-21 12:54 | 2010-07-21 18:44 | Connector / NET | Not a Bug (5338 days) | S1 | Connector .NET Beta 6.3.2 | Windows (Seven - VS 2010 ) | Any | .NET FormView Update with DataSet generated -- |
57629 | 2010-10-21 13:56 | 2012-05-18 20:19 | Connector / NET | No Feedback (4993 days) | S1 | 6.3.5.0 | Windows (7 prof) | Any | Update statement bug (last_insert_id) when using mySQL <-> EF4 Code-Only |
63122 | 2011-11-06 22:51 | 2020-06-18 9:14 | MySQL Server: InnoDB storage engine | Verified (4863 days) | S3 | 5.0+ | Any | Any | "Searched SQL update" seems to release lock got by "select for update" |
68198 | 2013-01-28 6:59 | 2013-01-29 15:32 | MySQL Server: Stored Routines | Not a Bug (4415 days) | S2 | 5.5.29 | Windows (8) | Any | Incorrect usage of UPDATE and ORDER BY |
87420 | 2017-08-15 11:42 | 2017-08-25 11:57 | MySQL Server: Security: Privileges | Verified (2755 days) | S3 | 5.6.36, 5.6.37, 5.5.56, 5.7.19 | CentOS (7.3.1611) | Any | GRANTS using general and specific permissions |
101478 | 2020-11-05 13:46 | 2020-12-03 23:40 | MySQL Package Repos | Duplicate (1578 days) | S2 | 5.7 | Red Hat (Release 7.8) | x86 | yum update of mysql-connector-python fails |
110126 | 2023-02-19 10:40 | 2023-04-15 1:00 | Connector / NET | No Feedback (688 days) | S1 | 8.0.32 | Any | Any | Incorrect datetime value - MySQL 8.0.32 - Entity framework |
111992 | 2023-08-08 3:30 | 2023-08-08 12:45 | MySQL Server: JSON | Duplicate (572 days) | S3 | 8.0 | Any (azure mysql single server) | Any | cannot update null value into nullable field when using UPDATE JOIN JSON_TABLE |
102831 | 2021-03-05 16:32 | 2021-04-19 6:39 | MySQL Server: InnoDB storage engine | Verified (1457 days) | S2 | 5.7.31, 5.7.33 | Any (CentOS, Ubuntu) | Any | transaction-isolation level is not honored when changed at session level |
11021 | 2005-06-01 18:09 | 2008-11-14 16:18 | MySQL Server | Closed (5952 days) | S4 | 3.23 to current | Windows (Windows XP) | Any | "Dublicate Entry '#####' for key 1" when it should not occur |
25034 | 2006-12-13 10:54 | 2008-06-18 11:20 | MySQL Server: General | Won't fix (6101 days) | S2 | 5.0 & 5.1 | Any (Any) | Any | MySQL does not correctly handle errors on statement commit |
39670 | 2008-09-26 14:22 | 2010-05-26 17:59 | MySQL Server: Falcon storage engine | Unsupported (5394 days) | S3 | 6.0-falcon-team (6.0.8a) | Any | Any | Error on rename (errno: 121) from ALTER TABLE ADD KEY in concurrent test |
89210 | 2018-01-12 15:43 | 2018-01-13 6:34 | MySQL Utilities | Duplicate (2605 days) | S2 | 1.6.5 | MacOS | Any | mysqldcompare erroneously includes database name differences in SQL output |
91049 | 2018-05-28 17:38 | 2018-06-08 14:02 | MySQL Server | Not a Bug (2461 days) | S3 | 5.5.38 | Any | Any | deleting duplicate complains about foreign key |
5103 | 2004-08-19 0:49 | 2016-12-04 20:45 | MySQL Server | Duplicate (6507 days) | S4 | 4.0.20-standard | Linux (Linux) | Any | Cannot add or update a child row: a foreign key constraint fails |
56046 | 2010-08-17 9:12 | 2011-02-16 23:44 | MySQL Server: Locking | No Feedback (5279 days) | S1 | 5.1.46sp1-enterprise-gpl-pro-log | Linux (Red Hat Enterprise Linux Server release 5.3 (Tikanga) x86_64) | Any | 'SELECT ... FOR UPDATE' locked another table's index |
80471 | 2016-02-23 9:05 | 2017-02-17 12:20 | MySQL Cluster: Cluster (NDB) storage engine | Not a Bug (2935 days) | S3 | 7.x | Any | Any | Via a secondary unique index is automatically upgraded to a Shared read lock |
9680 | 2005-04-06 14:49 | 2011-02-16 23:43 | MySQL Server: InnoDB storage engine | Closed (5369 days) | S3 | 4.* | Linux (redhat) | Any | wrong error from cascading update |
77034 | 2015-05-14 3:52 | 2018-04-10 16:06 | MySQL Server | Unsupported (2518 days) | S2 | Percona 5.6.23-72.1 R 0503478 | Linux (Ubuntu 14.04LTS) | Any | Server crashes mid constraint-definition, then gets false 'duplicate key' error. |
10946 | 2005-05-29 21:15 | 2006-07-24 18:26 | MySQL Server: Stored Routines | Closed (6796 days) | S3 | 506-beta-log | Linux (Linux Suse 9.3) | Any | Confusing error messeges in the case of duplicate trigger definition |
13130 | 2005-09-13 6:35 | 2005-09-13 6:56 | MySQL Server | Not a Bug (7110 days) | S2 | 4.1 | Windows (windows advanced server) | Any | query based update failed the row to update do not found |
25563 | 2007-01-11 23:39 | 2012-05-18 20:19 | MySQL Cluster: Cluster (NDB) storage engine | No Feedback (6481 days) | S2 | 5.0.27 | Linux (RHEL4) | Any | Nested Triggers Produce Non-Existant Table |
42519 | 2009-02-01 15:36 | 2010-01-04 15:47 | MySQL Server: Maria storage engine | Closed (5778 days) | S2 | 6.0-maria | Any | Any | Maria: RESTORE leads to corrupted table and assertion |
54861 | 2010-06-28 11:50 | 2011-02-16 23:44 | MySQL Server: Embedded Library ( libmysqld ) | Closed (5264 days) | S3 | 5.5.6-m3 | Any | Any | Additional connections not handled properly in mtr --embedded |
74538 | 2014-10-24 7:38 | 2014-11-03 15:15 | MySQL Server: Replication | Open | S4 | All | Any | Any | Need to change the style of SQL apply on slave mode for Update statement |
78127 | 2015-08-18 12:16 | 2019-11-26 21:50 | MySQL Server: DML | Closed (1923 days) | S3 | 5.6.22, 5.5.46, 5.6.26 | Any | Any | In consistent behavior between similar UPDATE sqls, error vs warning |
101523 | 2020-11-09 11:01 | 2020-11-16 14:04 | MySQL Server: DML | Duplicate (1567 days) | S5 | 8.0.18, 8.0.22 | Linux | Any | "JSON partial update" does not work when updating a view |
106918 | 2022-04-05 17:46 | 2022-05-25 10:19 | MySQL Server: Row Based Replication ( RBR ) | Verified (1012 days) | S3 | 8.0.25 | Any | Any | master and slave may get serious in-consistence after add auto-increment as pk |
2754 | 2004-02-12 10:24 | 2004-03-26 11:05 | MySQL Server: Command-line Clients | No Feedback (7646 days) | S1 | 4.0.17 | MacOS (Mac OS X and RedHat 9) | Any | Index error when using order by and limit on indexes |
8429 | 2005-02-11 0:34 | 2005-02-25 18:09 | MySQL Server: Documentation | Closed (7310 days) | S2 | 4.1.9 | Linux (Debian unstable ('sid')) | Any | Can't create foreign keys on TINYTEXT fields |
11228 | 2005-06-10 8:40 | 2011-02-16 23:43 | MySQL Server: Documentation | Closed (5275 days) | S1 | 5.0.4-beta-standard-log | Linux (Linux) | Any | DESC shows arbitrary column as "PRI" |
16700 | 2006-01-21 13:13 | 2006-01-21 13:51 | MySQL Server | Duplicate (6980 days) | S3 | 5.0.18 | FreeBSD (FreeBSD 6.0-RELEASE-p3) | Any | optimizer marks subquery DEPENDENT though it's not |
18568 | 2006-03-28 7:41 | 2006-04-28 11:29 | MySQL Server | No Feedback (6883 days) | S1 | mysql-mysql-5.1.7-beta-linux-i686 | Linux (linux) | Any | some index can't create |
18744 | 2006-04-03 15:15 | 2006-09-06 23:20 | MySQL Server: Optimizer | Closed (6752 days) | S3 | 5.0.21-pre | Any | Test 'join_outer' fails if "classic" configuration in 5.0 | |
18745 | 2006-04-03 15:20 | 2006-05-22 18:27 | MySQL Server: Optimizer | Closed (6859 days) | S3 | 5.0.21-pre | Any | Test case 'func_group' fails if "classic" 5.0 configuration | |
19171 | 2006-04-18 18:12 | 2006-04-20 11:08 | MySQL Server | Can't repeat (6891 days) | S2 | 5.1.9-beta | Solaris (Solaris 8 Sparc (32)) | Any | Test "information_schema": Incorrect key file for table './mysql/event' |
19657 | 2006-05-09 22:03 | 2006-05-14 7:22 | MySQL Server: Documentation | Closed (6867 days) | S3 | 5.0.21/5.1 | Windows (Windows binary distribution) | Any | Proposition for YaSSL manual part correction |
20325 | 2006-06-07 22:11 | 2007-03-19 19:18 | Connectors: DBD::mysql ( Perl ) | Closed (6558 days) | S3 | 3.0004 | Linux (SLES 8) | Any | t/41bindparam.t: All parts of a PRIMARY KEY must be NOT NULL |
28766 | 2007-05-30 8:25 | 2007-06-05 15:05 | MySQL Server | Can't repeat (6480 days) | S1 | 5.1.20 | Any | Any | MySQL crashes when tables with many partitions opened |
28888 | 2007-06-05 1:25 | 2007-06-05 10:21 | MySQL Server: Data Types | Can't repeat (6480 days) | S3 | 4.0.25 | Any | Any | CAST on TEXT field returns BLOB when ORDERED BY |
29680 | 2007-07-10 6:38 | 2007-08-07 20:00 | MySQL Server: Documentation | Closed (6417 days) | S3 | 5.0.46-BK, 5.0.41 | Any | Any | index_merge is used instead of (faster!) range |
31373 | 2007-10-03 14:42 | 2007-11-10 23:51 | MySQL Server | No Feedback (6322 days) | S2 | 5.0.27-log | Linux | Any | Unusing index in select query |
31672 | 2007-10-17 18:21 | 2016-02-25 12:24 | MySQL Server: Optimizer | Not a Bug (6290 days) | S3 | 5.0.46 | Any | Any | EXPLAIN indicates multiple column index used when it is not |
37995 | 2008-07-09 15:42 | 2011-02-16 23:43 | MySQL Server: Embedded Library ( libmysqld ) | Closed (5686 days) | S3 | 5.1.26-rc | Any | Any | Error message truncation in test "innodb" in embedded mode |
45969 | 2009-07-06 12:23 | 2012-10-08 15:31 | MySQL Server: Optimizer | Closed (4528 days) | S3 | 5.1.35, 5.1.38-bzr | Windows (XP, Vista) | Any | the query otimizer choose the wrong index |
54951 | 2010-07-02 7:51 | 2011-07-27 21:32 | MySQL Server: DDL | Closed (4967 days) | S2 | 5.1.41-3ubuntu12.3, 5.1.49-bzr | Linux (Ubuntu) | Any | Creating a unique key across fields that have foreign keys, deletes first FK |
67683 | 2012-11-23 9:27 | 2013-01-02 22:13 | MySQL Workbench: Modeling | Duplicate (4442 days) | S3 | 5.2.44 | Windows (XP) | Any | WB claims it corrected problems in mwb file but same message re-appears |
68148 | 2013-01-22 21:10 | 2017-08-30 16:43 | MySQL Server: InnoDB storage engine | Closed (4332 days) | S1 | 5.5.27, 5.6.7 | Linux | Any | drop index on a foreign key column leads to missing table |
70002 | 2013-08-12 19:23 | 2013-08-19 7:38 | MySQL Server: Optimizer | Duplicate (4213 days) | S2 | 5.6.13, 5.5, 5.1 | Any | Any | very low performance join - eq_ref and ref access broken for compound indexes |
89958 | 2018-03-08 10:02 | 2018-03-13 8:04 | MySQL Workbench | Can't repeat (2546 days) | S3 | 5.7.21-0ubuntu0.16.04.1 | Windows (Server 2012 R2 Datacenter) | x86 (x64) | Bad export generated by Workbench: ALTER TABLE for UNIQUE KEY |
93332 | 2018-11-25 18:22 | 2018-11-26 9:08 | MySQL Workbench | Verified (2288 days) | S3 | 8.0.13 | Windows (Microsoft Windows 10 Pro) | Any | foreign key referencing 2 columns does not show up in schemas |
99746 | 2020-05-29 17:04 | 2020-05-30 4:04 | Connector / Python Documentation | Closed (1737 days) | S2 | Any | Any | wrong table definition in connector Python docs | |
102199 | 2021-01-08 14:04 | 2023-03-17 7:36 | MySQL Server: InnoDB storage engine | Can't repeat (716 days) | S3 | 8.0.22 | CentOS (7.9) | x86 | Data dictionary upgrading fails with encrypted tablespace |
105090 | 2021-09-30 17:23 | 2021-09-30 18:26 | MySQL Server: DDL | Verified (1249 days) | S3 | 5.7.35 | Any | x86 | FK cannot be created when the table has a UNIQUE KEY in a virtual generated col |
109357 | 2022-12-13 7:11 | 2022-12-13 12:55 | MySQL Server | Can't repeat (810 days) | S3 | Mysql Operator 8.0.31 | Ubuntu | x86 | TLS/SSL Certificates with MySQL Operator now working |
110071 | 2023-02-15 6:41 | 2023-02-15 8:11 | MySQL Server: Row Based Replication ( RBR ) | Verified (746 days) | S2 | Any, 5.7, 8.0 | Any | Any | Foreign Key should not be added to Writeset-based Dependency Tracking. |
29845 | 2007-07-17 13:10 | 2011-02-16 23:43 | MySQL Server: Optimizer | Verified (6319 days) | S4 | 6.0.0-alpha | Any | Any | GROUP BY does not make best use of indicies when evaluating SUM aggregates |
41984 | 2009-01-08 22:28 | 2011-02-16 23:43 | MySQL Server: InnoDB storage engine | Can't repeat (5816 days) | S3 | 5.1.22rc 5.1.30 GA | Any (Linux, Windows) | Any | inserts with auto-increment fails |
27140 | 2007-03-14 16:27 | 2007-03-15 17:44 | MySQL Server: InnoDB storage engine | Not a Bug (6562 days) | S2 | 5.0.38-BK, 5.0.37-community-nt | Linux (Linux, Windows XP SP2) | Any | SHOW CREATE TABLE and mysqldump does not show ON UPDATE/DELETE constraints |
40761 | 2008-11-15 19:17 | 2011-02-16 23:43 | MySQL Server: DML | Closed (5877 days) | S2 | 5.1.29/5.0/5.1/6.0 | Windows (WinXP (Intel-32)/Linux) | Any | LEFT JOIN on inline view crashes server |
70515 | 2013-10-03 19:01 | 2014-03-12 1:37 | MySQL Workbench: Modeling | Closed (4008 days) | S3 | 6.0.7 | Any | Any | Workbench cannot handle fractional timestamp |
72526 | 2014-05-03 17:47 | 2018-10-21 20:45 | Connector / NET | No Feedback (3681 days) | S2 | 6.8.3 | Any | Any | Fails to generate correct SQL for one-to-one relationships in Entity Framework 6 |
97462 | 2019-11-03 15:05 | 2019-11-12 16:37 | MySQL Server: Optimizer | Can't repeat (1937 days) | S5 | 8.0.17 | FreeBSD (12.0) | x86 | Slow JOIN with ORDER BY due wrong index selection |
102791 | 2021-03-03 5:03 | 2021-03-05 13:13 | MySQL Server | Not a Bug (1459 days) | S3 | 5.7.30 GA | Any | Any | A deadlock occurs one innodb tables between unrelated rows |
3591 | 2004-04-28 16:49 | 2004-04-28 18:50 | MySQL Server: Replication | Not a Bug (7613 days) | S2 | 4.0.18 | Linux (redhat 9) | Any | Replication sending Errored SQLs to Slave |
5520 | 2004-09-10 18:33 | 2004-09-10 20:58 | MySQL Server: MyISAM storage engine | Not a Bug (7478 days) | S2 | 4.0.20-standard | pc-linux | Any | Insert statement failing on duplicate key |
21072 | 2006-07-14 22:51 | 2007-12-14 20:32 | MySQL Cluster: Cluster (NDB) storage engine | Closed (6288 days) | S2 | 5.2 | Any | Any | Duplicate key error in NDB references wrong key |
23945 | 2006-11-03 15:59 | 2006-11-07 23:44 | MySQL Server: Falcon storage engine | Closed (6690 days) | S1 | Any | Any | crash during drop table, AUTOCOMMIT=0, CREATE TABLE .. AS SELECT | |
35487 | 2008-03-21 18:14 | 2008-03-28 14:37 | MySQL Server | Can't repeat (6183 days) | S1 | 5.0.37-community | Linux | Any | Duplicate Entry For Key error reports truncated key value |
36912 | 2008-05-23 11:36 | 2008-07-28 21:16 | MySQL Server: Errors | Can't repeat (6061 days) | S3 | 6.0-bk | Any | Any | wrong error messages |
43307 | 2009-03-02 13:25 | 2011-02-16 23:43 | MySQL Server: Documentation | Closed (5841 days) | S1 | 5.1, 6.0 | Any | Any | default collation will be ignored |
45885 | 2009-07-01 18:26 | 2010-05-26 17:59 | MySQL Server: Falcon storage engine | Unsupported (5394 days) | S3 | 6.0.12-bzr | Any | Any | Primary key added to Falcon table allows non-unique values. |
114133 | 2024-02-27 2:39 | 2024-02-27 12:38 | MySQL Server: InnoDB storage engine | Can't repeat (369 days) | S3 | 8.3.0-debug | Oracle Linux (v9, WSL v2 over Windows11) | x86 | dd corrupt assert lob0impl.cc:1237:total_read == len || total_read == avail_lob |
10563 | 2005-05-11 17:23 | 2007-07-03 19:05 | Connector / ODBC | Closed (6452 days) | S2 | 3.51.11 | Windows (Windows XP SP1) | Any | Update using multicolumn primary key with duplicate indexes fails |
13473 | 2005-09-25 22:49 | 2006-09-07 0:16 | MySQL Server: Documentation | Closed (6751 days) | S3 | 5.0.12 | * / windows | Any | Before insert trigger executed, without insert happening |
8565 | 2005-02-17 11:50 | 2022-12-04 20:45 | MySQL Server: DDL | Duplicate (4615 days) | S2 | 5.0.30 | Any (*) | Any | ALTER TABLE MODIFY adds duplicate keys which slow down SELECTs |
23873 | 2006-11-02 4:46 | 2006-11-02 6:51 | MySQL Server | Not a Bug (6695 days) | S3 | 5.0.27 | Windows (Win2003) | Any | SELECT statement works, but not done as CREATE VIEW AS |
26316 | 2007-02-13 12:01 | 2022-04-28 15:04 | MySQL Server: InnoDB storage engine | Closed (5324 days) | S2 | 5.0.36-BK, 5.0.32, 5.0.38BK, 5.1.17BK | Any (*) | Any | Triggers create duplicate entries on auto-increment columns |
32656 | 2007-11-23 12:33 | 2011-02-16 23:43 | MySQL Cluster: Cluster (NDB) storage engine | Closed (5639 days) | S1 | 5.1 | Any | Any | NDB: Duplicate key error aborts transaction in handler. Doesn't talk back to SQL |
44381 | 2009-04-21 12:28 | 2014-01-24 14:29 | MySQL Server: Falcon storage engine | Won't fix (4055 days) | S3 | 6.0-falcon-team | Linux | Any | sysbench v0.5 oltp_complex_rw.lua test fails with duplicate entry error |
46188 | 2009-07-15 3:31 | 2011-02-16 23:44 | MySQL Server: DDL | No Feedback (5678 days) | S2 | Any | Any | Server raises fatal exception if engine returns error during ONLINE ALTER | |
70060 | 2013-08-16 15:09 | 2018-04-24 1:00 | MySQL Server: Errors | No Feedback (2505 days) | S2 | 5.6 | Any | Any | "Access denied using password no" for slave w/ password, can't connect 2 slaves |
71896 | 2014-03-01 15:28 | 2014-04-04 1:00 | MySQL Workbench | No Feedback (3986 days) | S2 | 6.0 | MacOS (10.8.5) | Any | MySQLWorkbench crashes frequently on OSX |
82475 | 2016-08-05 13:40 | 2018-02-03 10:26 | MySQL Workbench: SQL Editor | Verified (2584 days) | S4 | 6.3.10 | Any | Any | duplicate values in column |
30943 | 2007-09-11 6:43 | 2007-09-11 6:47 | MySQL Server: User-defined functions ( UDF ) | Not a Bug (6382 days) | S2 | 5.1.21, 5.0.45 | Linux (SuSE-10) | Any | UPDATE where key depends on function VERY slow. |
55385 | 2010-07-20 4:51 | 2011-03-02 15:24 | MySQL Server: DML | Closed (5114 days) | S3 | mysql-next-mr-wl5136-stage, 5.1 | Any | Any | UPDATE statement throws an error, but still updates the table entries |
67637 | 2012-11-19 16:44 | 2013-01-22 13:50 | MySQL Server: Optimizer | Closed (4422 days) | S3 | 5.6.7, 5.6.8 | Any | Any | EXPLAIN UPDATE output doesn't match query execution |
80885 | 2016-03-29 12:59 | 2025-01-03 21:23 | MySQL Server: DML | Verified (3257 days) | S2 | 5.7.11 | Debian (Debian GNU/Linux 8 (jessie)) | Any | Not null update fails with an "Column cannot be null" error. |
82990 | 2016-09-14 12:29 | 2016-09-14 13:44 | MySQL Server: Parser | Duplicate (3091 days) | S3 | Any | Any | Multiple UPDATE query separated by 'AND' not detected Syntax Error | |
97418 | 2019-10-29 15:25 | 2020-01-28 4:10 | MySQL Server: Optimizer | Closed (1860 days) | S5 | 5.7, 5.7.28 | Any | Any | MySQL chooses different execution plan in 5.7 |
21059 | 2006-07-14 13:10 | 2006-08-17 8:51 | MySQL Cluster: Cluster (NDB) storage engine | Closed (6772 days) | S1 | 5.1.11, 5.0.19 | Linux (Linux) | Any | Server crashes on join query with large dataset with NDB tables |
26480 | 2007-02-19 17:31 | 2007-04-12 14:20 | MySQL Server: InnoDB storage engine | Not a Bug (6534 days) | S2 | 5.0 | Windows (Windows XP) | Any | on update cascade crashes when a foreign key belongs to the primary key |
103837 | 2021-05-28 9:32 | 2021-05-28 9:54 | MySQL Server: Logging | Verified (1374 days) | S4 | All, 8.0 | Any | Any | Suggest to add materialized view log for innodb tables |
113138 | 2023-11-20 7:43 | 2023-11-20 13:15 | MySQL Server | Not a Bug (468 days) | S3 | 8.2.0 | Any | Any | Optimization of MySQL query with LIMIT |
16324 | 2006-01-10 6:02 | 2019-10-28 22:42 | MySQL Server: DML | Closed (1952 days) | S4 | 5.0.12 | Windows (windows & linux) | Any | auto_increment primary key can be updated,and then insert record fail |
11287 | 2005-06-13 12:58 | 2005-07-21 14:30 | MySQL Server | No Feedback (7164 days) | S3 | 5.0.6 | Linux (CentOS4) | Any | Errors in stored procedure (ERROR 1418, ERROR 2013) |
11305 | 2005-06-14 7:05 | 2020-04-11 13:22 | MySQL Server: InnoDB storage engine | Closed (7199 days) | S3 | 4.0.16 | Windows (Windows 2000) | Any | On Update Cascade not working with two references to the same field |
45055 | 2009-05-24 17:25 | 2011-02-16 23:44 | MySQL Server: Errors | Closed (5761 days) | S1 | 5.0.41 | Linux (4) | Any | update error: Column count doesn't match value count at row 1 |
71736 | 2014-02-16 13:23 | 2016-10-19 17:28 | MySQL Server: Documentation | Closed (3056 days) | S3 | 5.6 | Any | Any | Manual does not explain locks set by UPDATE properly |
93787 | 2019-01-02 18:07 | 2021-03-17 10:45 | Connector / ODBC | No Feedback (1661 days) | S3 | 5.3.9, 5.3.11, 8.0.13 | Windows (Server 2012 R2) | Other (x64) | Auto-inc primary key field changes to 0 on update with ODBC > 5.3.4 |
7290 | 2004-12-14 17:27 | 2016-01-03 20:45 | MySQL Server: InnoDB storage engine | Open (5407 days) | S4 | 4.1.7 | Solaris (Solaris) | Any | update should check primary keys after all records altered |
58027 | 2010-11-06 9:26 | 2011-02-16 23:44 | MySQL Workbench | No Feedback (5198 days) | S3 | Windows (windows 7) | Any | Mysql Duplicate entry Error to Update A Table | |
114498 | 2024-03-27 16:03 | 2024-03-28 12:43 | MySQL Workbench | Duplicate (339 days) | S3 | 8.0.36 | Windows (Microsoft Windows 11 Enterprise) | x86 (Ryzen 4600H) | MySQL Workbench failed to check for update |
115067 | 2024-05-21 9:47 | 2024-05-21 11:49 | MySQL Workbench | Duplicate (285 days) | S3 | 8.0.36 | MacOS (macOS 14.x Sonoma x86_64) | x86 | Check for Update fails |
68302 | 2013-02-07 13:47 | 2013-12-31 11:14 | MySQL Server: InnoDB storage engine | Can't repeat (4079 days) | S1 | 5.5.32 | Linux | Any | MySQL crashed when trying to free page that is already marked as free |
21301 | 2006-07-26 16:22 | 2006-08-26 23:34 | MySQL Server | No Feedback (6763 days) | S2 | 4.1.15 | Linux (RedHat/Fedora Core) | Any | SQL Error updating table when primary key contains multiple columns |
260 | 2003-04-09 10:57 | 2003-06-19 6:54 | Connector / ODBC | Closed (7927 days) | S3 | 3.51 | Any | Parsing the key columns while generating cursor based updates/deletes query | |
2535 | 2004-01-27 11:56 | 2004-01-27 12:48 | MySQL Server: InnoDB storage engine | Won't fix (7705 days) | S3 | 4.0.17 | Linux (Linux Intel) | Any | Foreign Keys on InnoDB tables not honoured. |
28103 | 2007-04-25 19:34 | 2007-04-27 14:25 | MySQL Query Browser | Closed (6519 days) | S3 | 1.2.11 | Any | Any | MySQL Query Browser ON UPDATE/DELETE NO ACTION not set on foreign keys |
61088 | 2011-05-07 7:59 | 2012-01-17 20:17 | MySQL Server: InnoDB storage engine | Can't repeat (4793 days) | S1 | 5.5.9 | Linux (Ubuntu 64 bit) | Any | Cannot alter table or update all row in table at all |
75631 | 2015-01-26 4:42 | 2015-01-26 4:42 | MySQL Cluster: Cluster (NDB) storage engine | Open | S4 | 7.3.8 GPL | Windows (2008) | Any | Rquest for foreign key constrain on update cascade and native primary key update |
80618 | 2016-03-04 15:08 | 2016-05-16 23:15 | MySQL Workbench: Modeling | Closed (3212 days) | S3 | 6.3.6 | Windows (Microsoft Windows 10 Pro) | Any | Forard Engineered DB Script for table with virtual field has syntax error |
104734 | 2021-08-26 8:51 | 2021-08-27 15:18 | MySQL Server | Unsupported (1283 days) | S2 | 5.7.33 | Other (LINUX AWS RDS x86_64) | x86 (AWS RDS Master-Slave set up) | Parallel one record update by unique key cause deadlock |
4224 | 2004-06-20 13:40 | 2004-06-21 16:07 | MySQL Server: Documentation | Closed (7559 days) | S3 | Any | German documentation misses INSERT ON DUPLICATE KEY-syntax | ||
12158 | 2005-07-25 17:32 | 2005-07-25 17:52 | MySQL Server | Can't repeat (7160 days) | S2 | 5.0.3 | Solaris (Solaris) | Any | ON Duplicate Key when field Truncated causes Server Hang |
15236 | 2005-11-24 20:47 | 2006-03-09 15:42 | MySQL Server: Partitions | Can't repeat (6933 days) | S3 | 5.1.2-alpha-debug | Linux (SUSE 10.0) | Any | Partitions: crash, if Insert .. on duplicate key causes update of existing row |
19656 | 2006-05-09 21:55 | 2006-05-23 14:43 | MySQL Server: Documentation | Closed (6858 days) | S3 | 5.1.11 | Any | MySQL Error log flooded with [ERROR] NDB Binlog: Duplicate key on write or upda | |
24440 | 2006-11-20 15:06 | 2006-11-21 9:57 | Connector / NET | Closed (6676 days) | S3 | Connctr./NET 1.0.7 | Windows (Win XP SP2) | Any | Prepared statement with more than 4 parameters and ON DUPLICATE KEY clause fails |
24491 | 2006-11-21 23:20 | 2007-02-03 2:34 | MySQL Server: Stored Routines | Closed (6602 days) | S3 | 5.0.27, 5.1 BK | Linux (Linux, Windows) | Any | using alias from source table in insert..on duplicate key |
25123 | 2006-12-17 19:28 | 2007-02-08 18:40 | MySQL Server: Views | Closed (6597 days) | S3 | 5.0.30/5.1BK | FreeBSD (freebsd) | Any | insert into view on dup key, allows cross table reference |
26342 | 2007-02-13 20:23 | 2007-06-19 12:37 | MySQL Cluster: Cluster (NDB) storage engine | Closed (6466 days) | S2 | 5.0.38 | mysql-5.1-telco | Linux (CentOS 4.4 | Fedora) | Any | auto_increment_increment AND auto_increment_offset REALLY REALLY anger NDB clust |
31971 | 2007-10-30 23:08 | 2019-10-29 22:33 | MySQL Server: DML | Can't repeat (1951 days) | S3 | 5.0.51 and 5.0.45 | Any (Debian, FreeBSD) | Any | last_insert_id with on duplicate key still broken |
33736 | 2008-01-08 9:53 | 2008-01-14 6:51 | MySQL Server: General | Closed (6257 days) | S2 | 5.1.22(5.1.19, 6.0.3) | Any | Any | mysql crash on error sql with INSERT DELAYED and ON DUPLICATE KEY UPDATE |
39597 | 2008-09-23 4:38 | 2018-04-08 20:45 | Tests: Server | Duplicate (6004 days) | S3 | 5.1+ | Any | Any | Various partition errors have changed output - need to update test results |
45677 | 2009-06-23 13:08 | 2011-02-16 23:44 | MySQL Server: Replication | Closed (5232 days) | S2 | 5.1.35 and 5.4.0 | Any | Any | Slave stops with Duplicate entry for key PRIMARY when using trigger |
52020 | 2010-03-12 21:49 | 2017-12-22 8:24 | MySQL Server: InnoDB storage engine | Closed (4806 days) | S3 | 5.0, 5.1.46 | Any | Any | InnoDB can still deadlock on just INSERT...ON DUPLICATE KEY |
62961 | 2011-10-27 8:02 | 2011-10-27 17:20 | MySQL Server: DML | Open | S4 | 5 | Any | Any | update..........on duplicate Key delete |
66565 | 2012-08-28 6:46 | 2012-08-28 9:01 | MySQL Server: Federated storage engine | Not a Bug (4569 days) | S2 | 5.5.28 | Any | Any | Insert into federated table |
90688 | 2018-04-30 10:37 | 2019-05-22 18:37 | Connector / J | Verified (2495 days) | S3 | 8.0.11 | Any | Any | Statement.getGeneratedKeys() returns too many rows on INSERT .. ON DUPLICATE KEY |
106113 | 2022-01-08 6:52 | 2022-01-08 9:45 | MySQL Server: Replication | Verified (1149 days) | S2 | 8.0.27, 5.7.36 | Any | x86 | Contribution by Tencent: insert on duplicate key cause 1032 replication error in |
109510 | 2023-01-02 15:14 | 2023-01-03 14:21 | MySQL Server: General | Not a Bug (789 days) | S2 | 8.0.31-0ubuntu2 | Ubuntu (22.04) | Any | ON DUPLICATE KEY UPDATE change wrong row |
111377 | 2023-06-13 2:40 | 2023-06-13 7:55 | MySQL Server: DML | Verified (628 days) | S6 | 8.0.33 | Ubuntu (20.04 LTS) | x86 (Intel(R) Core(TM) i7-10700 CPU) | int mysql_execute_command(THD*, bool): Assertion `!thd->in_sub_stmt' failed |
69243 | 2013-05-15 11:56 | 2019-08-14 19:58 | MySQL Server: FULLTEXT search | No Feedback (4273 days) | S2 | 5.6.11 | Windows | Any | Can't update InnoDB table with fulltext index defined |
69872 | 2013-07-30 15:53 | 2013-07-30 16:54 | MySQL Server: Stored Routines | Duplicate (4233 days) | S3 | 5.6 | Any | Any | UPDATE in stored function is not rolled back |
2159 | 2003-12-18 11:10 | 2004-01-15 12:33 | MySQL Server | Closed (7717 days) | S1 | v4.0.15-standard | Linux (Linux/Windows) | Any | UPDATE of LONGBLOB >= 16Megs corrupts table |
2377 | 2004-01-13 11:49 | 2004-02-03 7:51 | MySQL Server: MyISAM storage engine | Closed (7698 days) | S1 | 4.0.16 | Linux (Linux) | Any | UPDATE privilege BUG |
5165 | 2004-08-23 11:19 | 2004-08-23 16:38 | MySQL Server: InnoDB storage engine | Won't fix (7496 days) | S2 | 4 | Any (All) | Any | SELECT ... FOR UPDATE uses 'select' privelege instead 'update' |
15028 | 2005-11-17 17:21 | 2005-12-08 23:53 | MySQL Server | Closed (7024 days) | S3 | 5.0.17-BK, 5.0.15, 4.1.14/5.0.13 | Linux (Linux, Windows, Solaris) | Any | Update multiple tables updates more rows than expected |
19608 | 2006-05-08 13:50 | 2006-05-08 14:09 | MySQL Server | Not a Bug (6873 days) | S3 | 4.0.18, 5.0.16 | Solaris (Solaris, Linux(Mandrake 10.2)) | Any | Separating multiple 'ColName = ExpName' statements within Update x Set ... |
31391 | 2007-10-04 9:46 | 2008-01-31 8:21 | MySQL Cluster: Replication | Can't repeat (6240 days) | S2 | 5.1.20 | Linux (x86_64) | Any | Replication broken after few UPDATE on RAM disk only with mod_ndb |
36676 | 2008-05-12 22:05 | 2016-02-25 12:24 | MySQL Server: DML | Closed (6128 days) | S2 | 5.0.58 | Any | Any | UPDATE on TEXT column using LEFT JOIN doesn't update all rows |
39695 | 2008-09-27 15:14 | 2008-12-13 9:03 | MySQL Server: Falcon storage engine | Closed (5923 days) | S1 | 6.0-falcon-team (6.0.8a) | Linux | Any | Crash in SRLUpdateRecords::thaw during falcon_chill_thaw test |
56565 | 2010-09-05 10:08 | 2010-09-06 20:50 | MySQL Server: DML | Not a Bug (5291 days) | S3 | 5.1.36 | Any | Any | Multiple update syntax doesn't update rows multiple times |
68726 | 2013-03-20 11:22 | 2014-07-14 15:28 | MySQL Server: DML | Closed (3884 days) | S3 | 5.5.30 and 5.6.10, 5.1.70, 5.5.32, 5.6.12 | Windows | Any | Update trigger invoked when update ignore means that no update is performed |
83659 | 2016-11-02 20:47 | 2016-11-08 16:34 | MySQL Server: Replication | Unsupported (3036 days) | S3 | Percona-XtraDB-Cluster-5.5.39-25.11 | Linux | Any | Replication Statements Missing From Binary Logs |
102676 | 2021-02-21 18:29 | 2021-02-22 21:03 | MySQL Server: Locking | Not a Bug (1469 days) | S2 | 5.7.12, 8.0.11 | Linux (RDS of AWS) | Any | In REPEATABLE READ, the behavior after executing select for update is strange. |
103059 | 2021-03-22 12:35 | 2021-03-23 5:35 | MySQL Server: InnoDB storage engine | Verified (1441 days) | S3 | 8.0.23 | Any | Any | system_variable_source does not report DYNAMIC when queried from sys_var update |
104117 | 2021-06-26 2:36 | 2021-06-26 2:39 | MySQL Server: Group Replication | Closed (1345 days) | S2 | mysql8.0.23 mysql8.0.24 | Any | Any | MGR all second node abnormal stop |
104118 | 2021-06-26 2:42 | 2022-08-23 8:45 | MySQL Server: Security: Privileges | Verified (1342 days) | S2 | 8.0.24 | Any | Any | MGR all second node abnormal stop |
108155 | 2022-08-16 16:22 | 2024-03-12 11:04 | MySQL Server: DML | Duplicate (355 days) | S3 | 8.0.30 | Any | Any | BEFORE INSERT trigger causes Error 1048 during UPDATE |
109196 | 2022-11-24 15:39 | 2022-11-25 14:45 | MySQL Server: InnoDB storage engine | Verified (828 days) | S3 | 8.0 | Any | Any | FOR UPDATE doesn't block FOR SHARE if secondary index is used |
112007 | 2023-08-09 9:32 | 2023-08-09 9:39 | MySQL Server: DDL | Verified (571 days) | S3 | Any, 5.7, 8.0 | Any | Any | FOREIGN KEY (reference the hidden part of key) should not have the UK's name. |
3551 | 2004-04-23 10:54 | 2004-04-28 12:10 | MySQL Server | Can't repeat (7613 days) | S2 | 5.0.0-alpha | Linux (Linux) | Any | Incorect row count on query |
8558 | 2005-02-16 21:51 | 2005-02-16 23:32 | MySQL Server: MyISAM storage engine | Not a Bug (7319 days) | S3 | 4.0.18-standard | Linux (Linux 2.4.22 (Mandrake 9)) | Any | Poor query plan with merge tables |
12662 | 2005-08-19 2:20 | 2005-08-19 2:41 | MySQL Server | Duplicate (7135 days) | S2 | 5.0.9 | FreeBSD (FreeBSD 5.4) | Any | Poor View Performance |
13218 | 2005-09-15 10:25 | 2005-09-24 3:51 | MySQL Server: Optimizer | Closed (7099 days) | S3 | 4.1.14-nt, 4.1.15-BK | Windows (Windows XP, Linux) | Any | select MIN(..) / InnoDB: using a partial-field key prefix in search |
16736 | 2006-01-23 22:44 | 2006-03-16 9:38 | MySQL Server: Documentation | Closed (6926 days) | S2 | 5.1.6-alpha | Linux (Linux) | Any | Implicit partitioning key not displayed. |
17590 | 2006-02-20 17:44 | 2006-02-23 9:32 | MySQL Server: Optimizer | Can't repeat (6947 days) | S2 | 5.1.7-beta | Any (All) | Any | Different key-len and # rows reported on all platforms |
18800 | 2006-04-05 13:13 | 2006-08-07 7:52 | MySQL Server: InnoDB storage engine | Closed (6782 days) | S2 | 5.1 | Linux (Linux) | Any | Unicode quoted foreign key references are broken |
19213 | 2006-04-20 9:16 | 2006-05-20 16:30 | MySQL Server | No Feedback (6861 days) | S2 | 4.1.16 | Linux (linux x86_64) | Any | Table Locked after wrong Query |
19463 | 2006-05-01 18:48 | 2006-05-01 19:58 | MySQL Server | Not a Bug (6880 days) | S2 | 5.x | Windows (windows) | Any | Bug in executing SQL scripts that has a key named Group |
19653 | 2006-05-09 21:49 | 2007-10-26 2:50 | MySQL Server: Documentation | Closed (6337 days) | S2 | 5.0.21 | Any | Any | YaSSL: is passphrase removing optional for keys? |
20298 | 2006-06-06 16:27 | 2006-06-11 4:40 | MySQL Server | Not a Bug (6839 days) | S1 | 5.0.22 | MacOS (Mac OS X) | Any | Specified key was too long; max key length is 1000 bytes |
21713 | 2006-08-18 9:23 | 2007-02-14 16:41 | MySQL Server: Information schema | Closed (6591 days) | S3 | 5.1.12-BK, 5.1.11 beta | Linux (Ubuntu 6 (Linux 2.6.15)) | Any | incorrect value for the REFERENTIAL_CONSTRAINTS.UNIQUE_CONSTRAINT_NAME column |
32735 | 2007-11-26 19:40 | 2011-02-16 23:43 | MySQL Cluster: Cluster (NDB) storage engine | Won't fix (5304 days) | S3 | mysql-5.0 | MacOS (10.5 (x86: 32 bit)) | Any | Ndb is unreliable, fails with varying symptoms (platform-specific): debug server |
35137 | 2008-03-07 9:45 | 2008-07-09 7:26 | MySQL Cluster: Cluster (NDB) storage engine | Closed (6080 days) | S2 | 5.1.23 | Any | Any | Query crashed mysqld |
41332 | 2008-12-09 16:01 | 2021-05-02 20:45 | MySQL Cluster: Cluster (NDB) storage engine | Duplicate (5893 days) | S1 | Cluster 6.3.20 | Any | Any | Insert into partitioned "ndbcluster" table causes server crash |
44057 | 2009-04-02 22:28 | 2011-02-16 23:43 | MySQL Server: InnoDB storage engine | No Feedback (5779 days) | S2 | 5.0.51a | Linux (14.12 Distrib 5.0.51a, for debian-linux-gnu (x86_64)) | Any | Unable to create new tables with foreign key references in big databases |
45787 | 2009-06-26 11:35 | 2011-02-16 23:44 | MySQL Server: DDL | Closed (5728 days) | S3 | 5.0.67 | Linux | Any | ALTER TABLE doesn't differentiate between unique and foreign key |
47963 | 2009-10-09 23:07 | 2016-02-25 12:24 | MySQL Server: Optimizer | Closed (5469 days) | S1 | 5.1.39, 5.1.41 | Any | Any | Wrong results when index is used |
51378 | 2010-02-22 9:57 | 2011-02-16 23:44 | MySQL Server: InnoDB Plugin storage engine | Closed (5339 days) | S3 | 5.1+ | Any | Any | Init "ref_length" to correct value, in case an out of bound MySQL primary_key |
58524 | 2010-11-26 17:19 | 2013-03-03 20:45 | MySQL Server: MyISAM storage engine | Verified (5206 days) | S4 | 5.x | Any | Any | More detailed information on custom key caches |
68534 | 2013-03-01 7:00 | 2013-04-17 17:09 | MySQL Workbench: SQL Editor | Not a Bug (4337 days) | S3 | MySQL 5.5 | Windows | Any | Primary Key - NULL Paradox |
70013 | 2013-08-13 11:29 | 2013-08-13 12:54 | MySQL Server | Duplicate (4219 days) | S2 | 5.5.23 | Linux (Red Hat Enterprise Linux Server release 5.8 (Tikanga) 64 bit) | Any | select count from innodb partitioned table with compound key can crash db |
73299 | 2014-07-16 14:59 | 2014-07-18 9:26 | MySQL Server: DDL | Verified (3880 days) | S2 | 5.6.19, 5.6.20 | Any | Any | DEFAULT value for PRIMARY KEY column depends on the way to declare it PRIMARY |
82610 | 2016-08-17 10:38 | 2016-09-18 1:00 | MySQL Workbench | No Feedback (3088 days) | S1 | 6.3.7 | MacOS | Any | MySQL WorkBench alter table window miss primary key |
83298 | 2016-10-07 9:52 | 2016-10-20 12:50 | MySQL Server: Optimizer | Duplicate (3055 days) | S2 | 5.6.10 | Debian (debian-linux-gnu (x86_64) using readline 6.2) | Any | MYSQL 5.6.10 Optimiser selecting wrong index |
88334 | 2017-11-02 16:29 | 2019-08-23 14:29 | MySQL for Windows: Installer | Verified (2018 days) | S3 | 5.7.20 | Windows (Windows 10) | Any | Web community Installer fails to install MySQL Server 5.7.20 |
92392 | 2018-09-12 20:53 | 2023-08-17 7:46 | MySQL Server: Installing | No Feedback (2243 days) | S1 | 8.0.12 | Windows (Windows 10 Pro 64 bit) | Any | The action 'Install' for product 'MySQL Server 8.0.12' failed |
93845 | 2019-01-07 21:55 | 2021-08-23 12:23 | MySQL Server: Optimizer | Verified (2244 days) | S2 | 5.7,8.0.11,8.0.13 | Any | Any | Optimizer choose wrong index, sorting index instead of filtering index |
96958 | 2019-09-20 21:42 | 2024-04-30 9:09 | MySQL Server: Optimizer | Verified (1988 days) | S3 | 8.0 | Any | Any | MySQL optimizer wrongly chooses to use a bigger and inefficient index for query |
100017 | 2020-06-27 14:02 | 2023-05-05 8:00 | MySQL Server: MyISAM storage engine | Duplicate (1707 days) | S5 | 8.0.20 | Any | Any | Extremely slow queries after database repair |
102193 | 2021-01-08 12:21 | 2021-01-15 14:06 | MySQL Server: Optimizer | Not a Bug (1510 days) | S3 | 8.0.22 | CentOS (CentOS Linux release 8.0.1905 (Core)) | x86 (4.18.0-80.el8.x86_64 ) | Inaccurate execution plan selection |
13226 | 2005-09-15 15:18 | 2005-10-18 10:14 | MySQL Server | No Feedback (7075 days) | S2 | 4.1.11 | Windows (WinXP SP2) | Any | AUTO_INCREMENT attempting to insert zero value |
13431 | 2005-09-23 15:21 | 2014-01-16 2:56 | MySQL Server: InnoDB storage engine | Closed (4063 days) | S3 | 5.0 | Linux (Linux) | Any | Duplicate FOREIGN KEY error does not make sense |
16222 | 2006-01-05 13:21 | 2006-01-09 0:31 | MySQL Server | Not a Bug (6992 days) | S3 | 4.0.22 | Linux (Linux) | Any | Select on truncated keys |
109313 | 2022-12-08 7:33 | 2023-03-14 19:09 | Shell Dump & Load | Closed (752 days) | S2 | 8.0.31 | CentOS (7.9) | x86 | Can't restore loadDump with deferTableIndexes=all by MySQL Error 1061 |
114904 | 2024-05-07 7:34 | 2024-05-23 13:00 | MySQL Server: DDL | Verified (299 days) | S1 | 8.0.36, 8.0.11, 8.0.37 | Any | Any | Rename table with COPY does not change the constraint name |
15762 | 2005-12-14 23:34 | 2006-06-18 21:25 | MySQL Server | No Feedback (6832 days) | S2 | 5.0.16-1 | Linux (debian, unstable) | Any | losing connection on queries after creating view |
20670 | 2006-06-23 21:26 | 2006-10-05 16:15 | MySQL Server: Stored Routines | Closed (6723 days) | S3 | 5.0.23-bk | Any (Any) | Any | UPDATE using key and invoking trigger that modifies this key does not stop |
24668 | 2006-11-28 19:02 | 2016-01-03 20:45 | MySQL Server: InnoDB storage engine | Verified (5407 days) | S4 | 5.0.32-BK, 5.0.27 | Linux (Linux, Windows XPsp2) | Any | CASCADING FOREIGN KEYS do not work on same TABLE |
50917 | 2010-02-04 15:23 | 2012-05-18 20:19 | MySQL Server: Replication | Verified (5203 days) | S3 | 5.1.43,5.5.2-m2 | Any | Any | slave stops with HA_ERR_KEY_NOT_FOUND |
50927 | 2010-02-04 19:29 | 2011-02-16 23:44 | MySQL Enterprise Monitor: Server | Closed (5480 days) | S3 | 2.1.0.1096 | Any | Any | Delete server fails on foreign key error to rule_schedules table |
57733 | 2010-10-26 9:43 | 2011-02-16 23:44 | MySQL Workbench: Modeling | Verified (5239 days) | S4 | ALL | Any | Any | During data insert/update show foreign key values |
1721 | 2003-10-31 0:17 | 2012-05-18 20:19 | MySQL Server: MyISAM storage engine | No Feedback (7678 days) | S2 | 4.0.16 | Linux (Linux SuSE 8.2) | Any | False duplicate key warnings on FULLTEXT columns |
1824 | 2003-11-12 20:59 | 2003-12-10 9:11 | MySQL Server: Replication | Closed (7753 days) | S2 | 4.0.13 (-log) | Linux (Debian) | Any | replication fails for duplicate in primary key, which isn't true on master |
2027 | 2003-12-05 13:27 | 2005-05-22 16:22 | MySQL Server: MyISAM storage engine | Can't repeat (7224 days) | S1 | 4.1.1 (01 Dec 2003) | Linux (GNU/Linux) | Any | Error "Duplicate entry ... for key ..." where not expected |
6075 | 2004-10-13 22:19 | 2004-11-19 17:34 | MySQL Server | No Feedback (7408 days) | S2 | 4.0.20a-nt | Windows (Windows) | Any | Bogus Duplicate Key Error |
7836 | 2005-01-12 14:24 | 2005-02-13 20:15 | MySQL Server: Replication | Not a Bug (7322 days) | S3 | 4.0.22 | Linux (Redhat 9.0) | Any | REPLACE INTO dies with Duplicate Key Error |
12695 | 2005-08-20 15:35 | 2005-09-28 2:08 | MySQL Server: Optimizer | Closed (7095 days) | S2 | 4.1.13 | Linux (Linux(Redhat9.0)) | Any | Duplicate entry 'xxxxx for key 1 |
14520 | 2005-10-31 20:31 | 2005-12-16 17:51 | MySQL Server | No Feedback (7016 days) | S2 | 4.1.11 | Windows (Windows XP Pro 2002 SP2) | Any | Replication fails with error "Error 'Duplicate entry '-1' for key 2'" |
15600 | 2005-12-08 19:06 | 2005-12-09 11:27 | MySQL Server: Stored Routines | Duplicate (7023 days) | S2 | 5.0 | Any | SELECT on ill FUNCTION gets warning instead of error | |
16840 | 2006-01-27 13:22 | 2006-02-10 20:38 | MySQL Server | Not a Bug (6960 days) | S1 | MySQL 5.0.18-standard | MacOS (OSX 10.4, RedHat 4) | Any | Duplicate Key error without keys being identical |
18552 | 2006-03-27 18:55 | 2022-09-04 20:45 | MySQL Server: Partitions | Duplicate (6901 days) | S2 | 5.1 | Any | Partitions: SP with cursor, autoincrement PK, duplicate key on insert | |
23190 | 2006-10-11 21:36 | 2006-11-12 5:18 | MySQL Workbench Preview | No Feedback (6685 days) | S2 | 1.1.3 alpha | Windows (WinXP) | Any | duplicate foreign keys |
25326 | 2006-12-29 9:19 | 2007-03-12 15:18 | MySQL Server: Replication | No Feedback (6565 days) | S1 | 5.1.14-beta | Linux (Linux 2.6) | Any | Since table has been partitioned, replication fails due to duplicate key |
28039 | 2007-04-23 19:50 | 2007-04-23 19:50 | MySQL Server: Falcon storage engine | Closed | S3 | Any | Any | Falcon Crash if INSERT ON DUPLICATE KEY with two interleaving transactions | |
29460 | 2007-06-30 20:00 | 2007-10-19 20:56 | MySQL Server: Falcon storage engine | Can't repeat (6344 days) | S3 | 6.0.1-BK | Any | Any | falcon - Can't find record in 't1' |
29884 | 2007-07-19 0:00 | 2007-07-20 8:39 | MySQL Server: MyISAM storage engine | Can't repeat (6435 days) | S3 | 5.0.27-community-nt | Windows (XP SP2 fully updated) | Any | Duplicate key problem |
30907 | 2007-09-07 17:18 | 2011-02-16 23:43 | MySQL Server: InnoDB storage engine | Closed (5371 days) | S2 | 5.1.22 | Any | Any | Regression: "--innodb_autoinc_lock_mode=0" (off) not same as older releases |
33824 | 2008-01-11 17:56 | 2008-02-11 21:00 | MySQL Server: Falcon storage engine | Can't repeat (6229 days) | S1 | 6.0.4-p3 | Any | Any | Manipulations on a view and on the underlying table cause duplicate primary key |
37448 | 2008-06-17 14:43 | 2008-06-19 18:21 | MySQL Server | Not a Bug (6100 days) | S2 | 5.0.51 | Any | Any | C with cedilla and tilde duplicate key unique entry event up |
37718 | 2008-06-28 11:48 | 2018-09-25 21:47 | Tests: Replication | Closed (5816 days) | S7 | 5.1 | Any | Any | rpl.rpl_stm_mystery22 fails sporadically on pushbuild |
41186 | 2008-12-02 19:54 | 2018-09-25 21:50 | Tests: Replication | Duplicate (5903 days) | S7 | 6.0-rpl, 5.1 | Any | Any | rpl_stm_mystery22 fails sporadically on pushbuild while waiting for slave start |
43306 | 2009-03-02 13:16 | 2012-05-18 20:19 | MySQL Server: Charsets | Duplicate (5834 days) | S1 | 5.1, 6.0 | Any | Any | Wrong utf8 collation default behaviour |
49349 | 2009-12-02 13:29 | 2018-11-04 20:45 | MySQL Server: Optimizer | Duplicate (4451 days) | S3 | 6.0 | Any | Any | Wrong cost calculation for duplicate weed-out |
55919 | 2010-08-11 17:12 | 2010-08-11 18:16 | MySQL Server | Not a Bug (5317 days) | S2 | 5.1.37sp1-enterprise-gpl-advanced-log | Linux (RedHat 5.2) | Any | Duplicate rows on Unique key |
56019 | 2010-08-16 15:47 | 2013-01-31 11:49 | MySQL Server: Documentation | Can't repeat (4413 days) | S2 | 5.6.99-m5 | Any | Any | Blackhole slave replication: 2nd slave stops for two REPLACE statements |
61371 | 2011-06-01 10:26 | 2011-06-02 12:16 | MySQL Server: DML | Not a Bug (5022 days) | S1 | 5.0.32-7etch12, 5.1.54-1ubuntu4 | Linux (Ubuntu 11.04) | Any | Duplicate Key when inserting new auto increment value |
65396 | 2012-05-23 7:24 | 2012-05-25 14:34 | MySQL Server: Replication | Not a Bug (4664 days) | S1 | 5.5.17-55 | Linux (2.6.32-34-generic #77-Ubuntu SMP Tue Sep 13 19:39:17 UTC 2011 x86_64 GNU/Linux) | Any | Duplicate Entry for Key 'primary' on query insert into select |
67447 | 2012-11-01 12:33 | 2012-11-01 12:35 | MySQL Server: DDL | Open | S4 | 5.2 | Any | Any | Tools/Options needs Define Primary Key |
78934 | 2015-10-23 4:14 | 2015-10-26 13:37 | MySQL Server: DML | Not a Bug (3415 days) | S3 | 5.7.8 | Any | Any | Failed INSERT(Dup entry) still change LAST_INSERT_ID() for auto_increment col |
107157 | 2022-04-29 3:49 | 2022-04-29 5:41 | MySQL Server: InnoDB storage engine | Verified (1038 days) | S3 | 8.0.22, 8.0.29 | Any | Any | Contribution by Tencent: Collation compare handling is confused in Innobase |
108488 | 2022-09-15 7:50 | 2022-09-19 13:59 | MySQL Server | Not a Bug (895 days) | S3 | 5.7.18, 5.7.35, 8.0 | Any | Any | Gap locking issue in READ COMMITTED |
110565 | 2023-03-30 10:52 | 2023-04-17 18:28 | MySQL Server: FULLTEXT search | Verified (685 days) | S3 | 8.0.32 | Any | Any | Adding a fulltext index causes a "Duplicate entry '0'" for the primary key |
112372 | 2023-09-18 7:19 | 2023-09-21 9:36 | MySQL Server: Parser | Can't repeat (528 days) | S3 | 8.0.33 | MacOS | x86 | Select query returns duplicate rows |
116366 | 2024-10-16 8:00 | 2024-10-16 9:01 | MySQL Server: Optimizer | Not a Bug (137 days) | S3 | 8.0.39 | Any | Any | Pagination order by a datetime column with same value display duplicate rows |
1890 | 2003-11-19 11:09 | 2003-12-10 5:37 | MySQL Server: Embedded Library ( libmysqld ) | Closed (7753 days) | S1 | 4.0.17 | Windows (Windows 2000/XP) | Any | table handler and corruption bugs on multithread application |
29251 | 2007-06-20 21:32 | 2007-07-11 22:27 | MySQL Server | Closed (6444 days) | S2 | 5.0.42, 5.1, 4.1 | Linux (Gentoo) | Any | MySQL coerces special 0 enum values to '' when ALTERing the column |
47774 | 2009-10-01 21:55 | 2011-02-16 23:44 | MySQL Server: Partitions | Closed (5589 days) | S3 | 5.5 WL#3352 | Any | Any | InnoDB: Assertion failure in thread 1769970576 in file row/row0mysql.c line 1355 |
68568 | 2013-03-05 3:17 | 2021-09-15 20:49 | MySQL Server: Replication | Verified (4126 days) | S3 | 5.6.10 | Linux (CentOS 5.8 X64) | Any | Stop Slave statement will timeout not waiting the event group complete |
96578 | 2019-08-16 22:08 | 2020-02-04 19:16 | MySQL Server: DML | Closed (1853 days) | S2 | 8.0.16, 5.7.27, 8.0.17 | Any | Any | `Insert on duplicate key update` updates the wrong row |
6709 | 2004-11-18 22:28 | 2005-10-04 10:06 | MySQL Server | Can't repeat (7089 days) | S3 | 5.0.2-alpha-debug | Linux (SuSE 8.2) | Any | Subquery: table subquery allows duplicate column names |
15575 | 2005-12-08 8:54 | 2005-12-09 5:10 | Eventum | Closed (7023 days) | S2 | Any | Searching for issues when creating a duplicate entry | ||
20636 | 2006-06-22 20:58 | 2006-06-22 22:55 | MySQL Workbench Preview | Duplicate (6828 days) | S2 | 1.0.6 Beta | Windows (Windows XP) | Any | duplicate phantom relationships created by applying changes |
22313 | 2006-09-13 14:32 | 2007-01-12 7:06 | MySQL Cluster: Cluster (NDB) storage engine | Closed (6624 days) | S3 | 5.0,5.1 | Any | can get duplicate log messages in cluster log | |
27575 | 2007-04-01 20:23 | 2009-05-26 11:53 | MySQL Administrator | Unsupported (5759 days) | S3 | 5.0r11 | MacOS (Mac OS X 10.4) | Any | Odd error mesage for duplicate column names in Table Editor |
34421 | 2008-02-08 16:04 | 2008-02-08 16:16 | MySQL Server: InnoDB storage engine | Closed (6232 days) | S1 | 5.1.22 rc | Any | Any | DUPLICATE of WHAT!!! RE bug 34420 |
35087 | 2008-03-05 17:54 | 2011-02-16 23:43 | MySQL Server: General | Closed (5773 days) | S2 | 5.0.50+ | Any | Any | Inserting duplicate values at one time with DES_ENCRYPT leads to wrong results |
36827 | 2008-05-20 18:57 | 2008-11-22 9:34 | Connectors: DBD::mysql ( Perl ) | No Feedback (5944 days) | S2 | 4.007 | MacOS (10.3.9 server) | Any | running make on OS X server 10.3.9 yields duplicate function definitions, errors |
39299 | 2008-09-08 6:50 | 2011-02-16 23:43 | MySQL Server: Packaging | Won't fix (5204 days) | S3 | 5.0.67 | HP/UX (B.11.11 on PA-RISC) | Any | HP-UX packages contain duplicate files instead of symlinks |
47416 | 2009-09-17 14:19 | 2011-02-16 23:44 | MySQL Server: Embedded Library ( libmysqld ) | Closed (5360 days) | S2 | 6.0.14-alpha, mysql-pe | MacOS (10.6) | Any | Build failure on OS X 10.6: duplicate symbol _timed_mutexes |
51451 | 2010-02-24 9:57 | 2012-05-18 20:19 | MySQL Server: DDL | Duplicate (5423 days) | S3 | 5.1 | Any | Any | ALTER TABLE DROP INDEX, ADD INDEX executed in opposite order |
60828 | 2011-04-11 11:39 | 2011-04-11 17:01 | MySQL Enterprise Monitor: Advisors/Rules | Verified (5074 days) | S4 | Any | Any | Add rule to detect duplicate foreign keys | |
69732 | 2013-07-12 14:29 | 2017-10-09 8:42 | MySQL Server: Optimizer | Not a Bug (4251 days) | S3 | 5.6.11 MySQL Community Server (GPL) | Any | Any | LIMIT clause results in duplicate data across pages |
76095 | 2015-03-02 13:29 | 2015-03-02 18:12 | MySQL Server: Views | Not a Bug (3653 days) | S3 | 5.5.40 | MacOS (10.10.2) | Any | CREATE VIEW with UNION does not allow duplicate column names in version 5.5.40 |
79591 | 2015-12-10 11:14 | 2017-08-04 13:00 | MySQL Server: Optimizer | Closed (3219 days) | S3 | 5.7.9 | Any | Any | select distinct not returning distinct rows in 5.7... |
84030 | 2016-12-01 18:40 | 2017-01-02 1:00 | MySQL Server: DML | No Feedback (2982 days) | S3 | 5.6.34 | Linux | Any | Duplicate entry error when doing GROUP BY with UTF collation |
86890 | 2017-06-30 14:58 | 2017-07-10 11:57 | MySQL Server: Replication | Not a Bug (2792 days) | S3 | 5.7 | CentOS | Any | Dupllicate Entry in Slave |
87353 | 2017-08-09 8:30 | 2017-08-09 9:39 | MySQL Cluster: Cluster (NDB) storage engine | Verified (2762 days) | S3 | 7.5.7 | Any | Any | "ndb_restore --print-data" and "ndb_restore --print-sql-log" have duplicate row |
104336 | 2021-07-16 12:38 | 2021-07-17 18:27 | MySQL Server: DML | Verified (1324 days) | S1 | 8.0 | Any | Any | LEFT Join giving duplicate records for matching records from right table |
116714 | 2024-11-19 16:04 | 2024-11-21 14:17 | MySQL Server: InnoDB storage engine | Verified (102 days) | S3 | 8.0 | Any | Any | With 8000 to 15,999 Tablespaces, MySQL Startup Spawns one Useless Sub-Thread. |
116716 | 2024-11-19 17:06 | 2024-12-03 18:04 | MySQL Server: InnoDB storage engine | Verified (89 days) | S4 | 9.1.0, 8.4.3, 8.0.40 | Any | Any | Allow Setting Nb Thread for Tablespace Duplicate Check (startup). |
9512 | 2005-03-31 2:29 | 2005-04-04 5:30 | MySQL Server: InnoDB storage engine | Not a Bug (7272 days) | S3 | 4.1.10a | Any (All) | Any | SELECT FOR UPDATE returns phantom rows |
25620 | 2007-01-15 6:54 | 2020-05-03 20:45 | MySQL Server: DML | Verified (6297 days) | S3 | 5.0.33 | Windows (Windows Server 2003 Web Edition) | Any | Error in ADDTIME function when update more 35 days |
36470 | 2008-05-02 12:12 | 2012-05-18 20:19 | Connector / ODBC | Duplicate (5976 days) | S3 | 5.1 | Any | Any | ODBC update boolean wrong in MySQL ODBC 5.1, correct in MySQL ODBC 3.51 |
54863 | 2010-06-28 16:38 | 2011-02-16 23:44 | Connector / NET | Closed (5346 days) | S2 | 6.2.3 | Windows | Any | Bug in MySqlDataAdapter update method |
67261 | 2012-10-16 10:36 | 2015-08-10 14:34 | MySQL Server: mysqldump Command-line Client | Duplicate (4503 days) | S3 | 5.6.7-rc | Windows (Windows 8) | Any | mysqldump 5.6.7-rc does not export all tables in `mysql` database |
70888 | 2013-11-12 11:21 | 2013-12-14 0:43 | Connector / NET | Closed (4096 days) | S1 | 6.7.4 | Windows (7 x64) | Any | NullReferenceException when try to save entity with TINYINT or BIGINT as PK |
76352 | 2015-03-17 14:51 | 2015-04-08 16:29 | MySQL Server | Not a Bug (3616 days) | S2 | Ver 14.12 Distrib 5.0.67, for suse-linux | Linux (Suse Linux ) | Any | “BEFORE UPDATE” trigger strange behaviour for table with two timestamp colums |
76396 | 2015-03-19 19:42 | 2015-03-24 7:48 | MySQL Server: DDL | Not a Bug (3631 days) | S2 | 5.6.22 | Linux | Any | Trigger behaving wrongly mysql |
82592 | 2016-08-16 3:55 | 2016-09-02 13:11 | MySQL Server: InnoDB storage engine | Not a Bug (3113 days) | S3 | 5.7.14 | Any | Any | MySQL InnoDB update locking |
26471 | 2007-02-18 13:55 | 2007-02-19 9:25 | MySQL Workbench Preview | Won't fix (6586 days) | S1 | 1.1.8alpha | Linux (linux) | Any | generated request for two tables (many to many relation) bad request generated |
39150 | 2008-09-01 7:45 | 2008-10-13 15:47 | MySQL Workbench | Closed (5984 days) | S3 | 5.0.24 | Any | Any | Remove a table referenced in foreing key constraint |
41844 | 2009-01-03 20:16 | 2022-08-21 20:45 | MySQL Server: General | Duplicate (5857 days) | S3 | 6.1.0-alpha | Linux (SUSE 10.0 / 32-bit) | Any | Foreign keys: failure with varbinary update cascade |
45279 | 2009-06-02 21:59 | 2011-02-16 23:44 | MySQL Server: InnoDB storage engine | No Feedback (5721 days) | S2 | MySQL-server-enterprise-5.0.54a-0.sles10 | Linux (SUSE Linux Enterprise Server 10 (x86_64) VERSION = 10) | Any | deadlock when inserting into auto increment table, not lock on auto-inc |
5553 | 2004-09-13 22:31 | 2004-09-23 9:59 | MySQL Server | Closed (7465 days) | S2 | 4.1.4 | Linux (Linux 2.4.20 debian) | Any | UPDATE IGNORE with multiple tables can lock up mysqld connection,reproducable |
9679 | 2005-04-06 14:38 | 2016-01-03 20:45 | MySQL Server: InnoDB storage engine | Open (5407 days) | S4 | 4.* | Any (any) | Any | errors in cascaded updates |
30922 | 2007-09-10 6:02 | 2008-09-04 18:49 | MySQL Enterprise Monitor: Server | Closed (6023 days) | S3 | 1.2.0.7481 | Any | Any | Constraint Violation Exception when starting several replication agents at once |
38839 | 2008-08-18 3:08 | 2012-05-09 23:37 | MySQL Server: InnoDB storage engine | Not a Bug (5406 days) | S4 | 5.1.25-rc, 5.1.26-rc | Any | Any | auto increment does not work properly with InnoDB after update |
18309 | 2006-03-17 14:14 | 2012-05-18 20:19 | MySQL Server: Stored Routines | Duplicate (6590 days) | S3 | 5.0.19, 5.1.7. 5.1.8 | Linux (Linux) | Any | BEFORE UPDATE TRIGGERS on BLACKHOLE tables raise an error but work as expected |
27443 | 2007-03-26 14:03 | 2007-03-26 14:33 | MySQL Server: Stored Routines | Not a Bug (6551 days) | S2 | 5 | Windows (windows) | Any | not able to create update trigger |
72412 | 2014-04-21 15:42 | 2014-04-21 16:52 | MySQL Server | Not a Bug (3968 days) | S1 | 6.1.4 | Windows (Microsoft Windows 7 Enterprise Edition Service Pack 1 (build 7601), 64-bit) | Any | Update Bug |
76002 | 2015-02-23 8:14 | 2015-02-25 1:35 | MySQL Server: Optimizer | Not a Bug (3658 days) | S3 | 5.6 | Any | Any | different plan when executing query using procedure |
78412 | 2015-09-11 16:17 | 2017-01-13 9:03 | MySQL Server: Documentation | Closed (3369 days) | S2 | 5.6.24 | Any | Any | UPDATE with subquery is NOT optimized the same way as equivalent SELECT |
97837 | 2019-12-01 5:01 | 2019-12-03 14:11 | MySQL Server: InnoDB storage engine | Can't repeat (1916 days) | S6 | 5.7.27 | CentOS (CentOS 7.4) | x86 (8Uxeon 16G memoy) | An assertion failure occurs when multiple threads update a record concurrently |
111811 | 2023-07-19 9:38 | 2023-07-20 14:06 | MySQL Server | Can't repeat (591 days) | S2 | 8.0.33 | Linux | x86 | UPDATE statement with JOIN doesn't update any records |
50102 | 2010-01-06 12:52 | 2010-01-06 15:15 | MySQL Server: InnoDB storage engine | Not a Bug (5534 days) | S3 | 5.1.37 | Any | Any | AUTO_INCREMENT increases when using UPDATE ON DUPLICATE |
68889 | 2013-04-08 20:27 | 2013-09-11 17:18 | Connector / NET | Closed (4190 days) | S1 | Net Connector 6.6.5 | Any | Any | EF 4.3.1 Code First Migration Tries to Migrate Already Migrated Database |
2799 | 2004-02-14 16:18 | 2020-04-27 13:04 | MySQL Server: InnoDB storage engine | Closed (7682 days) | S2 | 4.0.18 | Windows (Win NT) | Any | Multi-table DELETE and Foreign Key (bad affected rows) |
19495 | 2006-05-02 21:39 | 2020-11-22 20:45 | MySQL Server: Partitions | Duplicate (6871 days) | S2 | 5.1.10 | Linux (Linux 32 Bit OS) | Any | default-storeage-engine=ndb causes tables by other engines to be partitioned |
41695 | 2008-12-23 0:29 | 2011-02-16 23:43 | MySQL Server: General | Closed (5878 days) | S3 | 6.1.0-alpha-debug | Linux (SUSE 10.0 / 32-bit) | Any | Foreign keys: non-distinct value change |
46489 | 2009-07-31 11:39 | 2013-12-20 7:04 | MySQL Server: DDL | Won't fix (4090 days) | S3 | 6.1-fk-stage | Any | Any | Foreign keys: MERGE engine should be disallowed. |
56008 | 2010-08-16 10:59 | 2011-02-16 23:44 | MySQL Server | No Feedback (5281 days) | S2 | mysql-server-5.5.4 | FreeBSD (FreeBSD 7.2-RC1) | Any | Inquiry lag |
68526 | 2013-02-28 15:59 | 2013-04-16 1:00 | MySQL Server: FULLTEXT search | No Feedback (4339 days) | S2 | 5.6.10 | Windows (Server 2003 (SP2)) | Any | Server crash on UPDATEing an InnoDB table when adding a column to the FT index |
74962 | 2014-11-21 13:24 | 2014-11-21 14:20 | MySQL Server: Optimizer | Verified (3754 days) | S3 | 5.5/5.6 | Any | Any | Matching in char field type is not correct |
75515 | 2015-01-15 13:18 | 2015-01-19 16:00 | MySQL Cluster: Cluster (NDB) storage engine | Closed (3695 days) | S3 | 7.4 | Any | Any | Modify SHOW CREATE TABLE output for better OpenStack integration |
109857 | 2023-01-31 8:55 | 2023-02-03 4:54 | MySQL Server: Replication | Duplicate (758 days) | S2 | 5.7.38 | Any | Any | Truncate table with foreign key crash replication. |
116488 | 2024-10-28 8:31 | 2024-10-28 8:33 | MySQL Server: Documentation | Verified (125 days) | S3 | 8.0 | Any | Any | FK constraint checking no longer requires GAP Locks under Read-Committed in 8.0 |
19138 | 2006-04-17 12:52 | 2007-05-03 6:02 | MySQL Server: Memory storage engine | Duplicate (6513 days) | S3 | 5.0.20, 5.0.19, 4.1.20 | Linux (Linux) | Any | The table 'foo' is full displayed on HEAP tables which shouldn't be full |
37968 | 2008-07-08 12:56 | 2008-07-11 21:43 | Connector / NET | Closed (6078 days) | S2 | 5.1.6 | Windows (Server 2003) | Any | Prepared statements byte/tinyint causes data corruption. |
38043 | 2008-07-11 10:50 | 2008-09-30 20:36 | MySQL Server: Falcon storage engine | Closed (5997 days) | S1 | 6.0-falcon | Any | Any | Deadlock between server and falcon when executing concurrent ALTER + DML |
40788 | 2008-11-17 15:21 | 2011-02-16 23:43 | MySQL Server | Duplicate (5910 days) | S2 | 6.0.2 | Windows | Any | Transaction didn't work |
43519 | 2009-03-09 23:32 | 2013-12-20 6:52 | MySQL Server: General | Won't fix (4090 days) | S3 | 6.1.0-alpha-debug | Linux (SUSE 10 | 32-bit) | Any | Foreign keys: no error with RESTRICT and multi-table update |
46521 | 2009-08-03 6:50 | 2011-02-16 23:44 | MySQL Server: Data Types | No Feedback (5659 days) | S2 | 5.0.45 | Linux | Any | can't find rows when date column with primary key |
48148 | 2009-10-19 10:31 | 2011-02-16 23:44 | MySQL Server: Partitions | No Feedback (5550 days) | S2 | 5.1.34-log | Linux | Any | Can select but 1032 error when update and delete |
65648 | 2012-06-18 8:07 | 2013-07-04 13:14 | MySQL Server: InnoDB storage engine | Not a Bug (4259 days) | S2 | 5.1.63, 5.5.24 | Any (Linux, Windows) | Any | Foreign key and uppercase / lowercase values |
67123 | 2012-10-07 13:02 | 2012-10-12 12:56 | MySQL Server: MyISAM storage engine | Verified (4524 days) | S1 | 5.5.27, 5.5.29, 5.1.67, 5.7.0 | Any (MS Windows 2008 64bit, Linux) | Any | error in mi_update.c:226 |
90675 | 2018-04-28 7:30 | 2018-05-02 13:34 | MySQL Server: InnoDB storage engine | Not a Bug (2496 days) | S3 | mysql-5.7 | Any | Any | Improper Record lock With Primary Key. where key >= or <= N |
112589 | 2023-10-02 15:16 | 2024-02-27 14:58 | MySQL Server: Security: Privileges | Closed (369 days) | S3 | 8.0.33, 8.0.34 | Any | Any | ER_ROW_IS_REFERENCED vs ER_ROW_IS_REFERENCED_2 breaks backwards compatibility |
109748 | 2023-01-23 23:06 | 2023-03-17 1:00 | MySQL Workbench | No Feedback (717 days) | S3 | 8.0.32 | MacOS | Any | Error downloading MySQl Workbench 8.0.32 version (Community) |
112145 | 2023-08-23 2:49 | 2023-09-15 14:48 | MySQL Server: DML | Closed (534 days) | S6 | 8.1.0 | Ubuntu (22.04) | x86 (x86_64) | Insert on duplicate assertion error |
113636 | 2024-01-14 10:24 | 2024-01-16 13:00 | MySQL Workbench | Duplicate (411 days) | S1 | 8.0.34 | MacOS (unknown) | Any | Crash when create a new model or open any saved model |
27504 | 2007-03-28 19:34 | 2007-03-29 22:15 | MySQL Server: General | Duplicate (6548 days) | S2 | 5.0.36, 5.0.38 | Linux (Linux 2.6) | Any | Bugfix 23170 for INSERT...SELECT introduces regression to INSERT.. ON DUPLICATE. |
28153 | 2007-04-29 14:10 | 2007-04-29 15:49 | MySQL Server | Closed (6517 days) | S2 | 5.0.37 | Linux | Any | On duplicate update in conjuction with char field doesn't replicate properly |
31737 | 2007-10-21 15:58 | 2007-10-21 17:30 | MySQL Server | Can't repeat (6342 days) | S3 | 5.0.38 | Linux | Any | INSERT SELECT - ON DUPLICATE KEY UPDATE |
37206 | 2008-06-04 21:08 | 2008-06-04 21:45 | MySQL Server | Not a Bug (6115 days) | S3 | 5.0.51a | Any | Any | bulk increment contiguous unique values fails, constraint evaluated row-by-row |
41391 | 2008-12-11 10:57 | 2009-05-15 13:39 | MySQL Server: Falcon storage engine | Closed (5770 days) | S2 | 6.0.9-alpha,6.0.10-alpha | Any | Any | falcon.falcon_bug_22211 fails due to seeing duplicate entry |
108940 | 2022-10-31 16:03 | 2022-11-04 10:09 | MySQL Server: DML | Verified (849 days) | S6 | 8.0.31 | Ubuntu (22.04) | x86 (x86_x64) | Duplicate update column assertion error |
108849 | 2022-10-21 17:09 | 2022-11-04 2:19 | MySQL Router | Verified (850 days) | S3 | 8.0.31 | Any | Any | mysqlrouter bootstrap without password not working / incorrectly prompting |
109079 | 2022-11-14 15:03 | 2022-12-13 14:14 | MySQL Server: InnoDB storage engine | Verified (810 days) | S4 | 5.7.39-log, 8.0.28 | Debian (Not tested on other OSes) | x86 (Not tested on other architectures) | InnoDB: The B-tree of index GEN_CLUST_INDEX is corrupted |
112446 | 2023-09-24 23:24 | 2023-10-03 10:07 | MySQL Server | Can't repeat (517 days) | S2 | 8.0.34 | Debian (Debian 11) | x86 (x86-64) | Fractured read at SERIALIZABLE |
113507 | 2023-12-25 4:04 | 2025-01-15 12:43 | MySQL Server: DDL | Verified (433 days) | S2 | 8.0.35 | Any | Any | gipk add column failed |
117043 | 2024-12-25 8:23 | 2024-12-26 6:40 | MySQL Server: DDL | Duplicate (66 days) | S3 | 8.0.40 | Any | Any | Builder::bulk_add_row do not need to call key_buffer_sort for pk |
2059 | 2003-12-09 10:00 | 2012-05-18 20:19 | MySQL Server | No Feedback (7723 days) | S2 | 4.1.0 | Windows (Windows 2000 SP6) | Any | NATURAL JOIN changed behaviour |
2361 | 2004-01-12 12:22 | 2004-01-14 4:05 | MySQL Server | Closed (7718 days) | S3 | 4.1.2 | Linux (SuSE 8.2) | Any | ALTER TABLE ... DROP PRIMARY KEY drops a non-primary key |
2503 | 2004-01-24 15:20 | 2004-01-24 20:30 | MySQL Server | Not a Bug (7708 days) | S2 | 5.0.0a-alpha | Windows (Window XP Professional) | Any | stored procedure creation errors |
2514 | 2004-01-26 8:40 | 2008-09-29 21:32 | MySQL Server | Can't repeat (5998 days) | S2 | 4.0.18 | Windows (w2k) | Any | TRUNCATE table with merge corupts table |
4285 | 2004-06-25 13:11 | 2005-01-25 16:16 | MySQL Server | Closed (7341 days) | S3 | 4.1.3-beta bk tree | Linux (Linux) | Any | multiple key cache doesn't work properly |
6435 | 2004-11-04 16:06 | 2004-11-08 11:50 | MySQL Cluster: Cluster (NDB) storage engine | Closed (7419 days) | S1 | 4.1.8 bk | Linux (gentoo 2.6) | Any | strange behaviour of left join |
8957 | 2005-03-04 21:23 | 2014-03-28 11:26 | Connector / J | Closed (3992 days) | S1 | 3.1.6-7 | Windows (Win2Kserver) | Any | MySQL service crash without errors |
10912 | 2005-05-27 10:34 | 2012-05-18 20:19 | MySQL Server: Embedded Library ( libmysqld ) | Duplicate (7082 days) | S3 | 5.0.6 + 4.1.15 | various Unix (case-insignif. FS) | Any | Embedded tests show wrong path names |
11869 | 2005-07-11 19:18 | 2005-08-08 15:49 | MySQL Server: Optimizer | Closed (7146 days) | S1 | 4.1.12-nt, 5.0.7-nt-beta/5.0.10 | Windows (Windows XP1/Linux) | Any | Server crashes making a union join query with fulltext search |
12623 | 2005-08-17 13:50 | 2005-08-19 1:09 | MySQL Server | Can't repeat (7135 days) | S1 | >4.1.10 | Linux (LINUX 9.0) | Any | MYSQL CRASH AND HANG THE MACHINE WHILE RUNNING THIS QUERY |
13688 | 2005-10-02 11:43 | 2005-11-13 8:27 | MySQL Server: Stored Routines | Can't repeat (7049 days) | S3 | 5.0.13-rc, 5.0.14-BK | Linux (Linux, Windows) | Any | Lost connection with SELECT queries and DELETE in SP (WITH QUERY CACHE) |
15133 | 2005-11-22 13:32 | 2006-08-17 11:23 | MySQL Server: Federated storage engine | Closed (6772 days) | S2 | 5.0.16/5.0.17 BK | Linux (Linux) | Any | unique index with nullable value not accepted in federated table |
15700 | 2005-12-13 4:52 | 2005-12-13 9:46 | MySQL Server | Duplicate (7019 days) | S1 | 5.0.16 | Linux (linux,windows) | Any | left join return null |
15701 | 2005-12-13 5:03 | 2006-06-29 15:35 | MySQL Server | No Feedback (6821 days) | S2 | ? | Linux (linux, windows) | Any | left join return null (additional for BUg#15700 ) |
15702 | 2005-12-13 6:02 | 2005-12-13 9:50 | MySQL Server | Duplicate (7019 days) | S1 | mysql5.0 | Windows (windows2000,redhat AS3,redhat8) | Any | left join bug |
17106 | 2006-02-03 20:22 | 2006-06-04 4:11 | Connector / NET | Closed (6846 days) | S3 | 1.0.7.30072 | Windows (Windows 2003 Server) | Any | MySql.Data.MySqlClient.CharSetMap.GetEncoding thread synchronization issue |
20389 | 2006-06-12 8:22 | 2006-07-19 4:08 | MySQL Server: Partitions | Closed (6801 days) | S1 | 5.1.12-BK debug, 5.1.11 | Linux (linux 2.4.20-8) | Any | use partition, server crash |
21851 | 2006-08-26 19:04 | 2006-12-28 12:50 | MySQL Server | No Feedback (6639 days) | S1 | 5.0.22 | FreeBSD (FreeBSD 6.1) | Any | Mysql keep crashing with page corruption on disk or a failed file read |
22436 | 2006-09-18 9:55 | 2006-11-06 14:46 | MySQL Server: Tests | Closed (6691 days) | S3 | 5.0.25 | Any (All) | Any | Four tests require "innodb" to be configured, fail in "classic" build |
23081 | 2006-10-07 23:23 | 2006-10-17 15:58 | MySQL Administrator | Closed (6711 days) | S3 | 1.2.4rc | Any (any) | Any | false primary key (only a unique key) makes changes on the column difficult |
24879 | 2006-12-07 11:11 | 2007-06-04 18:13 | MySQL Server: Prepared statements | Closed (6481 days) | S3 | 4.1/5.0/5.1BK | Linux (Linux) | Any | Prepared Statements: CREATE TABLE (UTF8 KEY) produces a growing key length |
26939 | 2007-03-07 23:20 | 2008-01-10 4:56 | MySQL Server: MyISAM storage engine | No Feedback (6261 days) | S3 | 4.1.22, 5.0.45 | Linux (RHEL 3) | Any | We randomly get "MySQL Error 1030: Got error 127 from storage engine" on MyISAM |
27634 | 2007-04-04 5:36 | 2007-06-15 13:45 | MySQL Server: Tests | Closed (6470 days) | S3 | 5.1-bk | Linux | Any | group_by test fails |
27935 | 2007-04-18 20:22 | 2015-03-22 20:45 | MySQL Server: DDL | Duplicate (6205 days) | S3 | 5.1-bk/5.0bk | Linux | Any | TRUNCATE fires DELETE trigger if InnoDB table is referenced by a foreign key |
30747 | 2007-08-31 10:23 | 2007-10-24 20:09 | MySQL Server | Closed (6339 days) | S2 | 5.0 & 5.1 | Any | Any | Create table with identical constraint names behaves incorrectly |
31074 | 2007-09-18 5:04 | 2007-11-25 14:41 | MySQL Server: General | Can't repeat (6307 days) | S3 | 5.0.50, 5.1.23BK | Any | Any | keys on innodb spatial columns cause prefix warnings in logs |
35091 | 2008-03-05 21:50 | 2008-03-07 9:28 | MySQL Server: Data Types | Not a Bug (6204 days) | S3 | 5.0.54a or newer | Any | Any | IF (@...) Returns Incorrect Type - Regression from 5.0.44 |
35952 | 2008-04-10 1:20 | 2008-04-25 20:24 | MySQL Server: Optimizer | Closed (6155 days) | S2 | 5.1.24 | Any | Any | Regression: 5.1.24 Results not returned for users with select privs as expected |
36449 | 2008-05-01 10:09 | 2011-02-16 23:43 | MySQL Server: Optimizer | Closed (5907 days) | S2 | 6.0.6-pre | Any | Any | Significant slowdown for (ANY|SOME) subqueries processed with semijoin |
37067 | 2008-05-29 12:02 | 2011-02-16 23:43 | MySQL Server: FULLTEXT search | Won't fix (5281 days) | S1 | 5.0.51a, 5.0.75, 5.0 bzr | Linux (Centos 5.1 x86_64) | Any | SELECT query hang in state FULLTEXT initialization |
37328 | 2008-06-11 4:50 | 2014-08-12 2:08 | MySQL Server: Optimizer | Won't fix (4514 days) | S3 | 5.0.60, 5.0.64 | Any | Any | Optimizer prefers ref access on multiple-column index over simple range access |
37333 | 2008-06-11 8:58 | 2013-08-07 18:39 | MySQL Server: Optimizer | Closed (4225 days) | S3 | 5.0.60, 5.0.64, 5.1.26 | Any | Any | Optimizer uses wrong index for the right table in LEFT JOIN |
45185 | 2009-05-29 10:19 | 2014-08-18 6:44 | MySQL Server: InnoDB storage engine | Can't repeat (3849 days) | S2 | 5.0.81-log, 5.6.6 | Linux (CentOS) | Any | InnoDB: Warning: using a partial-field key prefix in search |
47330 | 2009-09-15 15:39 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5639 days) | S5 | 5.0.77, 5.1.34, 5.1.37 | Linux (Debian x64) | Any | Slow query with left join and having. |
47906 | 2009-10-08 4:56 | 2011-02-16 23:44 | MySQL Server: Optimizer | No Feedback (5593 days) | S1 | 5.0.85, 5.1.37, 5.1.39, 6.0.9 | Any | Any | Having an extra field in a table changes optimizer index choice for other column |
52204 | 2010-03-19 8:45 | 2011-02-16 23:44 | MySQL Server: InnoDB Plugin storage engine | Can't repeat (5339 days) | S1 | M3 (Celosia) | MacOS (i386 max) | Any | Several tests using innodb fail with "Incorrect key file for table" on Mac OSX |
53631 | 2010-05-13 20:54 | 2010-05-26 20:59 | MySQL Server: MyISAM storage engine | Not a Bug (5394 days) | S3 | 5.0.41-community-log | Linux (CentOS 5.4) | Any | Primary key index size optimisation disagrees with docs |
54225 | 2010-06-04 8:12 | 2020-04-11 2:09 | MySQL Server: Optimizer | Closed (1786 days) | S5 | 5.1.37, 5.1.49, 5.5.5-m3 | Linux (5.1.37-1ubuntu5.1) | Any | Optimizer prefers table scan and filesort instead of index scan |
57888 | 2010-11-01 10:21 | 2013-12-05 10:40 | MySQL Server: Documentation | Can't repeat (4105 days) | S3 | 5.1.51 | Any | Any | OpenSSL vs yaSSL: different behavior of --ssl-ca parameter |
58406 | 2010-11-22 22:02 | 2012-02-06 23:12 | MySQL Server: InnoDB storage engine | Closed (4773 days) | S2 | 5.1,5.6 (from trunk) | Any | Any | Issues with copying partitioned InnoDB tables from Linux to Windows |
59777 | 2011-01-27 12:33 | 2011-04-29 23:00 | MySQL Server: Replication | No Feedback (5057 days) | S1 | 5.1.48, 5.1.55 | Solaris | Any | Replication over SSL; error 2026 most, but not all, of the time |
60457 | 2011-03-14 9:00 | 2011-03-15 9:10 | MySQL Server: Optimizer | Not a Bug (5101 days) | S1 | 5.5.9 | Any | Any | Select is not using index |
62239 | 2011-08-23 13:27 | 2011-11-03 9:33 | MySQL Workbench: Modeling | Verified (4869 days) | S4 | 5.2.23, 5.2.35 | Any | Any | Automatically detect when a relationship is one-to-many or one-to-one |
62679 | 2011-10-11 10:36 | 2011-10-11 12:09 | MySQL Server | Duplicate (4891 days) | S4 | Any | Any | Flow control in SQL scripts | |
65359 | 2012-05-18 12:41 | 2012-05-30 17:01 | MySQL Server: InnoDB storage engine | Duplicate (4659 days) | S2 | 5.1.62 | Linux | Any | bad select performance |
66337 | 2012-08-12 16:31 | 2014-04-18 16:25 | MySQL Cluster: Cluster (NDB) storage engine | Closed (3971 days) | S1 | gpl-7.2.7 | Solaris (5.10 Generic_147441-15 i86pc i386 i86pc) | Any | Cluster crashes Error 2341 (still exists in 7.2.7) |
72907 | 2014-06-07 8:12 | 2014-06-18 7:47 | MySQL Server: Optimizer | Can't repeat (3910 days) | S1 | 5.6.17 | Linux | Any | query on same table in different slave using different plan |
73542 | 2014-08-11 23:28 | 2014-09-13 1:00 | MySQL Workbench: SQL Editor | No Feedback (3824 days) | S2 | 6.1.7 | Windows (Microsoft build 9200, 64-bit) | Any | Dont add Foreign Key |
79006 | 2015-10-28 21:02 | 2018-02-15 8:35 | MySQL Workbench | Won't fix (2572 days) | S3 | 6.3.7 | MacOS (10.11.1) | Any | Cannot use ssh key authentication with new version of OpenSSH private key |
85765 | 2017-04-03 7:43 | 2017-10-16 12:47 | MySQL Server: InnoDB storage engine | Closed (2697 days) | S3 | 8.0.2 (trunk) | Any | Any | Assert !rw_lock_own(lock, RW_LOCK_S) rw_lock_s_lock_func in include/sync0rw.ic |
88704 | 2017-11-29 23:24 | 2017-12-05 13:32 | MySQL Server: Optimizer | Not a Bug (2644 days) | S5 | 5.7.18-ndb-7.6.3-cluster-gpl | Red Hat | Any | Compound index (pkey) not used when it should be |
95042 | 2019-04-17 8:22 | 2019-04-23 7:22 | MySQL Server: Optimizer | Closed (2140 days) | S7 | 5.6.43 | CentOS | x86 | mysql5.6 index problem |
100398 | 2020-07-31 8:33 | 2020-07-31 9:50 | MySQL Server: Optimizer | Verified (1675 days) | S3 | 8.0.19, 5.7.31, 8.0.21 | Any | Any | The results of aggregation operations are inconsistent in different partitions |
103909 | 2021-06-04 6:57 | 2021-11-01 1:00 | Connector / NET | No Feedback (1219 days) | S3 | 8.0.21.0 | Any | Any | Unable to determine the provider name for provider factory of type 'MySql.Data.M |
104249 | 2021-07-08 6:31 | 2021-07-09 18:02 | MySQL Server: Replication | Can't repeat (1332 days) | S2 | 8.0.16 | CentOS (8) | x86 | A field with type integer(12) unsigned is replicated as a bigint |
Showing 1-1000 of 13230 (Edit, Save, CSV, Feed) | Show Next 1000 Entries » |