MySQL Bugs: #58099: Null Bytes (\0) cause truncated query result in SQL Editor

Bug #58099	Null Bytes (\0) cause truncated query result in SQL Editor
Submitted:	9 Nov 2010 22:35	Modified:	6 Jan 2011 10:33
Reporter:	Chris Bednarski	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench: SQL Editor	Severity:	S2 (Serious)
Version:	5.2.29 SE r6756	OS:	Windows (Windows 7 Pro)
Assigned to:	Alfredo Kojima	CPU Architecture:	Any

Description:
Results for queries on rows which contain a null byte character (\0) are truncated at the null byte character when displayed in the SQL Editor results pane.

Any data following the null byte character is not displayed in the Workbench client.  The full data can be viewed when queried via commandline or other client API.

I encountered this using php's object serialization, which uses null byte characters around object members.  See Note at: http://us2.php.net/manual/en/function.serialize.php

How to repeat:
Create table:

CREATE  TABLE IF NOT EXISTS `test`.`table1` (
  `id` INT UNSIGNED NOT NULL AUTO_INCREMENT ,
  `value` VARCHAR(255) NULL ,
  PRIMARY KEY (`id`) ,
  UNIQUE INDEX `id_UNIQUE` (`id` ASC) )
ENGINE = InnoDB;

Insert record:

INSERT INTO test.table1 VALUES(null, 'Test data \0*\0 this will not display');

Select record in Workbench:

SELECT * FROM test.table1;

Result:

'1', 'Test data '

Notice that the result column is truncated after 'Test data', and the part with '\0*\0 this will not display' does not appear in the results column.

Select record from MySQL CLI:

SELECT * FROM test.table1;

+----+-------------------------------------+
| id | value                               |
+----+-------------------------------------+
|  1 | Test data  *  this will not display |
+----+-------------------------------------+

Suggested fix:
Prevent null byte \0 from truncating result output in SQL Editor.

Thank you for the bug report.

Easiest way to repeat is select 'hello\0world'

This has been fixed in backend and Mac, pending Linux and Windows.

The BE fix already fixed the Win part too.

Linux fixed too.

fix confirmed in repository

An entry has been added to the 5.2.31 changelog:

Results for queries on rows which contained a null byte character (\0) were truncated at the null byte character when displayed in the SQL Editor results pane.