into  mysql.com:/home/alexi/dev/mysql-5.0-12101

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

into  mysql.com:/home/alexi/mysql-4.1

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

  Fix for fix bug#12922.

Any form of HANDLER statement is forbidden from usage in stored procedures/functions.

Fields of view represented by Item_direct_view_ref. When complex expression
such as if(sum()>...,...) is splited in simpler parts by refs was ignored.
Beside this direct ref doesn't use it's result_field and thus can't store
it's result in tmp table which is needed for sum() ... group.
All this results in reported bug.

Item::split_sum_func2() now converts Item_direct_view_ref to Item_ref to
make fields from view being storable in tmp table.

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

Small tweak for random read performance (we shouldn't always tell the OS that we will be doing a linear scan). 

into  mysql.com:/home/alexi/dev/mysql-5.0-0

into  mysql.com:/home/alexi/dev/mysql-4.1-0

  Post merge changes
sql_yacc.yy:
  Post merge changes
sql_select.cc:
  Fixed bugs #12101, #12102: wrong calculation of not_null_tables()
   for some expressions (post merge changes).
   The function add_key_fields() is modified. There cannot be NOT before
   BETWEEN/IN anymore. Rather Item_func_between/in objects can represent
   now [NOT]BETWEEN/IN expressions.

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

into  mysql.com:/usr/home/bar/mysql-4.1.b12611

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

  use saved view db name in case of view

  Variable character_set_system is selectable now
  More accurate error message results during 
  update of character_set_system and some other read only variables

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

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

into mysql.com:/home/psergey/mysql-5.0-bug12941

into  mysql.com:/usr/home/bar/mysql-4.1.b12829

created item into item->result_field, not *(item->ref)->result_field.

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

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

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

into mysql.com:/Users/eric/bktmp/mysql-5.0

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

into  mysql.com:/home/alexi/dev/mysql-5.0-0

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

into mysql.com:/Users/eric/bktmp/mysql-4.1

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

into mysql.com:/Users/eric/bktmp/mysql-5.0

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

into  mysql.com:/home/alik/Documents/AllProgs/MySQL/devel/5.0-bug12953

OPTIMIZE TABLE statement is forbidden from usage in stored procedures/functions.

NOTE: OPTIMIZE TABLE statement can be useful in stored procedures. The idea is
that the user/administrator can create a stored procedure for admin
tasks (optimizing, backing up, etc). This procedure can be scheduled to run
automatically (by mean of internal cron (WL#1034)). So, once we can make this
statement work, it is worth doing it.