BUG#2826 "Seconds behind master weirdness"
(sometimes this column of SHOW SLAVE STATUS shows a very big value,
in fact a small negative number casted to ulonglong).
This problem was reported by only one user, but which uses
synchronized time between his servers.
As suggested by the user, to hide this I display max(0, the value)
so that it will be less confusing. For a user, seeing 0 is probably
better than seeing -1 (both tell you that the slave is very close
to the master).

"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