LIMIT clause when filesort had to be used.

In that case LIMIT was applied to filesort of one of the tables, 
although it could not be.

This fix solved problems with LEFT JOIN too...
 

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

  Fix a hang introduced in 4.0.5 in INSERT INTO ... SELECT ... when binlogging is not on

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

Optimized SELECT DISTINCT ... ORDER BY ... LIMIT
Fixed reference to uninitalized variable

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

More tests for multi-table-update & timestamp handling

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

New (simpler) internal timestamp handling.
More debuging to heap tables.
Small cleanups to multi-table-delete
false -> 0 and true -> 1  (We should use TRUE and FALSE)

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

  Make copies of all string-type start/up options in case C-sharp moves them around; remove the need to specify innodb_log_arch_dir in my.cnf, since it has no relevance anyway

into mysql.com:/home/pem/work/mysql-4.0

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

for column,table and named constarints. Now constraint test produces
exactly one line in report, with "yes","no" or syntax only".

add /odbc to server-version if benchmark/crash-me works over odbc

 - reverted some incompatible/non-portable modifications

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

Added CEIL as an alias for CEILING
Cleaned up CHECK constraint handling.
(We don't anymore require braces after CHECK)
Added casting to CHAR.

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

His explanation:

 The socket on which MySQL listens for new connections on a blocking
  socket most of the time but is set to non-blocking during the
  accept() of the new connection.  Due to a bug in the kernel, the new
  socket returned by accept() is a blocking socket but returns the
  O_NONBLOCK flag when queried via fcntl(F_GETFL).  That is, the file
  descriptor and the underlying socket don't agree on the blocking
  mode.

  Since MySQL determines via fcntl(F_GETFL) that the socket is
  non-blocking, it expects the first read() in my_real_read to not
  block, so it doesn't enable the timeout alarm.  However, the read
  does block, and thus there's no timeout alarm.  The thread kill
  (which relies on rescheduling the timeout alarm) also does not work
  as a consequence.

The bug shows itself if you build MySQL with LinuxThreads support
(needed for SMP on FreeBSD).  Issuing a KILL command in MySQL won't be
"noticed" by the "killed" thread until it runs another query--that
makes KILL pretty useless.  And the wait_timeout doesn't work either.

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

 - fixed some typos and wording (merged from 3.23 tree)
 - fixed parsing the correct section in /etc/my.cnf ([mysql_server] ->
   [mysql.server]) as documented in the manual

     - fix setting of niceness level

support-files/mysql.server.sh
     - applied some fixes from 4.0 mysql.server script
     - fix my.cnf parsing

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

  Flush stderr if we run out of memory, so that the error message more probably finds its way to the error log