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

This fixed problem with index reads on character fields with BDB tables. (Bug #2509)

  Fix bug: InnoDB row count and index cardinality estimates wrapped over at 512 million in 32-bit computers

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

reset errors (in thd) before executing the event. Otherwise if an event is ignored
because of replicate-*-table rules (error ER_SLAVE_IGNORED_TABLE) this error code
may remain in thd->net and the next event may pick it. 

  Fix bug #2483 with InnoDB, UNIQUE secondary index, and NULL values in that unique index; with the IS NULL predicate, InnoDB returned only the first matching row, though there can be many

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

into eagle.mysql.r18.ru:/home/vva/work/BUG_2290/mysql-4.0

into eagle.mysql.r18.ru:/home/vva/work/BUG_2290/mysql-4.0

<monty> ramil, in MySQL/MyISAM we should only strip end space, not 'space-like' characters.
<monty> This is according to SQL;  When doing a comparision end space and only end space are ignored.

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

   spec file after the build as RPM has its own option for this

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

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

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

do not write the Execute_load_log_event if there was no Create_file_log_event
(empty file).

manpage) turned out as a major overhaul of all man pages:

 - renamed all *.1 files to *.1.in to act as templates which are being
   processed at build time
 - replaced some hard-coded values with place holder that are being
   replaced with the proper values at build time
 - Updated list of available man pages in the SEE ALSO section and added a
   hint to the manual for more details
 - Added a BUGS section to all pages, referring to the bugs DB
 - Updated some obsolete URLs and mail addresses

The actual content of these man pages should probably be cross-checked for
correctness, though...

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

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

I remove the --old-rpl-compat which produces broken binlogs readable
neither by 4.0 nor by 3.23.
This option is a leftover of the early replication of 4.0.0, when
it was still partly compatible with 3.23.
I explained this to the user in the bug report. 

into mysql.com:/home/kostja/mysql/mysql-4.0-root

into sinisa.nasamreza.org:/mnt/work/mysql-4.0

for re-working project files and enabling remote builds.

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

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

   started via mysqld_safe (BUG#2114) Thanks to Rodrigo Marchant for the
   suggestion