MySQL server 5.6 + MySQL WorkBench 5.2.47 = dump error under OSX

This article is a little bit old… WorkBench has been updated! Please, see this post!

I was hoping to going to sleep early tonight, but I discovered a bug with mySQL 5.6 and the Workbench tool. I used the latest releases since last week. No problems at all for importing data or working on databases and tables.

BUT…

There’s a problem if you try to export your tables:

when you try to dump your tables, you get this

WARNING

/Applications/MySQLWorkbench.app/Contents/MacOS/mysqldump is version 5.5.24, but the MySQL Server to be dumped has version 5.6.10-log.

Because the version of mysqldump is older than the server, some features may not be backed up properly.

It is recommended you upgrade your local MySQL client programs, including mysqldump to a version equal to or newer than that of the target server.

The path to the dump tool must then be set in Preferences -> Administrator -> Path to mysqldump Tool:

If you proceed you’ll probably get:

mysqldump: Couldn’t execute ‘SET OPTION SQL_QUOTE_SHOW_CREATE=1′: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ‘OPTION SQL_QUOTE_SHOW_CREATE=1′ at line 1 (1064)

I searched google for 30 minutes, then as someone told that the mysqldump version was wrong, and that he got different versions of that file in his system (under Linux I think) I searched for the mysqldump file.

I found one in the mySQL Workbench app folder (/Applications/MySQLWorkbench.app/Contents/MacOS/mysqldump) , and one inside the mySQL Server folder (/usr/local/mysql/bin/mysqldump). Different creation dates… So I opened the WB and I went to Preferences > Administrator > Path to mysqldump tool, and I added this:

/usr/local/mysql/bin/mysqldump

After that, my dump went smooth as silk, no more errors.

I hope that helps until a fixed WB tool!

Cheers!

m4s0n501
Posted in mySQL Tagged with: , , ,
17 comments on “MySQL server 5.6 + MySQL WorkBench 5.2.47 = dump error under OSX
  1. Victor Gil says:

    Thank you, it helps me a lot…

  2. Pascal says:

    Thanks a lot! Easy fix, once you know it..

  3. Yoosaf says:

    Awesome Fix man!!!

  4. Bruno says:

    It works. thanks a lot!

  5. André Caribé says:

    Thank you! This was very helpful.

  6. edu says:

    That helped A LOT !!!

    Thanks

  7. Chris says:

    Thanks so much for the tip! worked great for me – got an assignment to submit in 2 days and couldnt export my db!

  8. Thankssssss. You help me a lot.

  9. Frank says:

    Thanks! that was a big help!

  10. olivier says:

    Thank you very much.I didn’t find the solution before visitting this web site!!

  11. yossi says:

    Thanks mate that’s helps a lot

  12. Neo-SK says:

    Thanks a lot dude… You made my life easy … :) Cheers

  13. Korgoth says:

    Thanks a lot! I was not able to export my table/data without this change.

  14. Stewe Jorn says:

    Helpfull information! Thanks! When I used MySQLWorkbench I had a lot of similar problems. Now I use dbForge Studio for MySQL. It has a built in MySQL Backup tool: http://www.devart.com/dbforge/mysql/studio/mysql-backup.html

  15. malike says:

    Not so far I have found new cool tool to work with mySQL – Valentina Studio. Its free edition can do things more than many commercial tools!!
    I very recommend check it. http://www.valentina-db.com/en/valentina-studio-overview

1 Pings/Trackbacks for "MySQL server 5.6 + MySQL WorkBench 5.2.47 = dump error under OSX"
  1. […] I just tested the import/export feature, exporting a DB ad importing it successfully, without using my workbench 5.2.47 fix. […]

Leave a Reply

Your email address will not be published. Required fields are marked *

*

fourteen − 7 =

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>