The optimizer needs to evaluate whether predicates are better
 evaluated using an index. IN is one such predicate.
 To qualify an IN predicate must involve a field of the index
 on the left and constant arguments on the right.
 However whether an expression is a constant can be determined only
 by knowing the preceding tables in the join order. 
 Assuming that only IN predicates with expressions on the right that
 are constant for the whole query qualify limits the scope of 
 possible optimizations of the IN predicate (more specifically it
 doesn't allow the "Range checked for each record" optimization for
 such an IN predicate.
 Fixed by not pre-determining the optimizability of the IN predicate
 in the case when all right IN operands are not SQL constant expressions

  The optimizer removes expressions from GROUP BY/DISTINCT
  if they happen to participate in a <expression> = <const>
  predicates of the WHERE clause (the idea being that if
  it's always equal to a constant it can't have multiple 
  values).
  However for predicates where the expression and the 
  constant item are of different result type this is not
  valid (e.g. a string column compared to 0).
  Fixed by additional check of the result types of the 
  expression and the constant and if they differ the 
  expression don't get removed from the group by list.

into  rakia.gmz:/home/kgeorge/mysql/work/B15439-5.0-opt

  Addendum to the fix for bug#15439 : valgrind pb failed

into  mysql.com:/d2/hf/opt/my50-opt

into  mysql.com:/d2/hf/common/my50-common

into  mysql.com:/d2/hf/common/my50-common

into  mysql.com:/d2/hf/common/my50-common

into  mysql.com:/d2/hf/common/my50-common

  Temporary work around for bug#25359

into  mysql.com:/d2/hf/common/my50-common

into  mysql.com:/d2/hf/common/my41-common

into  mysql.com:/d2/hf/common/my50-common

into  mysql.com:/home/kent/bk/main/mysql-5.0

  Corrected spelling in copyright text
Makefile.am:
  Don't update the files from BitKeeper
Many files:
  Removed "MySQL Finland AB & TCX DataKonsult AB" from copyright header
  Adjusted year(s) in copyright header 
Many files:
  Added GPL copyright text
Removed files:
  Docs/Support/colspec-fix.pl
  Docs/Support/docbook-fixup.pl
  Docs/Support/docbook-prefix.pl
  Docs/Support/docbook-split
  Docs/Support/make-docbook
  Docs/Support/make-makefile
  Docs/Support/test-make-manual
  Docs/Support/test-make-manual-de
  Docs/Support/xwf

into  willster.(none):/home/stewart/Documents/MySQL/5.0/ndb-mgm-work

into  poseidon.mysql.com:/home/tomas/mysql-5.0-ndb

into  xiphis.org:/home/antony/work2/mysql-5.0-engines-merge

            repair it

Multi-table delete that is optimized with QUICK_RANGE reports table
corruption.

DELETE statement must not use KEYREAD optimization, and sets
table->no_keyread to 1. This was ignored in QUICK_RANGE optimization.

With this fix QUICK_RANGE optimization honors table->no_keyread
value and does not enable KEYREAD when it is requested.

  Changed header to GPL version 2 only

into  chilla.local:/home/mydev/mysql-5.0-axmrg

into  rakia.gmz:/home/kgeorge/mysql/autopush/B23578-5.0-opt

into  bk-internal.mysql.com:/data0/bk/mysql-5.0-build

into  chilla.local:/home/mydev/mysql-5.0-axmrg

Compiler warnings due to non-matching conversion
specifications in format strings in DBUG_PRINT calls,
due to non-used parameters (in non-debug mode), and
due to seemingly uninitialized variables.

Initialized variables, declared parameters unused, and
casted DBUG_PRINT arguments to get rid of warnings.

Compiler warnings due to non-matching conversion
specifications in format strings in DBUG_PRINT calls.

Fixed DBUG_PRINT format specifiactions.

into  trift2.:/MySQL/M50/push-5.0

into  siva.hindu.god:/usr/home/tim/m/bk/50-build

into  siva.hindu.god:/usr/home/tim/m/bk/50-build