Gang, I'm answering my own question here because I was able to solve (part of) the problem in the meantime and want to give you some feedback. Perhaps there is a better or more general solution for this and any further comments from the listmembers are still appreciated.
Problem: Older (pre 4.0.0) clients report an error when accessing a new server running with charset latin1_de enabled. Analysis: latin1_de was introduced with version 4.0.0. However, latin1_de is not a "real charset" but rather a special sort order. This should not affect the client in most (all?) cases. Fix: (This is applied to fix the client host running 3.23.39) 1) added to the [client] section of '.my.cnf' on client host: character-sets-dir = /usr/share/mysql/charsets 2) added one line to /usr/share/mysql/charsets/Index on client host: latin1_de 31 3) created a "fake" configuration file latin1_de.conf : cd /usr/share/mysql/charsets ln -s latin1.conf latin1_de.conf Works like a charm but I consider this a hack. It would mean to hack each and every client machine to make it work. Patching the server daemon would be easier. Developers: Is there a more general way to make old clients happy with new servers running charset latin1_de ??? I think of patching the server to make a fake report to the client pretending latin1 is in use. Question: How does latin1_de affect FULLTEXT matching? No clues to this in the very fine manual (I looked at:) http://www.mysql.com/documentation/mysql/bychapter/\ manual_MySQL_Database_Administration.html#German_character_set Thomas Spahni On Fri, 7 Jun 2002, Thomas Spahni wrote: > ok folks, > > I was digging into my own problem and that's what I found: > > host 'hegel' running 3.23.39 is using character_set latin1 > host 'fidel' running 4.0.1 is using character_set latin1_de > > latin1_de is character set '#31' mentioned in the error message below. > Character set latin_de was introduced with release 4.0.0. From the very > fine manual: > > Changes in release 4.0.0 > * New character set `latin_de' which provides correct German sorting. > > Does this mean that clients before ver 4.0.0 can't access new servers with > correct German sorting??? > > Thomas > > > On Thu, 6 Jun 2002, Thomas Spahni wrote: > > > Dear listmembers, > > > > I've got 2 hosts running Linux: hostnames are 'hegel' and 'fidel' > > > > me@hegel:~>mysqladmin version > > mysqladmin Ver 8.21 Distrib 3.23.39, for pc-linux-gnu on i586 > > > > me@fidel:~>mysqladmin version > > mysqladmin Ver 8.23 Distrib 4.0.1-alpha, for pc-linux-gnu on i686 > > > > When logged in to 'hegel' I can't mysqlshow the databases on 'fidel'. It > > works, but gives an error. > > > > me@fidel:~> mysqlshow -u me -h fidel > > +-----------+ > > | Databases | > > +-----------+ > > | bge | > > | mysql | > > | something | > > | test | > > +-----------+ > > > > me@hegel:~> mysqlshow -u me -h fidel > > mysqlshow: File '/usr/share/mysql/charsets/?.conf' not found (Errcode: 2) > > mysqlshow: Character set '#31' is not a compiled character set and is not > > specified in the '/usr/share/mysql/charsets/Index' file > > +-----------+ > > | Databases | > > +-----------+ > > | bge | > > | mysql | > > | something | > > | test | > > +-----------+ > > > > However, it runs fine the other way round (4.0.1 client, 3.23.39 server): > > > > me@fidel:~> mysqlshow -u me -h hegel > > +--------------+ > > | Databases | > > +--------------+ > > | casino | > > | mitteilungen | > > | mysql | > > | ssl | > > | test | > > +--------------+ > > > > What happens? Any insights what to look for? > > Thomas Spahni --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
