case sensitive collation does not seem to work in 5.5
Posted by: Hans J. Stadler
Date: July 25, 2011 09:35AM

Hi all experts out there.

Under realease 5.0.66 we had created a new case sensitive collation latin1_german1_cs.
Everything worked well.
Key values like 'abc' and 'Abc' where stored in different rows.
Lately, we moved from 5.0.66 to 5.5.
Now our collation doesn't work anymore.
Storing a row with key 'Abc' while key 'abc' already exists yields 'Dupkey'.

Any idea?

p.s.
I installed the latest Release 5.5.14.
Changed collation id in Index.xml to 1024, which is recommended for user-defined collations.
Now it works, but only for MyISAM.
With InnoDB, even the creation of a table with columns of collation 'latin1_german1_cs' yields an error.

The CREATE statement:
USE test2;
CREATE TABLE `tabelle1` (
`feld1` char(30) COLLATE latin1_german1_cs NOT NULL,
`feld2` varchar(255) COLLATE latin1_german1_cs NOT NULL,
PRIMARY KEY (`feld1`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 COLLATE=latin1_german1_cs;

The Message:
ERROR 1005 (HY000): Can't create table 'test2.tabelle1' (errno: 1005)



Edited 1 time(s). Last edit at 07/27/2011 05:54AM by Hans J. Stadler.

Options: ReplyQuote


Subject
Views
Written By
Posted
case sensitive collation does not seem to work in 5.5
4799
July 25, 2011 09:35AM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.