MySQL Bugs: #57935: Critical error on dump export

Bug #57935	Critical error on dump export
Submitted:	2 Nov 2010 18:43	Modified:	16 Nov 2010 18:06
Reporter:	Eugene Pavlov	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Workbench: Administration	Severity:	S3 (Non-critical)
Version:	MySQL Workbench 5.2.29 CE, Revision 6756	OS:	Windows (XP Pro SP3 Russian)
Assigned to:		CPU Architecture:	Any
Tags:	dump

Description:
I want to export database dump to file on disk but I can't.

Error message:
Unhandled exception: 'ascii' codec can't decode byte 0xad in position 16: ordinal not in range(128)

Status bar:
Error in dump module: error calling WbAdmin.openExportImport: see output for details

Output:
====================================================================
Traceback (most recent call last):

 File "C:\Program Files\MySQL\MySQL Workbench 5.2 CE\modules\wb_admin_configuration.py", line 206, in tab_changed

    panel.page_activated()

 File "C:\Program Files\MySQL\MySQL Workbench 5.2 CE\modules\wb_admin_export.py", line 1751, in page_activated

    self.export_tab.check_mysqldump_version()

 File "C:\Program Files\MySQL\MySQL Workbench 5.2 CE\modules\wb_admin_export.py", line 1291, in check_mysqldump_version

    msg = "Could not parse version number from %s:\n%s"%(path, output)

UnicodeDecodeError: 'ascii' codec can't decode byte 0xad in position 16: ordinal not in range(128)
====================================================================

And there are no controls, just blank white form.
So I can do nothing with Import/Export.

When I connected to the server by telnet I got respond:

5.0.51a-24+lenny4-logW☺~Z(W^Sd|,в!☻c\%@Tdz[9ICU

It contains Cyrillic symbol.
MySQL server runs on the remote server machine (Ver 14.12 Distrib 5.0.51a, for debian-linux-gnu (i486) using readline 5.2), I can't manage it.

Checked on localhost 5.1.47-community and get the same bug.

Schema not contains any Cyrillic symbols at it's name or tables' names.

How to repeat:
1. I have registered new server instance without SSH support;
2. Clicked on «Manage Import / Export»;
3. Selected server;
4. Clicked «Data dump» and got error message

Do you have non-ascii identifiers (database names, table names etc.)?

WB code (naively) assumes exclusively ascii used for identifiers. There are more reports about same.  Fact is that from MySQL 5.1 the full unicode-range can be used for identifiers (as far as I remember with the sole exception of the NULL-character)

Peter
(not a MySQL person)

Hello, Peter!

No, I do not use any non-ascii symbols for database, table or field names. Only latin symbols and "_".

Thank you for the feedback.

This is duplicate of bug #56869