new file

  Fix for the bug 1175: Usernames will not converted to utf8 during connect

  he mysqld server crashes if issued a command select convert(...)
  with a
  non-compiled character set:

  install-test-db did not substiture the path to charsets file, so tests failed with non-default collation incompiled, for example --with-collation=latin1_german1_ci
mysqld.cc:
  better error messaging

into deer.(none):/home/hf/work/mysql-4.1.2046

into teton.kitebird.com:/home/paul/mysql-4.1

into deer.(none):/home/hf/work/mysql-4.1.2181

server)
We didn't perform the check for the error for embedded server

into mysql.com:/home/kostja/mysql/mysql-4.1-prep

There was an error with same function/class member names

broken with recent changes' (attempt 2).
Adding Statement_core is better because:
- set_statement() code is shorter and you don't need to modify it when adding
new members to Statement_core
- a bit faster (you don't have virtual call and don't free_root() twice)
Do that short patch instead in hope that set_statement() will be sooner or
later removed entirely

into teton.kitebird.com:/home/paul/mysql-4.1

into mysql.com:/home/kostja/mysql/mysql-4.1-root

uniform: cli_ + member name.

into serg.mylan:/usr/home/serg/Abk/mysql-4.1

into mysql.com:/home/kostja/mysql/mysql-4.1-root

see comments to the method why

into mysql.com:/my/mysql-4.1

Fixed bug in ORDER BY on a small column (Bug #2147)
Fixed error from pthread_mutex_destroy() when one had wrong errmsg file

  Define macro ULINTPF which can be used in printf statements as the print format of ulint both on Win64 and other platforms

  Check at compilation time on Unix that InnoDB ulint is the same size as void*, and also check it at runtime

A after merge fix for last merge

into mysql.com:/home/kostja/mysql/mysql-4.1-prep_st_hack

into teton.kitebird.com:/home/paul/mysql-4.1

into mysql.com:/my/mysql-4.1

  On 64-bit Windows use InnoDB's own printf function where %lu is converted to %I64u; this eliminates Intel compiler warnings on IA64

All tests pass (client_test included)

into teton.kitebird.com:/home/paul/mysql-4.1

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

"USE db"  affected the character set of further CREATE DATABASEs,
which should have not happened.