Bug #79067 Built-in data export/import support for MySQL <5.7 not supported anymore?

• Submitted: 2 Nov 2015 9:34
• Modified: 16 Nov 2015 7:29
• Reporter: Mauro Molinari
• Status: Not a Bug
• Category: MySQL Workbench: Administration
• Severity: S2 (Serious)
• Version: 6.3.5
• OS: Any
• CPU Architecture: Any

[2 Nov 2015 9:34] Mauro Molinari

Description:
Sorry if there's a reported issue on this already, but I couldn't find any. 

In the release notes for MySQL Workbench 6.3.5 I read this:

"The bundled mysqldump tool fails to create dumps for MySQL Server 5.6 and earlier."

But is this a temporary problem that will be addressed in the future or something that will stand from now on?

If this is going to stay, I think it constitutes a very important limitation, considering that current stable versions of well-known server Linux distributions carrying MySQL are still providing versions 5.5 and 5.6...
So much that it was introduced in a minor release of MySQL Workbench 6.3 line...

How to repeat:
Try to perform a Data Export from a MySQL 5.5 server

[2 Nov 2015 16:44] Todd Farmer

Hi Mauro,

It's a documented limitation found late in the release cycle of Workbench 6.3.5:

"The bundled mysqldump tool fails to create dumps for MySQL Server 5.6 and earlier. To work around this limitation, set an explicit mysqldump binary in the Workbench preferences under Administration -> Data Export and Import -> Path to mysqldump tool. Use one from MySQL Server 5.6."

http://dev.mysql.com/doc/relnotes/workbench/en/wb-news-6-3-5.html

We do expect this limitation to be lifted in an upcoming maintenance release of WB 6.3.

[2 Nov 2015 16:49] Mauro Molinari

Thank you, it's comforting to know it will be addressed, thank you!

[16 Nov 2015 7:29] MySQL Verification Team

Thank you Todd for the details/clarifications.

@Mauro Molinari,

As Todd pointed out,We do expect this limitation to be lifted in an upcoming maintenance release of WB 6.3.. I'll close this report for now.

Thanks,
Umesh