MySQL Bugs: #36183: MySQL-Workbench V 5.019; Error in Executing Scripts with Comments in C-Style

Bug #36183	MySQL-Workbench V 5.019; Error in Executing Scripts with Comments in C-Style
Submitted:	17 Apr 2008 18:00	Modified:	22 May 2009 9:30
Reporter:	Hans Grigull	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	MySQL Workbench	Severity:	S3 (Non-critical)
Version:		OS:	Windows (XP SP 2)
Assigned to:	Sergei Tkachenko	CPU Architecture:	Any
Tags:	comments, reverse engineering, utf8

Description:
The MySQL Worbench accepts no comments in C-Style, when the comment contains german mutated vowels

An Example: /* Müller schützt Mädchen */

Message: SQL statement contains non utf8 characters.

The next Statement in Script will not be executed.

In my MySQL-installation I use character set latin 1.

Yours sincerely

Hans Grigull

How to repeat:
Take a Script with Comments above

this doesn't only apply to c-style comments. A line like:
-- Müller
causes same problem. Though the import of objects seem to work.

I think the problem in your case is usage of national codepage for typing source SQL code. Charcodes representing umlauts in that codepage are not valid in UTF8. You should setup your editor properly to be able to enter text in UTF8 encoding. If non of your editors allows you to do this then I would recommend you to try any SciTE derived editor e.g. notepad++ (http://notepad-plus.sourceforge.net).

looks like i maded the same mistake when verifying it (see my comment above). I simply changed the encoding of the file to UTF8 and WB imported it flawlessly.

WB operates on SQL scripts containing only UTF8 symbols.