into hegel.local:/home/miguel/dev/mysql-4.0

into hegel.local:/home/miguel/dev/mysql-4.0

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

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

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

from command line did not work.

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

   binary distribution and Server RPM

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

into gw.mysql.r18.ru:/usr/home/ram/work/4.0.b2185

Now one need only SELECT privilege for tables that are only read in
UPDATE statements with many tables. (Bug #2377).

Marked --bdb-no-sync as deprecated
Added --sync-bdb-logs / --disable-sync-bdb-logs as a synonym / alternative.

Give error if locked table is used twice in query. This fixes strange error message when doing LOCK TABLES t1 WRITE; INSERT TABLE t1 SELECT * from t1 (Bug #2296)

"system variable query_prealloc_size can be only global"

increase the size of a signal thread's stack (the old one was too small for the thread to be created on some systems)
bug#2599

thnx Paul.                                             
              
<monty> can you get the above into configure and make Makefile.am patch         
mysql.server.sh with the right values for mysql.server ?                        
<monty> or do you think we should just put the above in mysql.server.sh directly
<ramil> as you want                                                             
<monty> the last is kind of hard to do with variables, so lets put the          
above in mysql.server.sh directly                                               
                                                                  

s/expection/exception

  Change tests so that tables are dropped in an order respecting the FOREIGN KEY constraints

  Change tests so that tables are dropped in an order respecting the FOREIGN KEY constraints

  Change print format of FOREIGN KEY constraints spanning multiple databases to <backquote>databasename<backquote>.<backquote>tablename<backquote>; but when parsing them we must also accept <backquote>databasename.tablename<backquote>, because that was the output format in < 4.0.18

  Change print format of FOREIGN KEY constraints spanning multiple databases to: .; but we when parsing them we must also accept , because that was the output format in < 4.0.18

  Remove redundant code; parse both the database name and the table name in a FOREIGN KEY constraint with quotes in mind
row0mysql.c, ha_innodb.cc, sql_table.cc:
  Return error message Cannot delete or update a parent row... if we try to drop a table which is referenced by a FOREIGN KEY constraint, and the user has not set foreign_key_checks=0

  Cleanup

Moved all range checks for TIMESTAMP value to my_gmt_sec().
Also fixed check of upper boundary of TIMESTAMP range (which 
also now will catch datetime values which are too small for
TIMESTAMP in case if time_t is unsigned).  

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

values for TIMESTAMP columns. The solution is not perfect since
we just silently ignoring default value for first TIMESTAMP 
column and properly reflecting this fact in SHOW CREATE TABLE.
We can't give a warning or simply support standard syntax 
(niladic functions as legal value for default) for first field 
since it is 4.0 tree.

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

Fixed parsing of column names and foreign key constraints in Innobase to handle quoted identifiers and identifiers with space. (Bug #1725)
Fix optimizer tuning bug when first used key part was a constant. (Bug #1679)

when we open the HEAP table for the first time since server restart,
in hp_open(), we set a flag to propagate this info to the handler level
which then writes a DELETE FROM this_heap_table to the binlog.
It is not a perfect solution for the bug, because between the server start and 
the first open of the table, the slave still had old data in his table so
a SELECT on the slave may show wrong content. But if there is a --init-file
to populate the HEAP table on master as startup, then this is a safe fix
(I'll put a note about init-file in the HEAP section of the manual).

(as long as replicate-*-table rules were defined, multi-table DELETE was never
replicated by the slave).

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