| Showing 1-30 of 37 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 51236 | 2010-02-17 10:53 | 2015-08-10 14:34 | MySQL Server: mysqldump Command-line Client | Verified (3505 days) | S3 | 5.6.23 | Any | Any | mysqldump cannot dump tables larger than max_join_size |
| 37182 | 2008-06-04 5:50 | 2018-07-01 18:08 | MySQL Server: Archive storage engine | Verified (5970 days) | S3 | 5.1.24, 5.1.30 | Any (RH Linux 64, WinXP) | Any | Dumped Archive table with AUTO_INCRMENET PRIMARY KEY won't restore from dump |
| 68775 | 2013-03-26 9:22 | 2014-04-29 12:01 | MySQL Server: Command-line Clients | Verified (4214 days) | S3 | 5.6.10 | Any (linux) | Any | GTID_PURGED variable makes mysql dump non backward compatible |
| 48972 | 2009-11-22 20:03 | 2015-08-10 14:34 | MySQL Server: mysqldump Command-line Client | Verified (3843 days) | S3 | 5.0 | Any | Any | mysqldump --insert-ignore leaves set unique_checks=0. |
| 72679 | 2014-05-19 12:14 | 2015-08-10 14:34 | MySQL Server: mysqldump Command-line Client | Verified (3736 days) | S3 | 5.6.17, 5.6.21 | Any | Any | Undocumented behavior when dumping mysql database using mysqldump utility |
| 75483 | 2015-01-12 19:02 | 2015-01-14 13:33 | MySQL Server: Charsets | Verified (3555 days) | S1 | 5.5.28, 5.6.24, 5.5.42 | Any | Any | Mysqldump bit information dumped in the txt file has whitespace |
| 75541 | 2015-01-17 21:16 | 2015-08-10 14:34 | MySQL Server: mysqldump Command-line Client | Verified (3550 days) | S3 | 5.6.21, 5.6.22, 5.7.6 | Any | Any | mysqldump error message line number is wrong by 1 |
| 77436 | 2015-06-22 14:55 | 2015-06-23 10:44 | MySQL Server: Options | Verified (3395 days) | S2 | 5.6.23, 5.6.26 | Linux | Any | procs_priv table not restored with sql_mode traditional and only_full_group_by |
| 79962 | 2016-01-13 19:29 | 2016-01-14 19:03 | MySQL Server: mysqldump Command-line Client | Verified (3190 days) | S3 | 5.5,5.1 | Any | Any | mysqldump wrap index comments in /*!50503 */ version comments. |
| 68650 | 2013-03-12 13:19 | 2013-04-12 19:15 | MySQL Server: Command-line Clients | Verified (4197 days) | S3 | 5.5.30, 5.1.70, 5.5.32, 5.6.12, 5.7.2 | Linux | Any | Dump restoration does not create events |
| 80055 | 2016-01-19 18:55 | 2016-01-20 9:38 | MySQL Server: mysqldump Command-line Client | Verified (3184 days) | S3 | 5.7.10, 5.6.28 | Any | Any | Wrong return code and incosistent error message on --set-gtid-purged=ON |
| 78763 | 2015-10-08 16:22 | 2015-10-08 17:02 | MySQL Server: mysqldump Command-line Client | Verified (3288 days) | S3 | 5.6/5.7 | Any | Any | mysqldump with --add-drop-trigger option when trigger name contains dots |
| 81926 | 2016-06-20 8:50 | 2020-07-27 12:17 | MySQL Server: mysqldump Command-line Client | Verified (3032 days) | S1 | 5.7.11, 5.7.13 | CentOS (6.5) | Any | mysqldump produce wrong sql on table with virtual json column as primary key |
| 80347 | 2016-02-12 5:02 | 2016-11-08 13:39 | MySQL Server: FULLTEXT search | Verified (2891 days) | S2 | 5.7.9, 5.7.11 | Any | Any | mysqldump backup restore fails due to invalid FTS_DOC_ID (Error 182 and 1030) |
| 61961 | 2011-07-23 16:58 | 2018-03-01 5:30 | MySQL Server: mysqldump Command-line Client | Verified (4311 days) | S3 | 5.0.75, 5.0.97, 5.1.68, 5.5.30, 5.7.1 | Any (IBM AIX, Linux) | Any | mysqldump has wrong order for views with functions |
| 74899 | 2014-11-17 11:18 | 2020-01-18 18:30 | MySQL Server: mysqldump Command-line Client | Verified (3613 days) | S3 | all versions up to 5.7.5 | Any | Any | mysqldump should ignore prompt setting in ~/.my.cnf |
| 111793 | 2023-07-18 15:06 | 2023-07-19 15:45 | MySQL Server: mysqldump Command-line Client | Verified (447 days) | S2 | 8.1 | Any | Any | mysqldump memory leaks |
| 113400 | 2023-12-12 14:12 | 2023-12-15 13:44 | MySQL Server: mysqldump Command-line Client | Verified (298 days) | S2 | 8.0 | Any | Any | mysqldump generates incorrect sql when skipping generated invisible pk |
| 58495 | 2010-11-25 14:26 | 2015-08-10 14:34 | MySQL Server: mysqldump Command-line Client | Verified (5066 days) | S2 | 5.0, 5.1, 5.5 | Any | Any | mysqldump doesn't export backslash correctly |
| 42327 | 2009-01-25 14:55 | 2011-02-16 23:43 | MySQL Server | Verified (5735 days) | S3 | 5.0.67, 5.0 bzr | Any | Any | MySQLDump + Stored Proc bug |
| 44848 | 2009-05-13 15:51 | 2015-08-10 14:34 | MySQL Server: mysqldump Command-line Client | Verified (5324 days) | S1 | 5.0.77, 5.1.45 | Any | Any | mysqldump produces stdout even if it encouters errors |
| 46392 | 2009-07-27 4:13 | 2015-08-10 14:34 | MySQL Server: mysqldump Command-line Client | Verified (5552 days) | S3 | 5.0, 5.1 bzr | Any (MS Windows NT 6, Mac) | Any | mysqldump.exe drops character on its timestamp |
| 51984 | 2010-03-12 11:17 | 2012-05-18 20:19 | Tests | Verified (5324 days) | S3 | 5.1.44, 5.5.3 | Windows | Any | mysqldump test will not succeed if not preceeded by a test that succeeds as well |
| 54371 | 2010-06-09 15:32 | 2022-12-04 20:45 | MySQL Server: Security: Privileges | Verified (5234 days) | S3 | 5.1.44, 5.1.49-bzr | Linux | Any | Privileges required to use --events option for mysqldump |
| 56965 | 2010-09-23 9:22 | 2015-08-10 14:34 | MySQL Server: mysqldump Command-line Client | Verified (5123 days) | S3 | 5.1.44 | Linux (2.6.18-164.6.1.el5 #1 SMP, CentOS 5.5) | Any | mysqldump poor performance with large number of tables |
| 58491 | 2010-11-25 12:59 | 2024-09-20 10:34 | MySQL Server: mysqldump Command-line Client | Verified (5064 days) | S3 | 5.1.52, 5.0, 5.1, 5.6.1 | Any | Any | --compact removes --tz-utc in mysqldump |
| 69311 | 2013-05-23 12:31 | 2015-08-10 14:34 | MySQL Server: mysqldump Command-line Client | Verified (4156 days) | S3 | 5.5.31 | Linux (n.a.) | Any | mysqldump with ignore-table does not consider case senstive table names |
| 64536 | 2012-03-03 16:56 | 2015-08-10 14:34 | MySQL Server: mysqldump Command-line Client | Verified (4602 days) | S3 | 5.5 | Any | Any | mysqldump using --add-drop-database make it error when restore |
| 64097 | 2012-01-22 8:42 | 2015-08-10 14:34 | MySQL Server: mysqldump Command-line Client | Verified (4643 days) | S3 | 5.1.61, 5.5.20 | Any | Any | mysqldump doesn't generate sorted data by PK for some InnoDB tables |
| 65941 | 2012-07-18 15:42 | 2015-08-10 14:34 | MySQL Server: mysqldump Command-line Client | Verified (4465 days) | S3 | 5.6.5-m8 | Any | Any | mysqldump should use single quote for escaping |
| Showing 1-30 of 37 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
