into  bk-internal.mysql.com:/data0/bk/mysql-5.0-kt

into  zippy.cornsilk.net:/home/cmiller/work/mysql/mysql-5.0

into  bk-internal.mysql.com:/data0/bk/mysql-5.0-kt

into  may.pils.ru:/home/svoj/devel/mysql/BUG20060/mysql-5.0

Problem described in this bug report affects MyISAM tables only.

Running mysqld --flush instructs mysqld to sync all changes to disk
after each SQL statement. It worked well for INSERT and DELETE
statements, but it did sync for UPDATE only in case if there was
index change (change of colum that has an index). If no updated column
has an index, data wasn't synced to disk.

This fix makes UPDATE statement to sync data to disk even if there is
no index change (that is only data change) and mysqld is run with
--flush option.

  After merge fix

into  sunlight.local:/local_work/leak_fix

into  sunlight.local:/local_work/leak_fix

  Correct memory leak fix

issue an error in case of DECIMAL(M,N) if N > M

into  mysql.com:/home/hf/work/mysql-5.0.clean

  Memory leak fix

into  sunlight.local:/local_work/leak_fix

into  sunlight.local:/local_work/leak_fix

  Memory leak fix

  Moving call that processes select results out of the assert

into  production.mysql.com:/usersnfs/rburnett/mysql-5.0-kt

set properly.  This patch should fix that.

mysqld.cc:
  Call test_if_case_insensitive in all cases so lower_case_file_system always gets set

into  bk-internal.mysql.com:/data0/bk/mysql-5.0-kt

into  bk-internal.mysql.com:/data0/bk/mysql-5.0-kt

now takes mbmaxlen into account when calculating max_length of new field. 

 - Backport patch from 5.0

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

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

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

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

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

into  rama.(none):/home/jimw/my/mysql-5.0-16502

into  rama.(none):/home/jimw/my/mysql-5.0-16502

into  rama.(none):/home/jimw/my/mysql-5.0-16502