Bug #54322 UTF BOM from .qbquery files not parsed - results in illegal query
Submitted: 8 Jun 2010 6:17 Modified: 29 Jul 2010 10:31
Reporter: Bruno Baketaric Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench: SQL Editor Severity:S3 (Non-critical)
Version:5.2.22 RC2 OS:Any
Assigned to: Mike Lischke CPU Architecture:Any

[8 Jun 2010 6:17] Bruno Baketaric
Description:
When opnening a .dbquery file created with MySql Query Browser, the SQL-Editor doesn't remove the BOM. This leads into an additional "character" in front of the statement, making it illegal.

How to repeat:
Open a .dbquery-File from MySQL Query Browser
[9 Jun 2010 8:16] Susanne Ebrecht
What exactly do you mean with BOM?
[9 Jun 2010 8:20] Sveta Smirnova
Thank you for the report.

Verified as described:

1. Open MySQL Query Browser
2. Create script file with some easy query like 'select 1'
3. Open WB
4. Load just created file
5. Get error

If MySQL Query Browser created UTF8 files with BOM probably makes sense to be able to open them in WB?
[9 Jun 2010 8:28] Susanne Ebrecht
Dump/restore tools always are created that way that they except input that were generated with same tool. Usually, it is tricky to restore dumps that are made with other tools.

Anyway, I will set this to feature request and we will discuss this.
[9 Jun 2010 8:45] Mike Lischke
As workaround open your files with e.g. Notepad (or any other capable editor) and save them without byte-order-mark.
[9 Jun 2010 10:18] Bruno Baketaric
From my point of view, this is not a feature request. It's a bug. As WB being the successor of the Query-Browser I'd expect WB to successfully open files created with Query-Browser. 
And I'm not talking about a Dump - just a .dbquery-File with a SQL-Statement. 

Anyhow, it's more or less two additional lines in the sources:
if (stream starts with byte-order-mark) {
    remove byte-order-mark
}

I think this could be fixed in 5.2.22 final.
[28 Jun 2010 15:03] Mike Lischke
Fixed in repository
[29 Jul 2010 10:31] Tony Bedford
An entry has been added to the 5.2.25 changelog:

When a .dbquery file, created with MySQL Query Browser, was opened in the SQL Editor, the Byte Order Mark (BOM) was not removed. This led to an erroneous character being prepended to the first statement, making it illegal.