Bug #20432 mysql client interprets commands in comments
Submitted: 13 Jun 2006 16:38 Modified: 28 Jul 2006 20:08
Reporter: Sergei Golubchik Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Command-line Clients Severity:S3 (Non-critical)
Version:4.1 OS:Any
Assigned to: Tatiana Azundris Nuernberg CPU Architecture:Any

[13 Jun 2006 16:38] Sergei Golubchik 
Description:
in 4.1 mysql command client interprets named commands even in comments, in 4.0 it does not.

How to repeat:
% ( echo '/*' ; echo 'use' ; echo '*/' ) | mysql-4.0/client/mysql
% ( echo '/*' ; echo 'use' ; echo '*/' ) | mysql-4.1/client/mysql
ERROR at line 2: USE must be followed by a database name

same with other commands, e.g. 'status'
[14 Jun 2006 11:17] Bugs System 
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/7624
[13 Jul 2006 7:04] Bugs System 
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/9108
[13 Jul 2006 12:19] Tatiana Azundris Nuernberg 
pushed to 4.1.21-maint
[25 Jul 2006 4:35] Tatiana Azundris Nuernberg 
in 4.1.21
[28 Jul 2006 20:08] Paul DuBois 
Noted in 4.1.21 changelog.

The mysql client did not ignore client-specific commands (such as use
or help) that occurred as the first word on a line within
multiple-line /* ... */ comments.
[6 Sep 2010 11:06] Bugs System 
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/117594

3089 Joerg Bruehe	2010-09-06
      Fix bug#56547
      Bug#20432 is back: mysql client interprets commands in comments
      
      The problem was not caused by a change in the client,
      rather by the tests using the Windows built-in "echo"
      and not the one built bby MySQL.
      This again happened because the binary was missing in the package,
      caused by the wrong macro being used to build it in "cmake".
[6 Sep 2010 11:27] Joerg Bruehe 
Sorry for the above entry, it doesn't belong here
but just to bug#56547.