MySQL Bugs: #65230: MySQL Workbench. Semicolon after comments before statement?

Bug #65230	MySQL Workbench. Semicolon after comments before statement?
Submitted:	7 May 2012 19:22	Modified:	10 Jun 2012 19:26
Reporter:	Dmytro Piddubetskyy	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench: SQL Editor	Severity:	S2 (Serious)
Version:	5.2	OS:	MacOS
Assigned to:		CPU Architecture:	Any
Tags:	osx, workbench

Description:
In MySQL Workbench (Mac) if not to put semicolon before statement after comments, statement is not executed. So DROP, USE and CREATE TABLE not executing without ; and next statement gives error..

No issue on windows or linux. tried reinstall and everything. 

If delete semicolon before DROP, next statement CREATE DATABASE gives error - database cannot be created because already exists. If delete semicolon before USE -> CREATE TABLE don't execute, and if before CREATE TABLE - table simply not created.

How to repeat:
-- launch Workbench on Mac OSX
-- Remove semicolons after comments

;DROP DATABASE IF EXISTS dbDataBase;

CREATE DATABASE dbDataBase
    CHARACTER SET 'utf8'
    COLLATE 'utf8_general_ci'; -- define set of rules to compare characters

;USE dbDataBase;

-- Make a table
;CREATE TABLE Teams
(
     teamID    INTEGER UNSIGNED NOT NULL,
     teamName  VARCHAR(50)      NOT NULL
);

Issue seems to appear only when working with local MySQL databases. Everything executes when working with my remote host MySQL DB, they run version 5.1.56 though. Locally I run MySQL Server 5.5.23

I can confirm that this doesn't happen neither in Windows (Windows 7 WB 5.2.39) nor in Linux (Ubuntu 11.10 WB trunk). The original report was posted here: http://stackoverflow.com/q/10484686/94484

The OP seems to suggest that he gets this issue with latest the WB version (5.2.39 as of today) although from his comments is not really clear whether this was the version he is running in his Mac.

Problem cause found.

It has something to do with character encoding and editing sql file with multiple editors.
In my case if *.sql file is created with "Sublime" editor and then reopened/edited and saved with Workbench - issue persists. If to copy all text from workbench editor dialog, open new window in Workbench to create new query and paste text - queries run with no errors.

So problem has to do with parsing existing .sql files while opening them. To solve the problem probably would be to make Workbench rewrite/encode all sql file in its own way while opening it, or saving it if changes had been made.

Please, upload some file that demonstrates the problem. This may help to find out what exact characters/bytes in it makes Workbench to work in this weird way.

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".