into  mysql.com:/home/mydev/mysql-5.0-bug12166

into  mysql.com:/home/cps/mysql/trees/mysql-5.0-virgin

into  mysql.com:/home/jimw/my/mysql-5.0-clean

into  mysql.com:/home/jimw/my/mysql-5.0-clean

Change in gis test to allow NDB to be able to call generic tests. Fix for Archive so that ALTER TABLE doesn't issue a warning. Also added test case for alter table.

into  zim.(none):/home/brian/mysql/mysql-5.0

into  selena.:H:/MYSQL/src/#14137-mysql-5.0

into  big_geek.:C:/Work/mysql/mysql-5.0

Bug#12166 - Unable to index very large tables
Moved clearing of errors behind the second repair attempt,
but will clear only if no error happened.

No test case. The error can be repeated with little free
space on tmpdir only. I do not know of a way to create this
in a portable way with our test suite.

I did however attach a shell script to the bug report which
can easily be adapted to the situation on the test machine.

into mysql.com:/Users/kent/mysql/bk/mysql-5.0

another macro defined in the Windows header files.

into mysql.com:/Users/kent/mysql/bk/mysql-5.0

into  mysql.com:/home/jimw/my/mysql-5.0-clean

into  zim.(none):/home/brian/mysql/mysql-5.0

into  asksasha.com:/reiser-data/mysql-dev/mysql-5.0-bug12974

into mysql.com:/data0/mysqldev/patg/mysql-5.0-viewfix

mysqldump.result:
  BUG# 12838
      New test results for mysqldump -x on a DB with views
mysqldump.test:
  sqldump.test:
      BUG# 12838
      New test to run mysqldump -x on a DB with views
mysqldump.c:
  BUG# 12838
      Removed/Changed code which created tables to be put into the dump
      (For loading views of views) by creating temp tables and then using
      the CREATE TABLE information in those temp tables. The problem with this
      is that when mysqldump -x is called, it locks all tables, so the
      temp tables could not be created, causing the mysqldump to exit with
      failure. The code was changed to use SHOW FIELDS to get the column
      names and type to build CREATE TABLE text used to create these tables
      that views need in the dump.

into deer.(none):/home/hf/work/mysql-5.0.12267

into deer.(none):/home/hf/work/mysql-5.0.12267

into deer.(none):/home/hf/work/mysql-5.0.12267

into deer.(none):/home/hf/work/mysql-5.0.12267

into  zim.(none):/home/acurtis/mysql-5.0-noraid.2

into  zim.(none):/home/brian/mysql/mysql-5.0

into deer.(none):/home/hf/work/mysql-5.0.12267

into  mysql.com:/usr/home/ram/work/5.0.b14207

into  mysql.com:/home/alik/Documents/AllProgs/MySQL/devel/5.0-bug13037

into  mysql.com:/usr/home/ram/work/5.0.b10303

into  zim.(none):/home/brian/mysql/mysql-5.0

into  mysql.com:/home/timka/mysql/src/5.0-bug-13832

The cause for the bug is that the priorities of all rules/terminals
that process the FROM clause are not fully specified, and the
parser generator produces a parser that doesn't always parse
the FROM clause so that JOINs are left-associative. As a result
the final join tree produced by the parser is incorrect, which
is the cause for subsequent name resolution to fail.

into mysql.com:/Users/kent/mysql/bk/mysql-5.0

  Option to set environment variable MTR_BUILD_THREAD to a small
  number, from what mysql-test-run calculate port numbers that
  will not conflict with other runs with different thread num