> >> why? Is this a bug or a shortcoming? is it documented anywhere?
> >> Should it be?
> >
> >Ehm, so a SERVER SIDE primary key can stop working
> >if you use a different character set for a CLIENT connection?
>
> Exactly. I'm afraid that conversion from inserted string to index
> key is performed using connection charset with default collation.

So there's two things wrong here?

1) the index key always uses the default collation, despite settings
in the table column

2) a client characterset can influence server STORAGE behaviour


Is this correct?

Martijn Tonies
Database Workbench - tool for InterBase, Firebird, MySQL, NexusDB, Oracle &
MS SQL Server
Upscene Productions
http://www.upscene.com
My thoughts:
http://blog.upscene.com/martijn/
Database development questions? Check the forum!
http://www.databasedevelopmentforum.com