Bug #20960 Extra HKSCS not support in MySQL 5.0.22
Submitted: 11 Jul 2006 6:27 Modified: 20 Jul 2006 18:53
Reporter: Chu Aaron Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server: Charsets Severity:S4 (Feature request)
Version:v5.0.22 OS:Windows (WinXP Pro)
Assigned to: CPU Architecture:Any

[11 Jul 2006 6:27] Chu Aaron
Description:
The problem is when I try to insert a data with extra HKSCS into a Table with column set with big 5, the error message 1406 popup "Data too long for column 'region' at row 3"

How to repeat:
CREATE TABLE `tx_address2` (
  `id` int(10) unsigned NOT NULL auto_increment,
  `region` char(30) character set big5 default NULL,
  `estate` char(30) character set big5 default NULL,
  `building` char(30) character set big5 default NULL,
  PRIMARY KEY  (`id`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1;

INSERT INTO 'tx_address2' ('region','estate','building') values ('鴨脷洲','利東邨','東安樓')
[11 Jul 2006 7:45] Valeriy Kravchuk
Thank you for a problem report. Please, send the results of

SHOW VARIABLES LIKE 'char%';

from the same mysql command line session.
[11 Jul 2006 8:19] Chu Aaron
character_set_client : big5
character_set_connection : big5
character_set_database : latin1
character_set_filesystem : binary
character_set_results : big 5
character_set_server : later1
character_set_system : utf8
character_set_dir : c:\Program Files\MySQL\MySQL Server 5.0\share\charsets\

Apart from that, when I try to input some Chinese in Query Browser, I notice that the Chinese words I input were displayed just left side of Chinese words?!
[11 Jul 2006 16:39] Valeriy Kravchuk
Looks like a duplicate of known bug #13577, it seems. Please, check. You can not use HKSCS characters now with big5 if some character set conversion is involved.
[12 Jul 2006 3:54] Chu Aaron
I reviewed the bug #13577, there is a suggested fix, too. But would it be better to explain more clear how could I do this?
[20 Jul 2006 18:53] Valeriy Kravchuk
Have you noticed this comment in bug #13577:

"However, please note, character set conversion
to/from other character sets will not work. We cannot
just add mapping for extra HKSCS characters into
Big5 implementation, because Big5 and HKSCS have
different mapping for some characters."

There is nothing good you can do. MySQL have to implement separate character set for this.