Bug #62934 Workbench Open Value in Viewer doesn't always work
Submitted: 25 Oct 2011 21:32 Modified: 23 Jul 2012 17:01
Reporter: Chris Wagner Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench: SQL Editor Severity:S3 (Non-critical)
Version:5.2.35 CE OS:Microsoft Windows (XP SP3)
Assigned to: CPU Architecture:Any
Tags: viewer, workbench

[25 Oct 2011 21:32] Chris Wagner
Description:
Normally on any output u can right click on a field and hit Open Value in Viewer.  However under certain non-Select statement results it doesn't work.  One field in the result set will open, others won't.

How to repeat:
Do SHOW FULL PROCESSLIST; in an SQL tab.  Right click on any row in the Info column and click Open Value in Viewer.  Nothing happens.  Doing it on the other fields works.  There are other situations where it doesn't work too.
[25 Oct 2011 21:40] MySQL Verification Team
Thank you for the bug report.
[8 Dec 2011 16:51] Peter Kniaz
Same thing happens with me (Vista).  Makes me have to go back to the old query browser to see the whole query that is running when I do a SHOW FULL PROCESSLIST.
[12 Dec 2011 20:14] Armando Lopez Valencia
Importing to Oracle's bug DB.
Seems that it fails with Number data type and/or Null values.
[23 Jul 2012 17:01] Philip Olson
This has been fixed as of the soon-to-be-released Workbench 5.2.41, and 
here's the changelog entry:

The "Open Value in Editor" SQL editor option did not work with "INT" or 
"NULL" values.