| Bug #70817 | Inconsistent behaviour of NULL with binary strings | ||
|---|---|---|---|
| Submitted: | 5 Nov 2013 10:03 | Modified: | 16 Jan 2014 2:25 |
| Reporter: | Olag Ulga | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Workbench | Severity: | S3 (Non-critical) |
| Version: | 6.0.7 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | NULL binary string | ||
[5 Nov 2013 11:20]
MySQL Verification Team
Thank you for the bug report.
[16 Jan 2014 2:25]
Philip Olson
Fixed as of the upcoming Workbench 6.1.1 release, and here is the changelog entry: MySQL Workbench displayed an empty binary string as NULL. Thank you for the bug report.
Description: its seems that workbench displays an empty binary string as null. How to repeat: select convert('',binary) as b, convert('',binary) is null as n, IFNULL(convert('',binary), 'XXX') as i, convert(convert('',binary),char) as c, convert('x',binary) as x results with server 5.6.14 in: b:<NULL> n:0 i:<NULL> c:'' x:<BLOB> Suggested fix: instead of <NULL> the result of the columns b and i should be displayed as an empty blob-result similar to the column x. With the context menu Open Value in Viewer the content should be an empty text.