The problem was in that the code that analyses the applicability of the
QUICK_GROUP_MIN_MAX access method for DISTINC queries assumed that there
are no duplicate column references in the DISTINCT clause, and it added
non-exiting key parts for the duplicate column references. 

The solution adds a test to check whether the select list already contained
a field with the same name. If such field was already present, then it was
already decided to use its key part for index access. In this such case we
must skip the duplicate field instead of counting it as a new field.

into mysql.com:/home/svoj/devel/mysql/stddev-mysql-5.0

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

Temporary patch to remove some warnings

  Fix wrong spelling

  Make InnoDB-5.0.3 to process log records of 4.1 undo log header create and reuse just like in 4.1; storing XID to the start of the undo log is a separately logged operation; this conforms to Rule 3 of InnoDB redo logging

This bug is also known as WL#1639.

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

(Found during build process)

  Another multi result statement added.
  Note: No test case, as it's not possible to get a deterministic result from this.

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

  Have to thd->set_time() before each substatement execution, to make
  current_time() et al return different times within the same procedure.

into mysql.com:/home/jonas/src/mysql-5.0

into mysql.com:/home/jonas/src/mysql-5.0

into mysql.com:/home/jonas/src/mysql-4.1

into mysql.com:/home/jonas/src/mysql-5.0

into mysql.com:/home/jonas/src/mysql-5.0

into mysql.com:/home/jonas/src/mysql-4.1

  More explicit naming of variables

Previously we only stored the first given error (the error sent to the client)

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

Funny sometimes how things work when in reality you would think it would crash pretty hard :)

  Wait some for all nodes to get connected

mysql-test-run runs with --sleep=10; otherwise GET_LOCK() times out
before being killed so we get 0 instead of NULL. Verified that it
works on our powermacg5 where the test was failing.

into mysql.com:/home/jonas/src/mysql-5.0

into mysql.com:/home/jonas/src/mysql-4.1

  remove dict forwarding
  add api retries on NotMaster
  

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

  The warning sent is by itself ok, the problem was rather why it wasn't
  sent on some other platforms...
  The real problem was that a total_warn_count which was inconsistent with warn_list
  was sent back with send_eof() during SP execution, which in turn cause a protocol
  error in mysqltest.

  Corrected path to my_decimal.cpp

into neptunus.(none):/home/msvensson/mysql/mysql-5.0