Showing 1-30 of 94 (Edit, Save, CSV, Feed) Show Next 30 Entries »
ID# Date Updated Type Status Sev Version OS CPU Summary
800552016-01-19
18:55
2016-01-20
9:38
MySQL Server: mysqldump Command-line ClientVerified
(3012 days)
S35.7.10, 5.6.28AnyAnyWrong return code and incosistent error message on --set-gtid-purged=ON
842142016-12-15
10:48
2016-12-15
15:21
MySQL Server: mysqldump Command-line ClientVerified
(2682 days)
S3allAnyAnymysqldump events/routines error if database name include ' character
841582016-12-11
12:15
2017-09-26
12:28
MySQL Server: mysqldump Command-line ClientVerified
(2685 days)
S38.0.0, 5.7.16AnyAnyLoading table with fulltext from mysqldump fails
833392016-10-11
19:45
2022-02-28
0:17
MySQL Server: mysqldump Command-line ClientVerified
(1809 days)
S25.7.13, 5.7.15, 5.7.25CentOSAnymysqldump fails due to max_execution_time with no override possible
832592016-10-05
5:10
2016-10-06
0:41
MySQL Server: mysqldump Command-line ClientVerified
(2752 days)
S35.7.xx, 5.7.15AnyAnyAll routines in the sys schema are deleted by restoring
828592016-09-05
8:25
2016-09-05
16:17
MySQL Server: mysqldump Command-line ClientVerified
(2783 days)
S35.7.14AnyAnyGenerated columns should have version specific comments in dump
828532016-09-04
8:06
2016-09-04
9:42
MySQL Server: mysqldump Command-line ClientVerified
(2784 days)
S35.7.14, 5.6.32, 5.5.51AnyAnymysqldump crashes when invoked with '--compatible=m'
828512016-09-03
9:52
2016-10-06
15:37
MySQL Server: mysqldump Command-line ClientVerified
(2752 days)
S37.5AnyAnymysqldump excludes only the old ndb apply and schema tables
819262016-06-20
8:50
2020-07-27
12:17
MySQL Server: mysqldump Command-line ClientVerified
(2860 days)
S15.7.11, 5.7.13CentOS (6.5)Anymysqldump produce wrong sql on table with virtual json column as primary key
815172016-05-20
11:35
2016-05-24
10:02
MySQL Server: mysqldump Command-line ClientVerified
(2887 days)
S35.5, 5.6.30, 5.7.12AnyAnyInvalid syntax created if mysqldump run with option --where="NEWLINE condition"
809502016-04-04
20:58
2017-10-25
23:47
MySQL Server: mysqldump Command-line ClientVerified
(2368 days)
S35.7AnyAnymysqldump warns about set-gtid-purged=OFF when not dumping data
807902016-03-18
13:16
2021-10-07
20:59
MySQL Server: mysqldump Command-line ClientVerified
(2954 days)
S25.7.11, 5.7.29, 8.0.19AnyAnymysqldump creates invalid dumpfile when generated columns exist
844492017-01-09
19:08
2017-01-09
20:51
MySQL Server: mysqldump Command-line ClientVerified
(2657 days)
S35.5/5.6/5.7/8.0AnyAnySigned zero not preserved by mysqldump/restore
799622016-01-13
19:29
2016-01-14
19:03
MySQL Server: mysqldump Command-line ClientVerified
(3018 days)
S35.5,5.1AnyAnymysqldump wrap index comments in /*!50503 */ version comments.
794962015-12-02
16:13
2015-12-07
7:28
MySQL Server: mysqldump Command-line ClientVerified
(3056 days)
S35.6.27, 5.6.29, 5.7.11AnyAnymysqldump fails for VIEWs which has double quote (") in their name
789322015-10-22
23:56
2015-12-02
12:24
MySQL Server: mysqldump Command-line ClientVerified
(3074 days)
S25.1AnyAnymysqldump --routines misquotes database names
787632015-10-08
16:22
2015-10-08
17:02
MySQL Server: mysqldump Command-line ClientVerified
(3116 days)
S35.6/5.7AnyAnymysqldump with --add-drop-trigger option when trigger name contains dots
777692015-07-17
16:32
2021-11-17
15:00
MySQL Server: mysqldump Command-line ClientVerified
(3194 days)
S35.5/5.6/5.7AnyAnymysqldump includes ALTER DATABASE statement even if --no-create-db option used
755412015-01-17
21:16
2015-08-10
14:34
MySQL Server: mysqldump Command-line ClientVerified
(3378 days)
S35.6.21, 5.6.22, 5.7.6AnyAnymysqldump error message line number is wrong by 1
748992014-11-17
11:18
2020-01-18
18:30
MySQL Server: mysqldump Command-line ClientVerified
(3441 days)
S3all versions up to 5.7.5AnyAnymysqldump should ignore prompt setting in ~/.my.cnf
729232014-06-09
22:08
2015-08-10
14:34
MySQL Server: mysqldump Command-line ClientVerified
(3600 days)
S35.6, 5.7AnyAnymysqldump should work reliably as a non-interactive program
726792014-05-19
12:14
2015-08-10
14:34
MySQL Server: mysqldump Command-line ClientVerified
(3564 days)
S35.6.17, 5.6.21AnyAnyUndocumented behavior when dumping mysql database using mysqldump utility
716142014-02-06
21:30
2015-08-10
14:34
MySQL Server: mysqldump Command-line ClientVerified
(3724 days)
S35.5, 5.6.17AnyAnymysqldump silently skips --triggers when user lacks TRIGGER privilege
709792013-11-22
10:55
2015-08-10
14:34
MySQL Server: mysqldump Command-line ClientVerifiedS3allAnyAnyload of mysqldump script may fail with error 1215 if dest already has tables
953612019-05-13
19:57
2021-03-02
0:52
MySQL Server: mysqldump Command-line ClientVerified
(1802 days)
S35.7, 5.7.26, 5.6.44AnyAnyMysqldump includes database name on create trigger statements.
1140212024-02-16
20:12
2024-02-19
7:37
MySQL Server: mysqldump Command-line ClientVerified
(60 days)
S28.0.35 (at least), 8.0.36Ubuntu (22.04.1)x86mysqldump --replace produces *some* REPLACE IGNORE statements
1134002023-12-12
14:12
2023-12-15
13:44
MySQL Server: mysqldump Command-line ClientVerified
(126 days)
S28.0AnyAnymysqldump generates incorrect sql when skipping generated invisible pk
1127192023-10-13
15:39
2023-10-16
14:23
MySQL Server: mysqldump Command-line ClientVerified
(188 days)
S38.0AnyAnyContribution: mysqldump: add line break after each database row
1117932023-07-18
15:06
2023-07-19
15:45
MySQL Server: mysqldump Command-line ClientVerified
(275 days)
S28.1AnyAnymysqldump memory leaks
1112922023-06-06
11:36
2023-06-08
14:58
MySQL Server: mysqldump Command-line ClientVerified
(316 days)
S38.0AnyAnyGIPK still dumped in SK even with skip GIPK
  Showing 1-30 of 94 (Edit, Save, CSV, Feed) Show Next 30 Entries »