Bug #9011 Erratic behaviour of concat

Description:
CONCAT works in an erratic way in certain situations (see example below)

in short - its output changes according to the situation

How to repeat:
CREATE TABLE `bugreport` (
  `cstbill` mediumint(6) unsigned zerofill default NULL,
  `idcontr` varchar(10) default NULL,
  `trtca` char(2) default NULL,
  `testo` varchar(14) character set utf8 NOT NULL default '',
  `Numb` bigint(1) NOT NULL default '0'
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

INSERT INTO `bugreport` VALUES (000807,'GB52068/04','18','Taratt_analisi',2),(000807,'GB52068/04','05','Taratt_analisi',2),(002902,'GB46212/01','06','Taratt_analisi',2),(052560,'LB301088/4','06','Taratt_analisi',2),(059037,'GB52023/04','18','Taratt_analisi',2);

SELECT DISTINCT  trtca,
 CONCAT(trtca,'- tipo calcolo non forfait per doppio autista')
 FROM bugreport;

>>output:

'18', '18- tipo calcolo non forfait per doppio autista'
'05', '05- tipo calcolo non forfait per doppio autista'
'06', '06- tipo calcolo non forfait per doppio autista'

SELECT DISTINCT  trtca,
 CONCAT('df df ', trtca,'- tipo calcolo non forfait per doppio autista')
 FROM bugreport;

>>output:

'18', 'df df 18- tipo calcolo non forfait per doppio autista'
'05', 'df df 1805- tipo calcolo non forfait per doppio autis'
'06', 'df df 180506- tipo calcolo non forfait per doppio aut'
'06', 'df df 18050606- tipo calcolo non forfait per doppio a'
'18', 'df df 1805060618- tipo calcolo non forfait per doppio'

Suggested fix:
No idea, sorry

Hi! tried  it on mysql 4.1.10 mysql query browser 1.1.5 and was not be able to reproduce. What the version of mysql server?

I'm running Server 4.1.9
mysql> select version();
+-----------+
| version() |
+-----------+
| 4.1.9-nt  |
+-----------+

mysql> \s
--------------
C:\Programmi\MySQL\MySQL Server 4.1\bin\mysql.exe  Ver 14.7 Distrib 4.1.9, for Win95/Win98 (i32)

If you cannot reproduce it, i can try to upgrade to 4.1.10 and see if the thing happens again...
Bye
ema

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".

Uhm, this no-Feddback-so-freeze engine must have some bugs...

Can't repeat with QB 1.16. and server 4.1.11.