Bug #61362 Workbench SQL History encoding problem (
)
Submitted: 31 May 2011 15:50 Modified: 31 May 2011 16:36
Reporter: Mike Reid Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:5.2.34 OS:MacOS (10.6.7)
Assigned to: CPU Architecture:Any
Tags: history, query, SQL, workbench

[31 May 2011 15:50] Mike Reid 
Description:
SQL History is not showing up correctly, white space is being represented by 
 and 
. Running SQL from the History section is no longer an option.

How to repeat:
1. Install MySQL Workbench 5.2.34
2. Run some SQL
3. On the "Output" tab, click the "History" label and select the Date in left-hand menu.

4. See the SQL you just ran, only with an unusable encoding (containing 
), etc.

NOTE: Clicking the SQL to send to the editor does not send valid SQL back to the editor. 

If you try and run the SQL from history, you now get an error:

"Error Code: 1064. You have an error in your SQL syntax; ..."

Suggested fix:
Correct the SQL History encoding to run like it did prior to v5.2.34 so that it is usable again.
[31 May 2011 15:52] Peter Laursen 
Same was reported a few days ago in another report.

Peter
(not a MySQL person)
[31 May 2011 16:36] Alfredo Kojima 
This is a duplicate of bug #61345
[22 Sep 2011 9:21] Saul Richman 
I confirm Mike Reid's bug report.

Here is what double-clicking an output from History generates in the scratch query field:

select * from `xxx`.`b_xxx_xxx_xx` where xxx_xxx  = 'xxx' AND application='xxx' AND (Time_in > '00:01:00' AND Time_in < '01:00:00');

It's obviously a non-executable query.
Note: xxx replaces commercial business info.

If it's any help, we use Switzerland(German) keyboards but I doubt that's related.