MySQL Bugs: #52358: LDML collations issue #2

Bug #52358	LDML collations issue #2 - indexes (cyrillic example)
Submitted:	25 Mar 2010 10:50	Modified:	29 Apr 2010 5:15
Reporter:	Alexandr Evstigneev	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server: Charsets	Severity:	S1 (Critical)
Version:	5.1.30-log	OS:	FreeBSD (7.0. 64bit)
Assigned to:		CPU Architecture:	Any
Tags:	collation, INDEX, LDML

Description:
This bug continues my previous report concerning LDML: http://bugs.mysql.com/bug.php?id=51976

After applying patch, case functions working ok, but other problem appeared. Unique index uses collation in strange way and says duplicate entry error on unknown reason. 

Tested on 5.5.2-m2, no such error.

How to repeat:
1) Apply bugfix for: http://bugs.mysql.com/bug.php?id=51976
2) Add collation utf8_russian_ci using LDML in charsets/Index.xml
Insert this into utf8 character set section:

<collation name="utf8_russian_ci" id="253">
    <rules>
	<reset>\u0415</reset><p>\u0401</p><t>\u0451</t>
    </rules>
</collation>

According the: http://dev.mysql.com/doc/refman/5.1/en/adding-collation-unicode-uca.html

3) In database: 

set names utf8;
drop table  if exists example;

create table example(
id int unsigned not null primary key,
val char(64) not null,
unique (val)
) character set utf8 collate utf8_russian_ci;

insert into example (id, val) values
(1, 'Ульдуар'),
(3, 'алгалон'),
(4, 'видео'),
(5, 'йогг-сарон'),
(10, 'ulduar');

insert into example set val = 'yogg-saron';

Here is the ERROR 1062 (23000): Duplicate entry 'yogg-saron' for key 'val'

Did you recompile the server?

After bugfix? Yes.

Thank you for the feedback.

I can not repeat described behavior with version mysql-5.1-bugfix where fix for another bug exists. Please be sure you run make clean before applying fix and recompiling. Please also install recompiled binaries in separate directory, so we can be sure this is not compiling problem and try this fix again.

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