MySQL Bugs: #12476: Some big5 codes are still missing, as reported and fixed in bug#11266.

Bug #12476	Some big5 codes are still missing, as reported and fixed in bug#11266.
Submitted:	10 Aug 2005 0:56	Modified:	20 Oct 2005 8:18
Reporter:	[ name withheld ]	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Command-line Clients	Severity:	S2 (Serious)
Version:	4.1.13a	OS:	Linux (Linux)
Assigned to:	Alexander Barkov	CPU Architecture:	Any

Description:
The bug#11266 hadn't been fixed in version 4.1.12a and 4.1.13a.
I found big5 code 0xF9DC, 0xF9D7 etc which were listed in the previous (and fixed) bug report are still not accepted by server.
The error message reported by the driver (My/ODBC 3.51.11-2) is --
Illegal mix of collations (ucs2_general_ci,IMPLICIT) and big5_chinese_ci,COERCIBLE) for operation '='
The character set used in client and connection is big5, while in server and database is ucs2.

How to repeat:
In client side, set driver's initial statement to "set character_set_client = big5, character_set_connection = big5, character_set_results = big5;".
In the [mysqld] segment of  \WINNT\my.ini for server side (which is a W2k) set -
default-character-set = ucs2
Then, try to input code 0xF9DC or 0xF9DC from client.

I tested it using MySQL v5.0.12-beta and the SQL code from bug#8603 (quoted in bug#11266) with the following insert statement:

insert into jj values ('&#30849; 0xF9DC; 0xF9D7');

The results after both selects were identical. 

The problem doesn't seem to be present in 5.0

Bug is fixed in 4.1.14 too.

Alexander, probably this is just a duplicate of Bug#9357 closed by you.
Could you please take care of this one as well?

I've been notified by Gerardo Narvaja that bug is fixed in 4.1.14.
But I've tried in mysql-standard-4.1.14-pc-linux-gnu-i686 and found it still exists.

yes, the bugreport is still open (see the Status field)

We checked  all Big5 modifications:
Big5-1984, Big5-eten, cp950, Big5-hkscs, Big5-2003.
All of them (except Big5-1984) map these extra seven characters the same way:

Big5   Unicode
 0x58BB 0xF9D9
 0x5AFA 0xF9DC
 0x6052 0xF9DA
 0x7881 0xF9D6
 0x7CA7 0xF9DB
 0x88CF 0xF9D8
 0x92B9 0xF9D7

In Big5-1984 these codes are undefinite. 
It means there are no conflicts between different Big5.
It is safe to add Unicode mapping for these extra characters.

Sorry, visa versa:

Unicode  Big5
0x58BB 0xF9D9
0x5AFA 0xF9DC
0x6052 0xF9DA
0x7881 0xF9D6
0x7CA7 0xF9DB
0x88CF 0xF9D8
0x92B9 0xF9D7

Big5       Unicode
0xF9D6 0x7881
0xF9D7 0x92B9
0xF9D8 0x88CF
0xF9D9 0x58BB
0xF9DA 0x6052
0xF9DB 0x7CA7
0xF9DC 0x5AFA

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/internals/30719

Fixed in 4.1.16.
Waiting to merge into 5.0.x.

Merged into 5.0.16.

Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html

Additional info:

Documented in 4.1.16 and 5.0.16 changelogs. Closed.