MySQL Bugs: #80214: workbench 6.3.6

Bug #80214	workbench 6.3.6
Submitted:	1 Feb 2016 1:06	Modified:	13 Apr 2016 7:54
Reporter:	Dan Ciuche	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Workbench	Severity:	S1 (Critical)
Version:	6.3.6	OS:	Windows (windows 10)
Assigned to:		CPU Architecture:	Any
Tags:	Export not working

Description:
Previous version had bugs related to table editing; this version has more serious issues related to exports ( i did not go further than just that); remote server data exports is raising a security error while the local data exports requires path to a mysqldump.exe that does not exist.

How to repeat:
Just try to export tables from a remote server or try to export from a local data base

Remote export

Attachment: workbench_error_remode_export.png (image/x-png, text), 9.63 KiB.

Even import is not working: in the file attached, the first bug related to "lack of db schema information" despite the import is done over an existing db;

the next bug refers to duplicate keys, so similar with 6.3.5 table editor.

I think this is the worse experience i had with workbench and it's stopping production; i have to go to previous working versions which are way back and will take me the rest of the day at least. What is really going on guys? Thanks

importing errors

Attachment: workbench_error_inport.png (image/png, text), 25.36 KiB.

altering table error

Attachment: table_editor_error.png (image/png, text), 16.45 KiB.

On top of exporting/importing not working, now altering table is as well not working, despite i was advised that this error was fixed in this version.
Actually this version of workbench adds so many important bugs that makes it impossible to use any longer. What is going on guys?

Am i wrong with something or these bugs are just being ignored??

Hello Dan,

Thank you for the report.
This is duplicate of Bug #79807

Thanks,
Umesh

Bug #81059 marked as duplicate of this