Change optimizer to prefer key lookups before table scan
Change table scans to be done after tables with constrains on scanned table 

Changed connect with timeout to use poll() instead if socket() to avoid problems with many open files

into narttu.mysql.fi:/my/mysql-4.0

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

into narttu.mysql.fi:/my/mysql-4.0

into gluh.mysql.r18.ru:/home/gluh/mysql-4.0.defweek

  In ORDER BY MySQL seems to set the key read flag also in the case where the primary key contains only a prefix of a column - not the whole column; to prevent potential bugs retrieve the whole column if the index contains a prefix of it

This way 3.23.58 slaves will always detect a 4.0.14 master (and stop)
immediately. BUG#198.

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

Safe parenthesis.

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

   problem on Windows/cygwin (BUG#668)

Task ID 894:
Backport default_week_format variable to 4.0

  Track an assertion failure reported on the mailing list June 18th, 2003

 - fixed a typo

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

  Add forgotten mutex_enter()

  Add forgotten mtr_commit()

  Fix error in previous push

  Fix bug: InnoDB could print that it cannot find a clustered index record if an update undo, purge, and a consistent read coincided, in rare cases it might also have returned a wrong row in a query

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

with 'head').
Test fix (this sync_with_master was nonsense).
Now all tests pass in 4.0 in autobuild.

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

More messages.
Testcase for bug 651.

  Cleanup
ha_innodb.cc, data0type.h:
  Make sure non-latin1 users can downgrade from 4.0.14 to an earlier version if they have not created DATA_BLOB column prefix indexes