Backport option description change from 5.1 to 5.0.

into  perch.ndb.mysql.com:/home/jonas/src/mysql-5.0

into  perch.ndb.mysql.com:/home/jonas/src/50-work

    ndb crash if trigger record get to big, fix incorrect max size of trigger record

into  perch.ndb.mysql.com:/home/jonas/src/mysql-5.0

  ndb crash if trigger record get to big, fix incorrect max size of trigger record

into  shellback.(none):/home/msvensson/mysql/mysql-5.0

into  mysql.com:/usr_rh9/home/elkin.rh9/MySQL/FIXES/5.0.20-bug15101-sysdate

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

into  mysql.com:/home/mydev/mysql-5.0-bug14980

Now DEFINER-clause in stored routines is expected to appear
in 5.0.20 release, not in 5.0.19. as it was supposed before.

into mysql.com:/M50/merge-5.0

Fixes bug#15861

into  mysql.com:/usr_rh9/home/elkin.rh9/MySQL/FIXES/5.0.20-bug15101-sysdate

   After the ChangeSet 1.1892.20.1 2005/08/24 (Bug #12562) SYSDATE() is not an alias
   of NOW() and is unsafe for replication.
   `SYSDATE()' backward compatible aliasing clashes with the idea #12562 
   fix. To make it safe-replicatable we have to either use RBR or to restore
   the pre-5.0 style.
   --sysdate-is-now command line flag was introduced to provide backward compatibility.

into  mysql.com:/home/mydev/mysql-5.0-bug14980

For "count(*) while index_column = value" an index read
is done. It consists of an index scan and retrieval of
each key.

For efficiency reasons the index scan stores the key in
the special buffer 'lastkey2' once only. At the first 
iteration it notes this fact with the flag 
HA_STATE_RNEXT_SAME in 'info->update'.

For efficiency reasons, the key retrieval for blobs
does not allocate a new buffer, but uses 'lastkey2'...

Now I clear the HA_STATE_RNEXT_SAME flag whenever the 
buffer has been polluted. In this case, the index scan
copies the key value again (and sets the flag again).

w/o definer if --skip-grant-tables specified.
  
The previous patch does not allow to specify empty host name in
DEFINER-clause explicitly.

produce wrong data

By default Item_sp_func::val_str() returns string from it's result_field 
internal buffer. When grouping is present Item_copy_string is used to 
store SP function result, but it doesn't additionally buffer the result.
When the next record is read, internal buffer is overwritten, due to
this Item_copy_string::val_str() will have wrong data. Thus producing
weird query result.

The Item_func_sp::val_str() now makes a copy of returned value to prevent
occasional corruption.

into  neptunus.(none):/home/msvensson/mysql/mysql-5.0

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

This patch does 1) fix my build breakage  2) Complete the removal of all symbols which could clash with another parser. 

into  neptunus.(none):/home/msvensson/mysql/mysql-5.0

  Fix typos.

into  neptunus.(none):/home/msvensson/mysql/mysql-5.0

Makes you wonder what I am up to, doesn't?

into  neptunus.(none):/home/msvensson/mysql/mysql-5.0

into  neptunus.(none):/home/msvensson/mysql/mysql-5.0

into  neptunus.(none):/home/msvensson/mysql/mysql-5.0

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

 -Add test case
Move testcase that needs innodb from sp.test => sp_trans.test 

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

into  perch.ndb.mysql.com:/home/jonas/src/mysql-5.0

  (not possible from SQL in 4.1 & 5.0)