Showing 1-30 of 49 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
2562 | 2004-01-29 13:55 | 2015-08-10 14:32 | MySQL Server: mysqldump Command-line Client | Duplicate (7386 days) | S1 | 4.0.17 | not relevant | Any | mysqldump creates inserts for merge tables |
81439 | 2016-05-16 18:07 | 2016-05-16 21:49 | MySQL Server: mysqldump Command-line Client | Duplicate (2895 days) | S1 | 5.6.30 | Windows ( Ver 14.14 Distrib 5.6.30, for Win64 (x86_64)) | Any | mysqldump don't work |
68037 | 2013-01-05 20:37 | 2015-08-10 14:34 | MySQL Server: mysqldump Command-line Client | Duplicate (4122 days) | S1 | 5.6.9 | Any | Any | mysqldump output fails to restore, due to syntax error |
57451 | 2010-10-14 11:02 | 2015-08-10 14:34 | MySQL Server: mysqldump Command-line Client | Duplicate (4936 days) | S1 | 5.5.6 | Any | Any | mysqldump omits events |
98717 | 2020-02-23 14:57 | 2020-02-24 5:39 | MySQL Server: mysqldump Command-line Client | Duplicate (1516 days) | S1 | 5.7.x, 5.7.29 | Debian | x86 | generated column causes mysqldump to create extremely big dump file |
33543 | 2007-12-27 22:16 | 2015-08-10 14:33 | MySQL Server: mysqldump Command-line Client | Duplicate (5490 days) | S1 | 5.1.22 | Linux | Any | mysqldump and hotcopy don't escape database names appropriately in use statement |
32563 | 2007-11-21 9:04 | 2015-08-10 14:33 | MySQL Server: mysqldump Command-line Client | Duplicate (5701 days) | S1 | 5.1, 5.0, 6.0 BK | Linux (REDHAT ES4) | Any | mysqldump no data dumped |
10453 | 2005-05-08 22:03 | 2015-08-10 14:33 | MySQL Server: mysqldump Command-line Client | Duplicate (6917 days) | S1 | 5.0.4-beta | Any (*) | Any | mysqldump escapes incorrectly |
8275 | 2005-02-02 20:58 | 2015-08-10 14:33 | MySQL Server: mysqldump Command-line Client | Duplicate (6944 days) | S1 | 4.1.8, 4.1.9 | 2003, 2000 | Any | Mysqldump adds incorect path when full dump, ie 'c:\mysql\data' should be c:\\m |
6212 | 2004-10-22 11:11 | 2015-08-10 14:33 | MySQL Server: mysqldump Command-line Client | Duplicate (7119 days) | S1 | 4.0.21 | Windows (Windows XP SP 2) | Any | mysqldump causes MySQL to crash |
5530 | 2004-09-12 3:09 | 2015-08-10 14:33 | MySQL Server: mysqldump Command-line Client | Duplicate (7113 days) | S1 | 4.0.21 | Linux (Linux) | Any | mysqldump connection lost |
5981 | 2004-10-08 12:44 | 2015-08-10 14:33 | MySQL Server: mysqldump Command-line Client | Duplicate (7127 days) | S1 | 4.0.21-3 | Linux (Debian GNU/Linux (i386)) | Any | mysqldump importation it's bad done |
5749 | 2004-09-26 8:45 | 2015-08-10 14:33 | MySQL Server: mysqldump Command-line Client | Duplicate (7111 days) | S1 | 4.0.21 | Linux (Fedora Core 2) | Any | After update from 4.0.20 to 4.0.21 mysqldump will crash |
100686 | 2020-08-29 0:50 | 2021-05-28 14:50 | MySQL Server: mysqldump Command-line Client | Duplicate (1329 days) | S2 | 8.0.18 | Any | Any | 8.0 mysqldump does not work against 5.7 server |
4047 | 2004-06-08 0:03 | 2016-01-03 20:45 | MySQL Server: mysqldump Command-line Client | Duplicate (7142 days) | S2 | 4.1.3 | Linux (Linux) | Any | mysqldump loses connection on InnoDB tables |
88879 | 2017-12-12 15:34 | 2017-12-15 8:06 | MySQL Server: mysqldump Command-line Client | Duplicate (2317 days) | S2 | 5.7 | Any | Any | Make mysqldump --all-tablespaces to work with InnoDB general tablespaces as well |
71902 | 2014-03-03 2:37 | 2015-08-10 14:34 | MySQL Server: mysqldump Command-line Client | Duplicate (3691 days) | S2 | 5.6.16 | Any | Any | mysqldump doesn't produce consistent GTID_EXECUTED without --master-data=2 |
79004 | 2015-10-28 16:20 | 2015-10-28 19:34 | MySQL Server: mysqldump Command-line Client | Duplicate (3096 days) | S2 | workbeanch 6.3 | Windows (8.1) | Any | [ERROR] unknown variable 'delayed-insert=FALSE' |
79992 | 2016-01-14 20:53 | 2016-01-15 5:58 | MySQL Server: mysqldump Command-line Client | Duplicate (3017 days) | S2 | 5.7.10 | MacOS | Any | mysqldump 5.7.10 cannot be used to reload database |
5693 | 2004-09-22 6:59 | 2015-08-10 14:33 | MySQL Server: mysqldump Command-line Client | Duplicate (7114 days) | S2 | 10.7 Distrib 4.1.2-alpha | pc-linux (i686) | Any | mysqldump encoding of enum/default values |
100219 | 2020-07-14 15:04 | 2022-07-06 12:57 | MySQL Server: mysqldump Command-line Client | Duplicate (1134 days) | S2 | 8.0.21, 8.0.29 | Linux | x86 | mysqldump Access denied Error after upgrading to 8.0.21 |
41958 | 2009-01-08 12:29 | 2015-08-10 14:34 | MySQL Server: mysqldump Command-line Client | Duplicate (5574 days) | S2 | Any | Any | mysqldump shouldn't dump triggers before data | |
35282 | 2008-03-14 8:38 | 2015-08-10 14:34 | MySQL Server: mysqldump Command-line Client | Duplicate (5877 days) | S2 | mysql-5.1.23-ndb-6.3.10, 5.1, 6.0 BK | Any | Any | mysqldumpslow seems not able to handle the microsecond format of slow query log |
26114 | 2007-02-06 13:28 | 2015-08-10 14:33 | MySQL Server: mysqldump Command-line Client | Duplicate (6217 days) | S2 | 5.0.26 | Linux (Centos 4.3) | Any | mysqldump failes with "too many open files" on busy server |
25920 | 2007-01-29 16:02 | 2015-08-10 14:33 | MySQL Server: mysqldump Command-line Client | Duplicate (6233 days) | S2 | 5.0 | Linux (Linux/Sparc) | Any | Bus error mysqldump efter upgrade 4.1 to 5.x |
22761 | 2006-09-27 19:43 | 2015-08-10 14:33 | MySQL Server: mysqldump Command-line Client | Duplicate (6206 days) | S2 | 5.0.24 | Any (Any) | Any | mysqldump reports no errors when using --routines without mysql.proc privileges |
15208 | 2005-11-24 0:08 | 2015-08-10 14:33 | MySQL Server: mysqldump Command-line Client | Duplicate (6699 days) | S2 | 5.0.15, 5.0.16 | Windows (Windows, Linux) | Any | mysqldump --compatible=mysql40 doesn't dump auto_increment |
109701 | 2023-01-19 11:11 | 2023-02-21 22:39 | MySQL Server: mysqldump Command-line Client | Duplicate (423 days) | S3 | 8.0.32 | Any | Any | Fix for #33630199 in 8.0.32 introduces regression when --set-gtid-purged=OFF |
84479 | 2017-01-12 7:20 | 2017-01-12 7:57 | MySQL Server: mysqldump Command-line Client | Duplicate (2654 days) | S3 | 5.6+ | Any | Any | mysql not consist with single-transaction when use gtid |
1028 | 2003-08-11 8:13 | 2015-08-10 14:31 | MySQL Server: mysqldump Command-line Client | Duplicate (7557 days) | S3 | 3.23.56 | Linux (redhat-linux-gnu) | Any | mysqldump does not escape possible column name "DESC" |
Showing 1-30 of 49 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |