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

When we are writing a transaction to the binlog, we log BEGIN/COMMIT with zero error code.
Example: all statements of trans succeeded, connection lost and so implicit rollback:
we don't want ER_NET* errors to be logged in the BEGIN/ROLLBACK events, while statement
events have 0. If there was really a serious error code, it's already in the statement events.

  Adding a prototype for the new function.

--defaults-extra-file option.

into a193-229-222-105.elisa-laajakaista.fi:/home/my/bk/mysql-4.0

my.cnf from the default directories.

  Dump VARCHAR(n) BINARY in HEX if --hex-blob too.

this is important because this 4.0 "Bootstrap" is the one generally used on host "build".

  Backport --hex-blob to 4.0

  After-merge clean-up

  Clean-ups

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

the fact that the transaction log is empty does not mean we're not in a transaction
(it could be BEGIN; SELECT * FOR UPDATE FROM ibtable: then we don't want to commit now, even if
the statement is a MyISAM update).
With a testcase.

into siva.hindu.god:/opt/home/tim/m/40/a

into mysql.com:/home/dlenev/src/mysql-4.0-bg6387

in the source tar-ball for distribution. This is done by using the "DISTFILES" macro
in a new "Docs/Images/Makefile". As the source BK tree does not contain these files,
they are copied from the "mysqldocs" tree at release build time.
This changeset relies on "bk commit - mysqldoc tree (joerg:1.2276)" of today.

into mysql.com:/M40/mysql-4.0

value if server runs in time zone with leap seconds".

Now in my_gmt_sec() function we take into account difference between
our target and estimation in seconds part.

into hundin.mysql.fi:/home/marko/k/mysql-4.0

for Solaris test, and fix if @IS_LINUX@ test in mysqld_safe itself.

  Backport Jan's fix of the LOAD DATA INFILE REPLACE duplicate key error bug (Bug #5835) to 4.0

which is needed for Netware ports.

  Describe innodb_max_purge_lag
  Improve description of innodb_table_locks

  Fix bug #3478: InnoDB's FOREIGN KEY tables treated table and database names as case-insensitive; RENAME TABLE t to T would hang in an endless loop if t had a foreign key constraint defined on it
dict0dict.c:
  Fix bug #3478: InnoDB's FOREIGN KEY tables treated table and database names as case-insensitive; RENAME TABLE t to T would hang in an endless loop if t had a foreign key constraint defined on it; fix also a hang that would occur if one tried in ALTER TABLE or RENAME TABLE to create a foreign key constraint name that collided with another existing name

 - tagged ChangeSet@1.2048.1.2 as "mysql-4.0.22"

close table before next iteration of table proccesing in mysql_admin_table (to allow open next table)

into mysql.com:/space/my/mysql-4.0

  (backports from fixes made in 4.1)

  Updated version of texi2html so that 4.0.22 HTML manual doesn't turn out all goofy.

into mysql.com:/M40/mysql-4.0

without trying to re-run autotools.
(Backport from 4.1.7 for 4.0.22)

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

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

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