Bug #86992 | update mysqldump to server version... | ||
---|---|---|---|
Submitted: | 9 Jul 2017 6:55 | Modified: | 9 Jul 2017 21:51 |
Reporter: | André verwijs | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server: Windows | Severity: | S5 (Performance) |
Version: | 6.3.9 | OS: | Windows (Microsoft Windows 10 Pro) |
Assigned to: | CPU Architecture: | Any | |
Tags: | WBBugReporter |
[9 Jul 2017 6:55]
André verwijs
[9 Jul 2017 6:56]
André verwijs
added wb-log.rtf..
Attachment: wb.log.rtf (application/rtf, text), 7.33 KiB.
[9 Jul 2017 21:39]
MySQL Verification Team
Microsoft Windows [Version 10.0.15063] (c) 2017 Microsoft Corporation. All rights reserved. c:\dbs>cd\ c:\>cd "Program Files" c:\Program Files>cd MySQL c:\Program Files\MySQL>cd "MySQL Server 5.7" c:\Program Files\MySQL\MySQL Server 5.7>bin\mysqldump --version mysqldump Ver 10.13 Distrib 5.7.18, for Win64 (x86_64) c:\Program Files\MySQL\MySQL Server 5.7>
[9 Jul 2017 21:51]
MySQL Verification Team
Thank you for the bug report. Please check the date where the server 5.7.18 was released and workbench one: https://dev.mysql.com/doc/relnotes/workbench/en/changes-6-3.html Changes in MySQL Workbench 6.3.9 (2017-02-07, General Availability) https://dev.mysql.com/doc/relnotes/mysql/5.7/en/ Changes in MySQL 5.7.18 (2017-04-10, General Availability) So the mysqldump of the server was released after WorkBench 6.3.9 and there is not partial update of the WorkBench stuff.
[11 Aug 2017 14:17]
MySQL Verification Team
https://bugs.mysql.com/bug.php?id=87401n marked as duplicate of this one.
[7 Jun 2018 13:03]
joop poelman
Same for 5.7.22, the MySQLdump.exe in workbench 6.3.10 is referring to 5.7.17. so again mismatch.
[7 Jun 2018 13:04]
joop poelman
back creation is possible, however import is not possible. Joop