MySQL Bugs: #44804: mysql repeats "no query specified" message continuous

Bug #44804	mysql repeats "no query specified" message continuous
Submitted:	11 May 2009 20:53	Modified:	12 May 2009 21:23
Reporter:	norbert van Nobelen	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Packaging	Severity:	S3 (Non-critical)
Version:	6.0.10-alpha RPM	OS:	Linux (OpenSuse 10.3)
Assigned to:		CPU Architecture:	Any
Tags:	no, query, repeat, specified

Description:
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 9
Server version: 6.0.10-alpha MySQL Community Server (Copyright 2000-2008 MySQL AB, 2008 Sun Microsystems, Inc.  All rights reserved.  Use is su

Type 'help;' or '\h' for help. Type '\c' to clear the buffer.

mysql> show tables;

ERROR:
No query specified

ERROR:
No query specified

ERROR:
No query specified

ERROR:
No query specified

ERROR:
No query specified

ERROR:
No query specified

How to repeat:
Installed RPM 6.0.10-alpha:
MySQL-client-6.0.10-0.glibc23.x86_64.rpm
MySQL-devel-6.0.10-0.glibc23.x86_64.rpm
MySQL-server-6.0.10-0.glibc23.x86_64.rpm
MySQL-shared-6.0.10-0.glibc23.x86_64.rpm
MySQL-shared-compat-6.0.10-0.glibc23.x86_64.rpm
MySQL-test-6.0.10-0.glibc23.x86_64.rpm

Login into mysql
After every ; the message repeats

Thank you for the report.

Verified as described.

Bug is only repeatable with RPM packages.

Workaround: use tar.gz package.

I extracted the RPM like this:

rpm2cpio MySQL-client-6.0.10-0.glibc23.x86_64.rpm | cpio -idmv

Then I ran:

usr/bin/mysql -h ... -u ...

Welcome to the MySQL monitor.  Commands end with ; or \g.
...
mysql> show tables;
Empty set (0.00 sec)

mysql>

In other words, the binary in the packages itself works fine on RHEL 5 and SLES 11. I don't currently have access to OpenSuSE 10.3.

On which platform(s) was this bug verified?

Ok, I will install the tar instead.
Close the bug?

No, please don't close it. I would very much prefer to find the problem first. It may not be a client issue.

Okay, I found it. This bug is actually fixed in the MySQL 6.0.11 code base.

As a temporary workaround, you might consider using the tarball exclusively, or even just replacing the mysqld binary from the RPM-based installation with one from a tarball. The problem is caused by the overlong version comment of the server included in the RPM packages. In future MySQL 6.0 releases, the client will be able to handle these longer comments.

This bug also affects 5.4. :(