MySQL Bugs: #29425: mysql 5.0 scripts no longer echoing comments

Bug #29425	mysql 5.0 scripts no longer echoing comments
Submitted:	28 Jun 2007 18:05	Modified:	29 Jun 2007 11:37
Reporter:	Lucio Chiappetti
Status:	Duplicate
Category:	Client	Severity:	S3 (Non-critical)
Version:	5.0.27	OS:	Linux (SuSE 10)
Assigned to:		Target Version:

Description:
I have a number of database administration scripts of which I redirect stdout to  a file,
which I then feed into an awk script which converts them into an HTML log. The awk script
relies on the fact that mysql comments in a custom form (i.e.
/* @my-own-code@ comment text */ ) are included in stdout together with the mysql
commands and output. 

This has nicely worked since mysql 3.23, and currently with 4.0.21. However it does not
work on 5.0.27. The comments are NO LONGER echoed to stdout !!!
Scripts continue working, but HTML logs cannot be generated any more.

I cannot find any info in user manual, mailing list or forum about a change in comment
handling or a way to repristinate the 4.0 behaviour.

How to repeat:
mysql -vvv -u $user -p$password $dbase << END
? /* this is a comment */
? select now();
END

on 4.0 I get as stdout

--------------
/* this is a comment */                <--- THIS IS MISSING ON 5.0 !!!!
select now()
--------------

+---------------------+
| now() |
+---------------------+
| 2007-06-18 16:14:32 |
+---------------------+
1 row in set (0.01 sec)

Bye

but on 5.0 the first comment line is NOT echoed !

Suggested fix:
If this is due to a change in some configuration option in 5.0 and the pre-4.0 behaviour
can be repristinated using some variable setting or runtime option, please advise AND
WRITE A NOTE IN THE USER MANUAL.

If it is a real bug, please repristinate the old behaviour.

Please do not submit the same bug more than once. An existing bug report already describes
this very problem. Even if you feel that your issue is somewhat different, the resolution
is likely
to be the same. Because of this, we hope you add your comments to the original bug
instead.

Thank you for your interest in MySQL.

Duplicate of bug #26215