Renames:
mysql_bind_param      -> mysql_stmt_bind_param
mysql_bind_result     -> mysql_stmt_bind_result
mysql_execute         -> mysql_stmt_execute
mysql_fetch           -> mysql_stmt_fetch
mysql_fetch_column    -> mysql_stmt_fetch_column
mysql_get_metadata    -> mysql_stmt_result_metadata
mysql_param_count     -> mysql_stmt_param_count
mysql_param_result    -> mysql_stmt_param_metadata
mysql_prepare         -> mysql_stmt_prepare
mysql_send_long_data  -> mysql_stmt_send_long_data

client_test.c cleaned up from memory leaks

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

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

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

Two things changed:
1. Repeated queries are only stored once in the history.
2. Multiline queries are stored in a concated format in the history, 
   in addition to pieces. 
(Push approved by serg)

into mysql.com:/home/mysql_src/mysql-4.1

SHOW SLAVE STATUS.

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).

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

reviewed in Saint-Petersbourg (including post-review fixes).

When password was granted with a global grant, then granting 
privileges on database level, without password being specified, 
will temporary (in memory) set password to ''.

into ice.snake.net:/Volumes/ice2/MySQL/bk/mysql-4.1

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

"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