return incorrect result set for a select SQL request"

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

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

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

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

into  ua141d10.elisa.omakaista.fi:/home/my/bk/mysql-4.1

Changes to Netware specific mysqld_safe.c

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

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

rename sha1_* to mysql_sha1_*

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

 To be uncommented after fixing bug 15805.

into  rurik.mysql.com:/home/igor/dev/mysql-4.1-0

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

into  devsrv-b.mysql.com:/space/magnus/my41-bug15598

into  mysql.com:/home/mydev/mysql-4.1-bug5390

into  mysql.com:/home/mydev/mysql-4.1-bug5390

into  devsrv-b.mysql.com:/space/magnus/my41-bug15598

 - When acl_user->host.hostname is NULL compare it as ""

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

Fixed bug #14274: a query with a having clause containing only set function returned a wrong result set.

Remove wrong fix for Bug#14397 - OPTIMIZE TABLE with an open HANDLER causes a crash
Safety fix for bug #13855 "select distinct with group by caused server crash"

when high concurrency": remove HASH::current_record and make it
an external search parameter, so that it can not be the cause of a 
race condition under high concurrent load.
The bug was in a race condition in table_hash_search,
when column_priv_hash.current_record was overwritten simultaneously
by multiple threads, causing the search for a suitable grant record
to fail.
No test case as the bug is repeatable only under concurrent load.

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

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

   - DROP USER command didn't reload the acl_check_hosts cache causing subsequent 
     connect's via TCP to fail randomly.
   - 4.1 version

When InnoDB compares varchar field in ucs2 with given key using bin collation,
it calls my_strnncollsp_ucs2_bin() to perform comparison.
Because field length was lesser than length of key field should be padded
with trailing spaces in order to get correct result. 
Because  my_strnncollsp_ucs2_bin() was calling my_strnncollp_ucs2_bin(), which
doesn't pads field, wrong comparison result was returned. This results in
wrong result set.

my_strnncollsp_ucs2_bin() now compares fields like my_strnncollsp_ucs2 do,
but using binary collation.

into  mysql.com:/home/mydev/mysql-4.1-bug5390

into  mysql.com:/home/mydev/mysql-4.0-bug5390

  When scan is completed, but lqhkeyreq is outstanding on primary replica and
  starting node dies, scan will not be closed leading to error handling of failed
  node not completing

into  mysql.com:/home/stewart/Documents/MySQL/4.1/cleanup

  Typo in help message.

field.cc:
  BLOB variations have number-in-bytes limit,
  unlike CHAR/VARCHAR which have number-of-characters limits.
  A tinyblob column can store up to 255 bytes.
  In the case of basic Latin letters (which use 1 byte per character)
  we can store up to 255 characters in a tinyblob column.
  When passing an utf8 tinyblob column as an argument into
  a function (e.g. COALESCE) we need to reserve 3*255 bytes.
  I.e. multiply length in bytes to mbcharlen for the character set.
  Although in reality a tinyblob column can never be 3*255 bytes long,
  we need to set max_length to multiply to make fix_length_and_dec()
  of the function-caller (e.g. COALESCE) calculate the correct max_length
  for the column being created.

ctype_utf8.result, ctype_utf8.test:
  Adding test case.

into  mysql.com:/home/stewart/Documents/MySQL/4.1/cleanup