Fix bug when repairing compressed MyISAM files

LOCATE() is now case sensitive


BUILD/compile-alpha-cxx:
  Don't build manager because it fails with linker error on Linux Alpha
Docs/manual.texi:
  Changelog
myisam/mi_check.c:
  Fix bug when repairing compressed MyISAM files
myisam/mi_open.c:
  Fix bug when repairing compressed MyISAM files
myisam/mi_packrec.c:
  Fix bug when repairing compressed MyISAM files
myisam/myisamchk.c:
  Fix bug when repairing compressed MyISAM files
myisam/myisamdef.h:
  Fix bug when repairing compressed MyISAM files
mysql-test/r/func_group.result:
  Fix result for new RND function
mysql-test/r/func_math.result:
  Fix result for new RND function
mysql-test/r/func_str.result:
  test of new locate()
mysql-test/t/func_str.test:
  test of new locate()
sql/item_func.cc:
  LOCATE() is now case sensitive
sql/sql_string.cc:
  LOCATE() is now case sensitive
sql/sql_string.h:
  LOCATE() is now case sensitive

1 files changed, 15 insertions, 3 deletions

diff --git a/Docs/manual.texi b/Docs/manual.texi
index e302b9d4a98..06c313a2020 100644
--- a/Docs/manual.texi
+++ b/Docs/manual.texi
@@ -6953,6 +6953,9 @@ version 4.0;
 
 @itemize @bullet
 @item
+@code{LOCATE()} and @code{INSTR()} are case sensitive if neither
+argument is a binary string.  binary strings.
+@item
 @code{INSERT INTO ... SELECT} had in 3.23 always @code{IGNORE} enabled.
 In 4.0.1 MySQL will stop (and possible rollback) in case of an error if you
 don't specify @code{IGNORE}.
@@ -28621,7 +28624,9 @@ mysql> select LOCATE('xbar', 'foobar');
         -> 0
 @end example
 
-This function is multi-byte safe.
+This function is multi-byte safe.  In MySQL 3.23 this function is case
+insensitive, while in 4.0 it's only case insensitive if either argument is
+a binary string.
 
 @findex LOCATE()
 @item LOCATE(substr,str,pos)
@@ -28634,7 +28639,9 @@ mysql> select LOCATE('bar', 'foobarbar',5);
         -> 7
 @end example
 
-This function is multi-byte safe.
+This function is multi-byte safe.  In MySQL 3.23 this function is case
+insensitive, while in 4.0 it's only case insensitive if either argument is
+a binary string.
 
 @findex INSTR()
 @item INSTR(str,substr)
@@ -28649,7 +28656,9 @@ mysql> select INSTR('xbar', 'foobar');
         -> 0
 @end example
 
-This function is multi-byte safe.
+This function is multi-byte safe.  In MySQL 3.23 this function is case
+insensitive, while in 4.0 it's only case insensitive if either argument is
+a binary string.
 
 @findex LPAD()
 @item LPAD(str,len,padstr)
@@ -45786,6 +45795,9 @@ Our TODO section contains what we plan to have in 4.0. @xref{TODO MySQL 4.0}.
 
 @itemize @bullet
 @item
+@code{LOCATE()} and @code{INSTR()} are case sensitive if neither
+argument is a binary string.  binary strings.
+@item
 Fixed core dump bug in @code{UPDATE ... ORDER BY }.
 @item
 Changed @code{INSERT INTO .. SELECT} to by default stop on errors.