Bug or Feature: Inserts and Uniqukey with german1 and latin1

Hallo,

I don't know, if this is a bug or a feature...:-) We have some trouble =
with inserts of German Umlaute. Perhaps someone can help us.

We have a table:

CREATE TABLE `search_keywords` (
`id` int(11) NOT NULL auto_increment,
`keyword` varchar(100) NOT NULL default '',
PRIMARY KEY (`id`),
UNIQUE KEY `keyword` (`keyword`),
UNIQUE KEY `ix_search_keywo1` (`id`)
) TYPE=3DMyISAM;

and two insert-statements:

INSERT INTO `search_keywords` VALUES (1,'könnte');
INSERT INTO `search_keywords` VALUES (2,'konnte');

If you run mysqld with the standard charset latin1 you get no error. If =
you run mysqld with the charset german1 you get the error:

ERROR 1062 at line 9: Duplicate entry 'konnte' for key 2

This is reproducible with Version 3.23.37 and 4.0.12 (both binary-tarballs =
from mysql.com).

When we use the charset latin1_de (new in 4.x?) the error does not occur =
and we also have the right sort-order with German Umlaute. Our production-e=
nvironment is still 3.23.37 but we want to migrate to 4.0.12. Is there any =
known problem with latin1_de, or can we migrate smooth from german1 to =
latin1_de? Is german1 obsolete?

Thanks and best regards!
Tom


--
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe: http://lists.mysql.com/bugs?unsub=3Dgcdmb-bugs@m.gmane.org