MySQL Bugs: #59290: blob shows up everywhere

Bug #59290	blob shows up everywhere
Submitted:	4 Jan 2011 20:07	Modified:	15 Jan 2014 19:29
Reporter:	James Richardson	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench	Severity:	S3 (Non-critical)
Version:	5.2.31	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
I tried to run a select query to look over the content of the result.  I did not know the exact name of what I was looking for but knew its general area.  Well with the Workbench, it only shows blob...edit...select...it does not show the text.  it shows blob.  So I have to create a PHP script to output everything (potentially a hundred record) so I can visually inspect and find what i am looking for.

is there a way to turn off this feature?  I am going from phpmyadmin and the old mysql query browser to this tool.

How to repeat:
Open a table and it shows blob

Suggested fix:
make it so that you can select data and it displays the text.  The research online says something about edit.  To view it is to view it, not edit it.  the best suggestion is a new gridview that displays only.  if you want to edit, then you either switch to and edit view or there is an option to edit that single row.

We are very focused on usability.  And, there is always room for improvement.

Perhaps you want to talk to other users on the MySQL Workbench Forums:
http://forums.mysql.com/index.php?151

Some Tweets:  
http://wb.mysql.com/?page_id=724

workbench currently only offers an editor/viewer opened as separate dialog to show/edit blob data. We're planning to improve that.

currently you can only use right-click on a cell and choose "open in viewer/editor".

A regular date field is also rendered as a blob if you do calculations on it:

SELECT IF(1 = 1, FIELD, FIELD) from TABLE

Without the IF it shows just fine as a date field. This is rather irritating as I can't calculate the date to become truly blob anyway.

It appears this is related to the "Treat BINARY/VARBINARY as nonbinary character string" setting, which was fixed in 5.2.43. This bug was combined with that fix, which is Bug #56642 / #11763872.

Thank you for the bug report.