into  pippilotta.erinye.com:/shared/home/df/mysql/build/mysql-5.0-build-work

into  debian.(none):/M50/push-5.0

into  debian.(none):/M50/push-5.0

                        in a build "--without-server".

Fix for bug#14685

into  debian.(none):/M41/push-4.1

into  debian.(none):/M50/push-5.0

into  pippilotta.erinye.com:/shared/home/df/mysql/build/mysql-5.0-build-work

into  blade09.mysql.com:/tmp/mmj/mysql-5.0-runtime

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

into  weblab.(none):/home/marcsql/TREE/mysql-5.0-rt-merge

into  gshchepa.loc:/home/uchum/work/bk-trees/mysql-5.0-opt-27704

into  debian.(none):/M50/push-5.0

into  gshchepa.loc:/home/uchum/work/bk-trees/mysql-5.0-opt-27704

into  debian.(none):/M50/push-5.0

into  debian.(none):/M50/push-5.0

Support for NULL components was incomplete for row comparison,
fixed.  Added support for abort_on_null at compare_row() like
in 5.x

into  magare.gmz:/home/kgeorge/mysql/autopush/B27786-5.0-opt

This bug was intruduced by the fix for bug#17212 (in 4.1). It is not 
ok to call test_if_skip_sort_order since this function will 
alter the execution plan. By contract it is not ok to call 
test_if_skip_sort_order in this context.

This bug appears only in the case when the optimizer has chosen 
an index for accessing a particular table but finds a covering 
index that enables it to skip ORDER BY. This happens in 
test_if_skip_sort_order.

                 not some other tool (file system checker on Tru64).

Patch originally supplied by Peter O'Gorman, slightly modified by me.

Bug#27739 "build fails on Tru64 due to icheck test in configure"

into  romeo.(none):/home/bk/merge-mysql-5.0

into  romeo.(none):/home/bkroot/mysql-5.0-rpl

When merging views into the enclosing statement
the ORDER BY clause of the view is merged to the
parent's ORDER BY clause.
However when the VIEW is merged into an UNION
branch the ORDER BY should be ignored. 
Use of ORDER BY for individual SELECT statements
implies nothing about the order in which the rows
appear in the final result because UNION by default
produces unordered set of rows.
Fixed by ignoring the ORDER BY clause from the merge
view when expanded in an UNION branch.

into  magare.gmz:/home/kgeorge/mysql/autopush/B27530-5.0-opt

They can drop table after table names list creation and before table opening.
We open non existing table and get ER_NO_SUCH_TABLE error.
In this case we do not store the record into I_S table and clear error.

into  debian.(none):/M50/push-5.0

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

    Hex constants that exceed 32 bit need to be marked "LL" for the compile to work.

into  debian.(none):/M50/push-5.0

conditions when executing an equijoin query with WHERE condition
containing a subquery predicate of the form join_attr NOT IN (SELECT ...).

To resolve a problem of the correct evaluation of the expression
  attr NOT IN (SELECT ...)
an array of guards is created to make it possible to filter out some 
predicates of the EXISTS subquery into which the original subquery 
predicate is transformed, in the cases when a takes the NULL value. 
If attr is defined as a field that cannot be NULL than such an array 
is not needed and is not created. 
However if the field a occurred also an an equijoin predicate t2.a=t1.b
and table t1 is accessed before table t2 then it may happen that the 
the EXISTS subquery is pushed down to the condition evaluated just after
table t1 has been accessed. In this case any occurrence of t2.a is 
substituted for t1.b. When t1.b takes the value of NULL an attempt is 
made to turn on the corresponding guard. This action caused a crash as 
no guard array had been created.

Now the code of Item_in_subselect::set_cond_guard_var checks that the guard
array has been created before setting a guard variable on. Otherwise the
method does nothing. It cannot results in returning a row that could be
rejected as the condition t2.a=t1.b will be checked later anyway.        

into  trift2.:/MySQL/M41/push-4.1

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

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

into  janus.mylan:/usr/home/serg/Abk/mysql-5.0

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

also control the list of man pages installed, so that they correspond better to the binaries.

This is the second version of this fix, including review comments.

into  weblab.(none):/home/marcsql/TREE/mysql-5.0-rt-merge