MySQL Bugs: #24041: Insensiblity to the charset XML files change

Bug #24041	Insensiblity to the charset XML files change
Submitted:	7 Nov 2006 12:53	Modified:	13 Oct 2008 16:00
Reporter:	[ name withheld ]	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	MySQL Server: Charsets	Severity:	S4 (Feature request)
Version:	5.0, 5.1	OS:	Linux (windows)
Assigned to:		CPU Architecture:	Any

Description:
Anyithing I change on the latin2.xml file or any other, it doesn't matters...

Even I remove all..

I only wanted to edit the true word chars with this method as the Manual writes it.
If I change the collation order, it doesn't make a difference.

(I dropped, recreated, fixed the indexes ; stopped/restarted the server but no reults)

How to repeat:
see above

Many thanks for writing a bug report.

I tested with MySQL 5.1 bzr tree.

It doesn't matter what I change at the xml files of share/mysql/charsets/ also it doesn't matter if I restart server or not. All what I tried has non effect.

It seems the xml files of share/mysql/charsets/ just will be ignored.

It's not a bug. If you do 'SHOW COLLATION' (or select from INFORMATION_SCHEMA.COLLATIONS) you'll see that latin2 collations are compiled in the server - well, in your build anyway. That means that latin2.xml isn't used at all. You need to use the server compiled without latin2 charset (it's a configure switch, your binary probably used --with-extra-charsets=all).