"replicate-wild-*-table=db.% does not apply to ALTER DATABASE"
apply replicate-* rules to ALTER DATABASE like we already do
for CREATE DATABASE/ DROP DATABASE.

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

update max_used_connections *after* thread_count was increased to take into account the current connection

   in class Statement")

on different systems sprintf("%.3", 1.555499999999999) behaves differently

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

UUID() function

  Remove unused function btr_cur_update_sec_rec_in_place; besides, it was faulty, because even if strings are alphabetically identified, they can have different lengths

(that is, these numbers are converted to doubles by a local OS strtod,
and on different systems they get different values)

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

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

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

into eagle.mysql.r18.ru:/home/vva/work/BUG_2719/mysql-4.1

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

Fixed wrong test of database name (affected optimization of ORDER BY)

into mashka.mysql.fi:/home/my/mysql-4.0

into sinisa.nasamreza.org:/mnt/work/mysql-4.0

"--read-only gives weird error on update".
It is not fixable in 4.0 because it requires modifying
the sql/share/*/errmsg.txt files. So it is fixed in 4.1 like this:
the ER_SKIP_GRANT_TABLES is replaced by a more generic
ER_OPTION_PREVENTS_STATEMENT which can be used both for
"can't do this because of --skip-grant-tables" and
"can't do this because of --read-only" (for this we don't use
ER_CANT_UPDATE_WITH_READLOCK anymore).
So now the message for --read-only is:
"The MySQL server is running with the --read-only option so
cannot execute this statement".