Fix for another optimize bug is undone, as the new one handles both cases.
test added

  Backport from 4.0 a bug fix: if unique search from a primary key matched a delete-marked record, InnoDB could return the NEXT record

Quote all table names with backticks.  

into geopard.(none):/storage/bk/mysql-3.23

into mysql.com:/home/walrus/bk/323

into geopard.(none):/storage/bk/mysql-3.23

This only showed up under heavy load.

  Backport from 4.0: Fix corruption of ON DELETE CASCADE in lock wait timeout

into geopard.(none):/storage/bk/mysql-3.23

into mysql.com:/home/walrus/bk/323

into sergbook.mysql.com:/usr/home/serg/Abk/mysql

Will be properly fixed in 4.1 and 5.0

into mysql.com:/home/walrus/bk/323

into geopard.(none):/storage/bk/mysql-3.23

  Backport from 4.0: Fix bug in MySQL-3.23 ORDER BY from a table with no PRIMARY KEY and where the user had added UNIQUE indexes with CREATE INDEX
pars0grm.y:
  Move inclusion of math.h after univ.i also in the .y file; this fix is already done in 4.0

   column with timestamp values with BETWEEN clause

 - Do-compile: fix small (cosmetical, not critical) typo

into mysql.com:/home/nick/mysql/mysql-3.23

into mysql.com:/home/walrus/bk/323

into geopard.(none):/storage/bk/mysql-3.23

  Include univ.i before any system headers to remove a large file compilation failure on AIX