Bug #49644 init_connect and \0
Submitted: 13 Dec 2009 8:52 Modified: 14 Mar 2010 1:18
Reporter: Sergei Golubchik Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Options Severity:S3 (Non-critical)
Version: OS:Any
Assigned to: CPU Architecture:Any

[13 Dec 2009 8:52] Sergei Golubchik 
Description:
@@init_connect value can contain \0. It is saved and executed correctly. But it's shown truncated.

The same applies to init_slave

How to repeat:
see init_connect.test
after set global init_connect="drop ...
where it's set to a value with \0 inside,
add
select @@global.init_connect;
show variables like 'init_connect';
[13 Dec 2009 8:53] Sergei Golubchik 
fixed in WL#4738
[6 Mar 2010 10:57] Bugs System 
Pushed into 5.5.3-m3 (revid:alik@sun.com-20100306103849-hha31z2enhh7jwt3) (version source revid:vvaintroub@fedora12-20091225154921-x25a5pyw1pxiwobv) (merge vers: 5.5.99) (pib:16)
[14 Mar 2010 1:18] Paul DuBois 
Noted in 5.5.3 changelog.

SHOW VARIABLES did not correctly display string-valued system 
variables that contained \0 characters.