Export Data from mysql Workbench 6.0

DatabaseExportMysqldumpMysql Workbench

Database Problem Overview


I'm trying to export my database, using MySQL Workbench 6.0 on Windows, to send to my db instance in Amazon RDS, but i'm getting this error:

Operation failed with exitcode 7
11:34:40 Dumping clubbin (taxicompanies)
Running: "C:\Program Files\MySQL\MySQL Server 5.7\bin\mysqldump.exe"
-defaults-extra- file="c:\users\selene\appdata\local\temp\tmp6o0hno.cnf"
--max_allowed_packet=1G --delayed-   insert=FALSE --host=localhost --user=root
--port=3306 --default-character-set=utf8 "clubbin"   "taxicompanies"
mysqldump: [ERROR] unknown variable 'delayed-insert=FALSE'

Does anybody have any idea that can help me?

Database Solutions


Solution 1 - Database

> mysqldump: [ERROR] unknown variable 'delayed-insert=FALSE'


This error occurs on various systems and can be temporarily fixed by:

  1. Going to the appropriate directory depending on the system:

    a) Windows: C:\Program Files\MySQL\MySQL Workbench 6.3 CE\modules (32-bit installation on x64 systems: C:\Program Files (x86)\MySQL\MySQL Workbench 6.3 CE\modules)

    b) Mac OS X: Applications/MYSQLWorkbench.app/Contents/Resources/plugins - right click on the app and select Show Package contents to get inside the app (thanks to Bradley Flood)

    c) Linux Ubuntu: /usr/lib/mysql-workbench/modules (thanks to Alessandro Lopes)

  2. Open file wb_admin_export_options.py

  3. Find line "delayed-insert":["Write INSERT DELAYED statements rather than ...

  4. Insert # at the begin of this line to comment it out

  5. Save file and restart Workbench.


Tested on Windows 7 x64, MySQL 5.6.27 (MyISAM) & Workbench 6.3.5 x64.

Tested on OSX Yosemite 10.10.4, MySQL 5.5.27 (MyISAM), Workbench 6.3.5 build 201 CE x64.

Solution 2 - Database

This worked for me.

Edit the file C:\Program Files\MySQL\MySQL Workbench 6.3 CE\modules\wb_admin_export_options.py (make sure you open your editor as administrator)

find the line:

delayed-insert":["Write INSERT DELAYED statements rather than INSERT statements.","FALSE", "BOOL", ("5.0.0", "5.7.0")],

and put a hash “#” at the beginning of the line so that it looks like this:

# delayed-insert":["Write INSERT DELAYED statements rather than INSERT statements.","FALSE", "BOOL", ("5.0.0", "5.7.0")],

This will comment the line out so that Workbench won’t use this statement.

Save and close the file.

Start Workbench and try again.

Reference http://dannytsang.co.uk/mysql-workbench-error-code-7/

Solution 3 - Database

On Linux Ubuntu/Mint:

The config file is located at : /usr/lib/mysql-workbench/modules/wb_admin_export_options.py

As described by c4pricorn, simply comment the line "delayed-insert":["Write INSERT DELAYED statements rather than...

And restart workbench.

Solution 4 - Database

Delayed inserts where deprecated in 5.6 and are converted to normal inserts in 5.7 (see also http://dev.mysql.com/doc/refman/5.7/en/insert-delayed.html). I wonder why mysqldump reports an error on this. Regardless, MySQL Workbench must be adjusted to no use delayed-insert for dumps. Can you please file a bug report at http://bugs.mysql.com to bring this on the agenta for MySQL Workbench?

Solution 5 - Database

In CentOS 7,

Open file /usr/lib64/mysql-workbench/modules/wb_admin_export_options.py Find line "delayed-insert":["Write INSERT DELAYED statements rather than ... Insert # at the begin of this line to comment it out Save file and restart Workbench.

Solution 6 - Database

As highlighted at an earlier post, by putting a # at the delayed-insert line in wb_admin_export_options.py does solves the problem.What i like to add is that when i tried to edit it in notepad and Pythonwin,i encountered the admin rights issue.They don't let me save the file after my edit.I finally work around it by editing and saving it in notepad++.One can download it from here https://notepad-plus-plus.org/

Solution 7 - Database

Removing delayed-insert line in wb_admin_export_options.py solves the problem. You need to get admin rights to modify the file.

Nonetheless consider that your MySQL database might have been not properly upgraded before.

Solution 8 - Database

Be careful on editor: on Win7 64 notepad doesn't work on this modification. Notepad will present a single line, use an editor with crlf.

Solution 9 - Database

I had this error until I upgraded to the latest version. Currently 8.0.15. That fixed it on my Mac.

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionRodrigo AraujoView Question on Stackoverflow
Solution 1 - Databasec4pricornView Answer on Stackoverflow
Solution 2 - DatabaseOlakunle AwotunboView Answer on Stackoverflow
Solution 3 - DatabaseAlessandro LopesView Answer on Stackoverflow
Solution 4 - DatabaseMike LischkeView Answer on Stackoverflow
Solution 5 - Databasegaurav kumarView Answer on Stackoverflow
Solution 6 - DatabaseC.PohView Answer on Stackoverflow
Solution 7 - DatabaseBartView Answer on Stackoverflow
Solution 8 - DatabaseandreAView Answer on Stackoverflow
Solution 9 - DatabasepinkpView Answer on Stackoverflow