Bug #8395 "o" = "ö" in duplicate checking using german character set

• Submitted: 9 Feb 2005 15:07
• Modified: 9 Feb 2005 15:23
• Reporter: Rolf Bardeli
• Status: Can't repeat
• Category: MySQL Server
• Severity: S3 (Non-critical)
• Version: 4.0
• OS: Windows (Windows 2000)
• CPU Architecture: Any

[9 Feb 2005 15:07] Rolf Bardeli

Description:
Starting mysqld (vers. 4.0, windows) with parameter
--default-character-set=german1

results in the identification of the characters "o" and "ö" in duplicate checking for primary keys.

(Using --default-character-set=latin1_de does not yield a german sort order at all.)

(Sorry if this is already fixed, I could not find it in the bug list nor the feature list of MySQL 4.1.)

How to repeat:
Create a table with one field of type "varchar".
Make it the primary key.
Insert the keys "bos" and "bös".
"bös" will be found to be a duplicate.

[9 Feb 2005 15:08] Rolf Bardeli

Forgot OS and Version

[9 Feb 2005 15:23] MySQL Verification Team

I wasn't able to repeat the behavior reported:

mysql> select version();
+-----------+
| version() |
+-----------+
| 4.0.23-nt |
+-----------+
1 row in set (0.00 sec)

mysql> show variables like "character_set";
+---------------+---------+
| Variable_name | Value   |
+---------------+---------+
| character_set | german1 |
+---------------+---------+
1 row in set (0.00 sec)

mysql> show create table x\G
*************************** 1. row ***************************
       Table: x
Create Table: CREATE TABLE `x` (
  `n` varchar(23) NOT NULL default '',
  PRIMARY KEY  (`n`)
) TYPE=MyISAM
1 row in set (0.00 sec)

mysql> select * from x;
+-----+
| n   |
+-----+
| bos |
| bös |
+-----+
2 rows in set (0.00 sec)

[10 Feb 2005 8:19] Rolf Bardeli

The problem only occurs when inserting values using MySQL control center, so this seems to be a MySQL-CC issue. As MySQL-CC is no longer supported...
rb