into  mysql.com:/usr/home/bar/mysql-5.1.new.ctype

A prerequisite for several fulltext and XML bugs.
MY_CHARSET_HANDLER now has a new function "ctype"
to detect a type of the next character in a string
(i.e. digit, letter, space, punctuation, control, etc),
which now works correctly for both 8bit and multibyte charsets.
Previously only 8bit charsets worked correctly,
while any multibyte character was considered as letter
in multibyte charsets.
Many files:
  Adding new function
Makefile.am:
  Adding build rules for uctypedump,
  a dump tool to create my_uctype.h
  using Unicode Character Database file.
m_ctype.h:
  Adding declaration of my_uni_ctype,
  ctype data for Unicode.
  Adding new member into MY_CHARSET_HANDLER
Makefile.am:
  Adding my_uctype.h into noinst_HEADERS
my_uctype.h, uctypedump.c:
  new files:
  ctype data for unicode,
  and the tool to generate it from 
  a Unicode Character Database file.

into  mysql.com:/home/dlenev/src/mysql-5.1-merges

into  mysql.com:/usr/local/home/marty/MySQL/mysql-5.1-new-wl1892

into  mysql.com:/home/dlenev/src/mysql-5.1-merges

into  mysql.com:/home/dlenev/src/mysql-5.1-merges

into  mysql.com:/home/kostja/mysql/mysql-5.1-merge

When we add new privilege we should update mysql-test/lib/init_db.sql
accordingly.

into  mysql.com:/space/pekka/ndb/version/my51

into  mysql.com:/home/kostja/mysql/mysql-5.1-merge

into  mysql.com:/home/kostja/mysql/mysql-5.1-merge

into  mysql.com:/usr/local/home/marty/MySQL/mysql-5.1-new-wl1892

into  mysql.com:/home/stewart/Documents/MySQL/5.1/tmp_merge

into  mysql.com:/home/stewart/Documents/MySQL/5.1/tmp_merge

fix up test cases.

into  mysql.com:/data0/mysqldev/my/mysql-5.1-new

into  mysql.com:/home/kostja/mysql/mysql-5.1-merge

into  poseidon.ndb.mysql.com:/home/tomas/mysql51

corrected test case

correction

into  mysql.com:/usr/local/home/marty/MySQL/mysql-5.1-new-wl1892

into  mysql.com:/mnt/hda4/home/alik/MySQL/devel/5.1-bug9412-latest

Implement table-level TRIGGER privilege to control access to triggers.
Before this path global SUPER privilege was used for this purpose, that
was the big security problem.

In details, before this patch SUPER privilege was required:
  - for the user at CREATE TRIGGER time to create a new trigger;
  - for the user at DROP TRIGGER time to drop the existing trigger;
  - for the definer at trigger activation time to execute the trigger (if the
    definer loses SUPER privilege, all its triggers become unavailable);

This patch changes the behaviour in the following way:
  - TRIGGER privilege on the subject table for trigger is required:
    - for the user at CREATE TRIGGER time to create a new trigger;
    - for the user at DROP TRIGGER time to drop the existing trigger;
    - for the definer at trigger activation time to execute the trigger
      (if the definer loses TRIGGER privilege on the subject table, all its
      triggers on this table become unavailable).
  - SUPER privilege is still required:
    - for the user at CREATE TRIGGER time to explicitly set the trigger
      definer to the user other than CURRENT_USER().

When the server works with database of the previous version (w/o TRIGGER
privilege), or if the database is being upgraded from the previous versions,
TRIGGER privilege is granted to whose users, who have CREATE privilege.

into  mysql.com:/home/stewart/Documents/MySQL/5.1/wl1359

into  poseidon.ndb.mysql.com:/home/tomas/mysql51