with view-merge algorithm and prepared statements: in case when some
Item_ref pointing to a view column was substituted with a reference 
pointing to the view expression for that column
Item_ref::ref member of the original Item_ref was left pointing to 
not_found_item (0x1).
As we currently perform expression substition part of the view-merge 
algorithm per each execution of a prepared statement or stored procedure, 
we need to preserve original Item_ref objects usable.

into mysql.com:/home/cps/mysql/devel/im-fix-review

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

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

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

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

                a DECLARE ? HANDLER FOR stmt.

  Return false from show_binlog_events() if successful, otherwise stored
  procedures will think it failed.

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

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/my/mysql-4.1

(No really critical errors found, but a few possible wrong results)

into mysql.com:/space/pekka/ndb/version/my50-ndb

into mysql.com:/home/cps/mysql/devel/im-fix-review

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

into mysql.com:/space/pekka/ndb/version/my50-ndb

  fix error code

into mysql.com:/usr/local/home/marty/MySQL/test/mysql-5.0-ndb

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

  Check if node == NULL, which means we are outside tablespace bounds, and print a big fatal error message

into hundin.mysql.fi:/home/heikki/mysql-4.1

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:/usr/home/bar/mysql-4.1-again

  Bug#7997 Add implicit --skip-set-charset when mysqldump from 4.0 server w/ 4.1 client