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

into  bodhi.local:/opt/local/work/mysql-5.0-runtime-debug-max

by the patch for Bug#4968

into  mysql.com:/data0/mysqldev/users/tomas/mysql-5.0-build

  Bug #25668    - corrected patch after test failures

into  mysql.com:/data0/mysqldev/users/tomas/mysql-5.0-build

    Bug #25668    ndb: mysqld may core if cluster disconnected
    -- pTrans may be NULL, remove not needed usage of handler::ndb_err

    Fix a compile error:  Macro "DBUG_ENTER" must not follow an executable statement.

into  bodhi.local:/opt/local/work/mysql-5.0-runtime

into  mockturtle.local:/home/dlenev/src/mysql-5.0-bg20390-2

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

into  bodhi.local:/opt/local/work/mysql-5.0-runtime

into  bodhi.local:/opt/local/work/mysql-5.0-runtime

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

into  mockturtle.local:/home/dlenev/src/mysql-5.0-bg20390-2

into  bodhi.local:/opt/local/work/mysql-5.0-4968-to-push

into  bodhi.local:/opt/local/work/mysql-4.1-4968-to-push

of untouched rows in full table scans".

SELECT ... FOR UPDATE/LOCK IN SHARE MODE statements as well as
UPDATE/DELETE statements which were executed using full table
scan were not releasing locks on rows which didn't satisfy
WHERE condition.
This bug surfaced in 5.0 and affected NDB tables. (InnoDB tables
intentionally don't support such unlocking in default mode).

This problem occured because code implementing join didn't call
handler::unlock_row() for rows which didn't satisfy part of condition
attached to this particular table/level of nested loop. So we solve
the problem adding this call.
Note that we already had this call in place in 4.1 but it was lost
(actually not quite correctly placed) when we have introduced nested 
joins.

Also note that additional QA should be requested once this patch is
pushed as interaction between handler::unlock_row() and many recent
MySQL features such as subqueries, unions, views is not tested enough.

into  bodhi.local:/opt/local/work/mysql-5.0-runtime

into  bodhi.local:/opt/local/work/mysql-5.0-runtime

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

into  bodhi.local:/opt/local/work/mysql-4.1-runtime

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

into  mysql.com:/home/gluh/MySQL/Merge/5.0

into  mysql.com:/home/gluh/MySQL/Merge/5.0

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

  Patch from Paul DuBois for better help messages

into  bodhi.local:/opt/local/work/mysql-5.0-runtime

into  bodhi.local:/opt/local/work/mysql-5.0-runtime

into  bodhi.local:/opt/local/work/mysql-4.1-runtime

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

           aliases ignored
When a column reference to a column in JOIN USING is resolved and a new 
Item is created for this column the user defined name was lost.
This fix preserves the alias by setting the name of the new Item to the
original alias.

into  mysql.com:/home/kent/bk/tmp2/mysql-5.0-build