try to find most suitable table, to avouid pickup table with too low locking mode or occupy table with write mode for select when it will be need for update later
(BUG#9597)

into  mysql.com:/opt/local/work/mysql-5.0-root

into  mysql.com:/opt/local/work/mysql-5.0-root

into  mysql.com:/opt/local/work/mysql-4.1-11458

into  mysql.com:/opt/local/work/mysql-5.0-root

into  mysql.com:/opt/local/work/mysql-4.1-11458

data": remove the fix for another bug (8807) that
added OUTER_REF_TABLE_BIT to all subqueries that used a placeholder
to prevent their evaluation at prepare. As this bit hanged in 
Item_subselect::used_tables_cache for ever, a constant subquery with
a placeholder was never evaluated as such, which caused wrong 
choice of the execution plan for the statement.
- to fix Bug#8807 backport a better fix from 5.0
- post-review fixes.

  mysql_update(): Call handler::unlock_row()
  also in the first while loop.
  This patch is from Heikki,
  and it was approved by Sergei Golubchik.

into  mysql.com:/home/dlenev/src/mysql-5.0-mysqlproc

indirectly using non-cached function".

into mysql.com:/home/bk/bXXX-mysql-5.0

end of the test, causing subsequent tests to fail.

into  mysql.com:/home/dlenev/src/mysql-5.0-mysqlproc

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

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

of stored routines definitions even if we already have some tables open and
locked. To avoid deadlocks in this case we have to put certain restrictions
on locking of mysql.proc table.

This allows to use stored routines safely under LOCK TABLES without explicitly
mentioning mysql.proc in the list of locked tables. It also fixes bug #11554
"Server crashes on statement indirectly using non-cached function".

  added out of range handling

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

into moonbone.local:/work/mysql-5.0-bug-11709

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

  Fix for test case for bug#11709

When searching column to sort on, item was compared to field under view
column, but not the column itself. Because names of view column and underlaid
field may differ, it leads to possibly choosing wrong column for sorting on.

This patch makes Item_direct_view_ref::eq(Item *item,...) compare
item's name with it's own name proir to comparing to *ref item.

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

into igor-inspiron.creware.com:/home/igor/mysql-5.0

into mysql.com:/M50/mysql-5.0

  Expanded the test case for bug #6120 to cover
  DROP VIEW / CREATE VIEW scenario.
sql_view.cc:
  Expanded the fix for bug #6120 to cover the case of
  DROP VIEW / CREATE_VIEW.

into igor-inspiron.creware.com:/home/igor/mysql-5.0

into mysql.com:/M50/mysql-5.0

into mysql.com:/home/psergey/mysql-5.0-bug11821-merge