MySQL Bugs: #3308: Hang following repeat of SOURCE request with illegal collation

Bug #3308	Hang following repeat of SOURCE request with illegal collation
Submitted:	26 Mar 2004 16:12	Modified:	30 Apr 2004 6:08
Reporter:	Graeme St.Clair	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server: Command-line Clients	Severity:	S3 (Non-critical)
Version:	4.1.1a-alpha-max-debug	OS:	Windows (Windows XP Pro)
Assigned to:		CPU Architecture:	Any

Description:
Command is "source ../Downloads/music/xtra_music_tbl.sql;" where the file contains the following:-

select '<body>','<html>','<table border>','<tr><th>Composer</th><th>Work</th></tr>',
  concat("<tr><td>", composer, "</td><td>", work, "</td></tr>"),
  '</table>','</body>','</html>'
  into outfile 'c:\wombat.htm'
  from music
  where genre like 'Tone%';

I get msg ERROR 1270 (HY000): Illegal mix of collations for operation 'concat'.

I know the cause is that the d-b 'music' has 'DEFAULT CHARACTER SET UTF8' for all fields, and that I should have used 'SET NAMES UTF8' first (and that the generated HTML is not what I want!).

But when I immediately repeat the SOURCE command (by using up-arrow) without modifying the xtra_blah file, mysql hangs and the only escape is to close the command prompt window and start over.

I have repeated the process with simpler commands such as "select concat(composer, "/", work) from music where genre like 'Tone%';" and everything works properly as often as I care to repeat.  However, there is one interesting difference.  With the simple commands, XP beeps as it delivers the error msg; with the complicated one causing the mysql hang, it not only beeps, but a sound is emitted from the speakers (a sort of 'bong' if anyone cares!).

How to repeat:
See above;  if necessary I will ship the offending d-b.

Yes please upload the offended d-b.

Thanks you.

XP zipped version (original was 208K)

Attachment: music.zip (application/x-zip-compressed, text), 50.37 KiB.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".