Fix a wrong memset in InnoDB Hot Backup code; the bug probably did not affect anything since we do not assume that the header of a log file is filled with zeros before writing the header info there; the bug found by Felix von Leitner

  Fix a little bug in InnoDB: we looked at the physical size of a stored SQL NULL value from a wrong field in the index; this has probably caused no bugs visible to the user, only caused some extra space usage in some rare cases; we may later backport the fix to 4.0

into mysql.com:/space/my/mysql-4.1-build

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

  "Max" RPM

entry was released before check. Thus empty it is when
size == no of free
This caused a memory leak which inserted a hard limit of
max 64 unique indexes in the cluster.

correctly even with zero month and day" and bug #7515 "from_unixtime(0)
now returns NULL instead of the Epoch" into 4.1 tree.

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

the Epoch". (With after review fixes).

into mysql.com:/home/dlenev/src/mysql-4.1-dtbug

into mysql.com:/dbdata/psergey/mysql-4.1-look

into mysql.com:/M41/mysql-4.1

  Perl version of mysql-test-run
  new file

Clean up the handling of "server" and "client" directories, while still avoiding the double listing of
common directories in 'SUBDIRS' macro ("make distclean" had failed due to that).
Solves bug#7368: "regex make error in 4.1.8"

When we cast datetime value to DATE (TIME) type we should throw away its
time (date) part. This was not done properly if CAST() function was used
in datetime expressions.

  Print a more descriptive error and refuse to start InnoDB if the size of ibdata files is smaller than what is stored in the tablespace header; innodb_force_recovery will override this

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

    compilation failure fixed
    cleanup

into mysql.com:/home/timka/mysql/src/4.1-dbg

The fix checks if the trim string argument is NULL. If so, the standard
mandates that the function result must be also NULL.

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

  Manually merge the latest FOREIGN KEY lock wait + DROP TABLE fix from 4.0

into hundin.mysql.fi:/home/heikki/mysql-4.1

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

- Added a hash to keep track of database-table pairs.
- Specified database-table tables do not get dumped

  Fix the previous bug fix: dropping a table with FOREIGN KEY checks running on it caused a cascade of failed drops while the foreign key check was waiting for a lock

  non-numerical characters (if $VERSION was e.g. "4.1.8a", $MYSQL_VERSION_ID
  resulted in "40108a", which broke the build as MYSQL_VERSION_ID must be
  numerical)

  Merge the two FOREIGN KEY bug fixes from 4.0, and add a TODO comment

into hundin.mysql.fi:/home/heikki/mysql-4.1

  Fix bug: if we dropped a table where an INSERT was waiting for a lock to check a FOREIGN KEY constraint, then an assertion would fail in lock_reset_all_on_table(), since that operation assumes no waiting locks on the table or its records
row0mysql.c:
  Fix bug: InnoDB failed to drop a table in the background drop queue if the table was referenced by a foreign key constraint

into mysql.com:/home/timka/mysql/src/4.1-dbg

Fix for BUG#7377. This fix adds the same implementation for ha_myisammgr::index_type as in version 5.0.

  Return a sensible error code from DISCARD TABLESPACE, if it fails because the table is referenced by a FOREIGN KEY