impossible view security".

We should not expose names of tables which are explicitly or implicitly (via
routine or trigger) used by view even if we find that they are missing.
So during building of list of prelocked tables for statement we track which
routines (and therefore tables for these routines) are used from views. We
mark elements of LEX::routines set which correspond to routines used in views
by setting Sroutine_hash_entry::belong_to_view member to point to TABLE_LIST
object for topmost view which uses routine. We propagate this mark to all
routines which are used by this routine and which we add to this set. We also
mark tables used by such routine which we add to the list of tables for
prelocking as belonging to this view.

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

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

CREATE TABLE and PS/SP": make sure that 'typelib' object for
ENUM values and 'Item_string' object for DEFAULT clause are 
created in the statement memory root.

into  mysql.com:/usr/local/home/marty/MySQL/mysql-4.1

into  mysql.com:/usr/home/bar/mysql-5.0.b14146

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

into  mysql.com:/usr/home/pem/bug13729/mysql-5.0

into  mysql.com:/usr/home/pem/bug13729/mysql-5.0

Loose index scan using only second part of multipart index was choosen, which
results in creating wrong keys and endless loop.

get_best_group_min_max() now allows loose index scan for distinct only if used
keyparts forms a prefix of the index.

into moonbone.local:/work/14482-bug-4.1-mysql

crash

resolve_const_item() substitutes item which will evaluate to constant with
equvalent constant item, basing on the item's result type. In this case
subselect was resolved as constant, and resolve_const_item() was substituting
it's result's Item_caches to Item_null. Later Item_cache's function was called
for Item_null object, which caused server crash.

resolve_const_item() now substitutes constants for items with 
result_type == ROW_RESULT only for Item_rows.

into  mysql.com:/usr/local/home/marty/MySQL/mysql-4.1

into  mysql.com:/usr/home/ram/work/5.0.b15047

into  mysql.com:/usr/home/pem/bug13729/mysql-5.0

into  mysql.com:/usr/home/ram/work/5.0.b15047

into  mysql.com:/usr/home/ram/work/5.0.b15047

into  mysql.com:/usr/home/pem/bug13729/mysql-5.0

into  mysql.com:/home/stewart/Documents/MySQL/5.0/bug15215

into  mysql.com:/usr/home/ram/work/5.0.b15047

In the rare circumstance where a mysqld connects to a mgm server, then the
mgm server goes away before a node id can be allocated, it was possible to get
an Error in mgm protocol parser error message.

Larger stack size neaded for open table on x86 64 bit
Fix failing test cases
Deleted symlink from bk

into  regul.home.lan:/mnt/md/bk/mysql-5.0

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

check_stack_overrun().

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

  Don't set thd->is_fatal_error in sql_update for duplicate key errors.

into mysql.com:/M41/mysql-4.1