into  mysql.com:/home/mysql_src/mysql-5.1-merge-of-5.0 (not all files are good,
I'll fix; I'll ask some devs to check their part)

into  mysql.com:/home/mysql_src/mysql-5.1

The code was reading a HASH or DYNAMIC_ARRAY which may be uninited (difference from 5.0
is that those vars were always zeroed in 5.0 because were static globals, while they are new'd in 5.1).

into lmy004.:/work/mysql-5.1-bdb_region

into  mysql.com:/home/jimw/my/mysql-5.1-clean

into lmy004.:/work/mysql-5.1-bdb_region

into  selena.:H:/MYSQL/src/#14569-mysql-5.0

into  selena.:H:/MYSQL/bkt/mysql-5.0

my_sopen() on win32 which allows to use FILE_SHARE_DELETE flag to 
allow deleting opened files. my_sopen() implementation is added to
support this functionality.

  Disabled yaSSL support for now

into mysql.com:/Users/kent/mysql/bk/mysql-5.0-release

  Corrected search for 'mysqlimport' executable

- added bdb-cache-parts
- modified bdb-cache-size to support more than 4G
- added bdb-region-size (size of memory pool for storing file names used in transaction)

be the same as the suggested innodb_buffer_pool_size.

we changing current db temporarily and restore it when sp is created. however thd->db
in this case becomes empty string rather than NULL and so all checks of thd->db == NULL 
will be false. So if after this we'll issue create procedure sp2()... without specifying
db it will succeed and create sp with db=NULL, which causes mysqldto crash on 
show procedure status statement.

This patch fixes the problem.

it is added a check of not being empty value. When modifying SP with Admin 
application on win32 it does not pass curent database so sp is stored with
db=null which causes a crash later on show procedure status;

into lmy002.wdf.sap.corp:/home/georg/work/mysql/prod/mysql-5.1

into  mysql.com:/home/timka/mysql/src/5.0-bug-14662

into  mysql.com:/home/timka/mysql/src/5.0-bug-14662

the same column as an aliased and as a non-aliased column.

The problem was that Item_direct_view_ref::eq() was first comparing view columns
by name, and in this case the name of one of them is different since it is aliased.

                  for invalid view
 Permit SHOW CREATE VIEW, SHOW CREATE TABLE, and retrieval of metadata from
 information_schema for invalid views

into  mysql.com:/home/alik/MySQL/devel/5.0-wl2818

into  zim.(none):/home/brian/mysql/show-5.1-new

into  mysql.com:/home/alik/MySQL/devel/5.0-wl2818

into  zim.(none):/home/brian/mysql/mysql-5.0

into  sanja.is.com.ua:/home/bell/mysql/bk/work-bug4-5.0

into  mysql.com:/home/alik/MySQL/devel/5.0-wl2818

checks on trigger activation)