character_set_results is now the same with character_set_client by default

into mysql.r18.ru:/usr/home/ram/work/4.1.latest

into bar.mysql.r18.ru:/usr/home/bar/mysql-4.1

into eagle.mysql.r18.ru:/home/vva/work/NEW_HELP/4.1.clear

  mysqldump now produces SET NAMES. It can be disabled by --no-set-names

  character_set_connection new variable

character_set_database was added
Code optimization: reuse more code for all character sets variables

into mysql.r18.ru:/usr/home/ram/work/4.1.latest

SELECT CAST(_latin1'string' AS CHAR CHARACTER SET latin2)

  bug #521 fix: ('3'='4')  was true in cp1250_czech_ci

./configure --with-charset=latin1 --with-collation=latin1_danish_ci

  ifdef wrong structure has been fixed

into sanja.is.com.ua:/home/bell/mysql/bk/work-4.1

   compile problems

Fixed new bug when reading field types

into narttu.mysql.fi:/my/mysql-4.1

  Changes according to CHARSET_INFO structure

  utf8 was not marked as compiled

into narttu.mysql.fi:/my/mysql-4.1

into mashka.mysql.fi:/home/my/mysql-4.1-narttu

  Remove accidenatlly committed debug printfs when query cache is used
sql_update.cc, sql_load.cc, sql_insert.cc, sql_delete.cc:
  For the transactional query cache algorithm to work we must invalidate the query cache in INSERT/DELETE/UPDATE before writing to the binlog or calling ha_autocommit_... Note that binlog writing may also call commit. The crucial thing is that the transaction which modified data must not be committed BEFORE the query cache is invalidated.

into mashka.mysql.fi:/home/my/mysql-4.1-narttu

ctype_ucs2 and ctype_ujis were skipped in mistake

  cp1250_czech_ci was displayed even when not compiled-in in mistake.

  Character set in this test results was displayed dispite the fact that the table has the same character set