Bug #16815 Please add Russian and Ukranian collations to utf8 charset.
Submitted: 26 Jan 2006 18:12 Modified: 14 Oct 2006 11:57
Reporter: Jaroslav Potapov Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server: Charsets Severity:S4 (Feature request)
Version:5.0.18 OS:Windows (Windows XP)
Assigned to: CPU Architecture:Any

[26 Jan 2006 18:12] Jaroslav Potapov
Description:
Hello!

Please add Russian and Ukranian collations to utf8 charset.
Now it is impossible to sort this languages correctly.

Thank you.

How to repeat:
This feature is not available
[14 Sep 2006 11:57] Valeriy Kravchuk
Thank you for a feature request. Please, send a test case that shows the problem you described. I had not used utf8 on Windows XP, but when I connected from Windows command line window with CP 1251 to MySQL 5.0.26-BK Linux it just works:

openxs@suse:~/dbs/5.0> bin/mysql -uroot test
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 5 to server version: 5.0.26-debug

Type 'help;' or '\h' for help. Type '\c' to clear the buffer.

mysql> set names cp1251;
Query OK, 0 rows affected (0.00 sec)

mysql> drop table ukr3;
Query OK, 0 rows affected (0.00 sec)

mysql> create table ukr3 (c1 char(1) character set 'utf8' collate 'utf8_general_ci') default charset 'utf8';
Query OK, 0 rows affected (0.02 sec)

mysql> insert into ukr3 values('а'),('г'), ('я'), ('ю');
Query OK, 4 rows affected (0.01 sec)
Records: 4  Duplicates: 0  Warnings: 0

mysql> select * from ukr3;
+------+
| c1   |
+------+
| а    |
| г    |
| я    |
| ю    |
+------+
4 rows in set (0.01 sec)

mysql> select * from ukr3 order by c1;
+------+
| c1   |
+------+
| а    |
| г    |
| ю    |
| я    |
+------+
4 rows in set (0.00 sec)
[14 Oct 2006 23:00] Bugs System
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".