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

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

  Fix bug: FOREIGN KEY ... ON UPDATE/DELETE NO ACTION must check the foreign key constraint, not ignore it. Peter Gulutzan said that NO ACTION should check the constraint as deferred, at the end of the SQL statement, while RESTRICT should check it immediately. Since we do not have defered constraints in InnoDB, this bug fix makes InnoDB to check NO ACTION constraints immediately, like it checks RESTRICT constraints.

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

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

   for the MySQL root user (BUG#2375)

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