MySQL Bugs: #63207: Unhandled exception: 'ascii' codec can't decode byte 0xce in position 9: ordinal

Bug #63207	Unhandled exception: 'ascii' codec can't decode byte 0xce in position 9: ordinal
Submitted:	11 Nov 2011 15:00	Modified:	11 Dec 2011 21:59
Reporter:	george pligor	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench	Severity:	S1 (Critical)
Version:	5.2.35	OS:	Linux
Assigned to:		CPU Architecture:	Any

Description:
Unhandled exception: 'ascii' codec can't decode byte 0xce in position 9: ordinal not in range(128)

I am using Greek characters. Please fix this asap! It is important to easily transfer dbs from dev server to production server

How to repeat:
Unhandled exception: 'ascii' codec can't decode byte 0xce in position 9: ordinal not in range(128)

Known issue and the most blatant design failure by Workbench team not realizing that in MySQL 5.1+ identifiers are Unicode (and not ASCII).  And also in SQL standards requirement for identifiers is unicode.

If you want to continuew using non-assic characters in identifiers you need another client than WB!

Peter
(not a MySQL person)

Here is the report about same that is 'verified'. It has several duplicates. And now one more.

http://bugs.mysql.com/bug.php?id=56869

Is this a duplicate of bug #56869? Please, check.

Please send a screenshot of the dump screen, where the progress log messages are output.

I know it's a duplicate report. That's why I am insisting! Anyway I found that mysqldump does pretty much the same. I didn't want any extreme options, just an accurate copy of the entire database including data and mysqldump does pretty much the same!
And no I wouldn't change MySQL client. MySQL Workbench is very good, but can be better! Thank you

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".