| Showing 1-30 of 36 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 68775 | 2013-03-26 9:22 | 2014-04-29 12:01 | MySQL Server: Command-line Clients | Verified (4383 days) | S3 | 5.6.10 | Any (linux) | Any | GTID_PURGED variable makes mysql dump non backward compatible |
| 68650 | 2013-03-12 13:19 | 2013-04-12 19:15 | MySQL Server: Command-line Clients | Verified (4366 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 |
| 93286 | 2018-11-22 6:43 | 2018-11-22 7:20 | MySQL Server: Command-line Clients | Verified (2316 days) | S2 | 8.0.13 | CentOS (7) | x86 | mysqldump uses deprecated option "NO_KEY_OPTIONS" in 8.0.13 with --skip-opt |
| 78763 | 2015-10-08 16:22 | 2015-10-08 17:02 | MySQL Server: mysqldump Command-line Client | Verified (3457 days) | S3 | 5.6/5.7 | Any | Any | mysqldump with --add-drop-trigger option when trigger name contains dots |
| 80055 | 2016-01-19 18:55 | 2016-01-20 9:38 | MySQL Server: mysqldump Command-line Client | Verified (3353 days) | S3 | 5.7.10, 5.6.28 | Any | Any | Wrong return code and incosistent error message on --set-gtid-purged=ON |
| 51236 | 2010-02-17 10:53 | 2015-08-10 14:34 | MySQL Server: mysqldump Command-line Client | Verified (3674 days) | S3 | 5.6.23 | Any | Any | mysqldump cannot dump tables larger than max_join_size |
| 79962 | 2016-01-13 19:29 | 2016-01-14 19:03 | MySQL Server: mysqldump Command-line Client | Verified (3359 days) | S3 | 5.5,5.1 | Any | Any | mysqldump wrap index comments in /*!50503 */ version comments. |
| 81926 | 2016-06-20 8:50 | 2020-07-27 12:17 | MySQL Server: mysqldump Command-line Client | Verified (3201 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 |
| 75541 | 2015-01-17 21:16 | 2015-08-10 14:34 | MySQL Server: mysqldump Command-line Client | Verified (3719 days) | S3 | 5.6.21, 5.6.22, 5.7.6 | Any | Any | mysqldump error message line number is wrong by 1 |
| 61961 | 2011-07-23 16:58 | 2018-03-01 5:30 | MySQL Server: mysqldump Command-line Client | Verified (4480 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 |
| 72679 | 2014-05-19 12:14 | 2015-08-10 14:34 | MySQL Server: mysqldump Command-line Client | Verified (3905 days) | S3 | 5.6.17, 5.6.21 | Any | Any | Undocumented behavior when dumping mysql database using mysqldump utility |
| 48972 | 2009-11-22 20:03 | 2015-08-10 14:34 | MySQL Server: mysqldump Command-line Client | Verified (4012 days) | S3 | 5.0 | Any | Any | mysqldump --insert-ignore leaves set unique_checks=0. |
| 69311 | 2013-05-23 12:31 | 2015-08-10 14:34 | MySQL Server: mysqldump Command-line Client | Verified (4325 days) | S3 | 5.5.31 | Linux (n.a.) | Any | mysqldump with ignore-table does not consider case senstive table names |
| 64651 | 2012-03-14 19:01 | 2015-08-10 14:34 | MySQL Server: mysqldump Command-line Client | Verified (4760 days) | S2 | 5.1.61, 5.5.21 | Any | Any | mysqldump xml fails to quote string literals |
| 67290 | 2012-10-18 16:10 | 2015-08-10 14:34 | MySQL Server: mysqldump Command-line Client | Verified (4500 days) | S1 | 5.5.27, 5.5.30, 5.7.1, 5.1.67 | Linux (RHEL 5.5 linux2.6 (x86_64) ) | Any | mysqldump 5.5.27 throws error 1049 while dumping routines for db with spl chrs |
| 64390 | 2012-02-21 7:01 | 2015-08-10 14:34 | MySQL Server: mysqldump Command-line Client | Verified (4775 days) | S3 | 5.5.21 | Linux | Any | mysqldump should not restart slave automatically |
| 66035 | 2012-07-26 20:50 | 2015-08-10 14:34 | MySQL Server: mysqldump Command-line Client | Verified (4625 days) | S2 | 5.5.23, 5.5.26 | Any | Any | mysqldump misplace /*!50003 if the word function is present in the procedure |
| 65941 | 2012-07-18 15:42 | 2015-08-10 14:34 | MySQL Server: mysqldump Command-line Client | Verified (4634 days) | S3 | 5.6.5-m8 | Any | Any | mysqldump should use single quote for escaping |
| 64097 | 2012-01-22 8:42 | 2015-08-10 14:34 | MySQL Server: mysqldump Command-line Client | Verified (4812 days) | S3 | 5.1.61, 5.5.20 | Any | Any | mysqldump doesn't generate sorted data by PK for some InnoDB tables |
| 64536 | 2012-03-03 16:56 | 2015-08-10 14:34 | MySQL Server: mysqldump Command-line Client | Verified (4771 days) | S3 | 5.5 | Any | Any | mysqldump using --add-drop-database make it error when restore |
| 58495 | 2010-11-25 14:26 | 2015-08-10 14:34 | MySQL Server: mysqldump Command-line Client | Verified (5235 days) | S2 | 5.0, 5.1, 5.5 | Any | Any | mysqldump doesn't export backslash correctly |
| 56965 | 2010-09-23 9:22 | 2015-08-10 14:34 | MySQL Server: mysqldump Command-line Client | Verified (5292 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 |
| 93566 | 2018-12-11 22:53 | 2018-12-12 6:52 | MySQL Server: mysqldump Command-line Client | Verified (2296 days) | S2 | 5.6.42, 5.7.24 | Debian (http://repo.mysql.com/apt/debian stretch/mysql-5.6) | x86 | mysqldump --compact omits NO_AUTO_VALUE_ON_ZERO option |
| 74899 | 2014-11-17 11:18 | 2020-01-18 18:30 | MySQL Server: mysqldump Command-line Client | Verified (3782 days) | S3 | all versions up to 5.7.5 | Any | Any | mysqldump should ignore prompt setting in ~/.my.cnf |
| 46392 | 2009-07-27 4:13 | 2015-08-10 14:34 | MySQL Server: mysqldump Command-line Client | Verified (5721 days) | S3 | 5.0, 5.1 bzr | Any (MS Windows NT 6, Mac) | Any | mysqldump.exe drops character on its timestamp |
| 44848 | 2009-05-13 15:51 | 2015-08-10 14:34 | MySQL Server: mysqldump Command-line Client | Verified (5493 days) | S1 | 5.0.77, 5.1.45 | Any | Any | mysqldump produces stdout even if it encouters errors |
| 113400 | 2023-12-12 14:12 | 2023-12-15 13:44 | MySQL Server: mysqldump Command-line Client | Verified (467 days) | S2 | 8.0 | Any | Any | mysqldump generates incorrect sql when skipping generated invisible pk |
| 42327 | 2009-01-25 14:55 | 2011-02-16 23:43 | MySQL Server | Verified (5904 days) | S3 | 5.0.67, 5.0 bzr | Any | Any | MySQLDump + Stored Proc bug |
| 37182 | 2008-06-04 5:50 | 2018-07-01 18:08 | MySQL Server: Archive storage engine | Verified (6139 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 |
| 75483 | 2015-01-12 19:02 | 2015-01-14 13:33 | MySQL Server: Charsets | Verified (3724 days) | S1 | 5.5.28, 5.6.24, 5.5.42 | Any | Any | Mysqldump bit information dumped in the txt file has whitespace |
| Showing 1-30 of 36 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
