MySQL Bugs: #97166: "Search Table Data..." for multiple tables fails if one has blob data

Bug #97166	"Search Table Data..." for multiple tables fails if one has blob data
Submitted:	9 Oct 2019 16:16	Modified:	31 Oct 2019 5:29
Reporter:	Evan Thompson	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Workbench	Severity:	S2 (Serious)
Version:	8.0.17	OS:	Windows
Assigned to:		CPU Architecture:	Any
Tags:	search

Description:
Before upgrade, I could select a either database in the list or ctrl-select multiple tables in a database, right click and 'Search Table Data...' and it would work. After upgrade, it almost immediately returned '0 rows matched in 2 searched tables.'

I tracked down the problem. One of the tables- the third of about 200- has an unusual column type of varbinary(64) (aka 'BLOB'). When it gets to this table, it gives up. It doesn't matter if 'Search columns of all types' is checked or not.

In the log, there's this message:

[ERR][  GRTDispatcher]: worker: task 'Search' has failed with error:.You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'key AS CHAR)  LIKE '%the-droids-youre-looking-for%' , key, '') AS key , IF(CAST(iv AS CH' at line 1
08:46:09 [ERR][SSHTunnelHandler]: Error during data transfer: unable to read, remote end disconnected

How to repeat:
I can't guarantee this would work, but it seems that creating a table with a varbinary(64) column among other tables is all it takes to do it.

Suggested fix:
At a minimum, display an error message in the status field giving the name of the table that caused the search to fail. 

Ideally, skip the bad column/table and continue searching through all the other selected tables. 

Maybe just don't try to search binary data, or do it however the previous version was doing it that worked.

Hello Evan Thompson,

Thank you for the bug report.
I tried to reproduce your issue on windows 10 with workbench 8.0.18 using dummy table with varbinary column but I am not seeing any issues at my end.
Please upgrade to 8.0.18 and report us back if issue persist even in 8.0.18 along with unaltered error log. Thank you.

Regards,
Ashwini Patil