New syntax: CHAR(x USING charset)
  Adding test case.
sql_yacc.yy:
  New syntax: CHAR(x USING charset)
  Adding new parser rule.
item_strfunc.h:
  New syntax: CHAR(x USING charset)
  Adding a new constructor.

into  mysql.com:/usr/home/pem/bug13510/mysql-5.0

into  mysql.com:/usr/home/pem/bug13510/mysql-5.0

into  mysql.com:/usr/home/pem/bug13616/mysql-5.0

into  mysql.com:/usr/home/pem/bug13616/mysql-5.0

into mysql.com:/home/gluh/MySQL/Merge/5.0

into mysql.com:/space/my/mysql-5.0

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

- CHAR() now returns binary string as default
- CHAR(X*65536+Y*256+Z) is now equal to CHAR(X,Y,Z) independent of the character set for CHAR()
- Test for both ETIMEDOUT and ETIME from pthread_cond_timedwait()
  (Some old systems returns ETIME and it's safer to test for both values
   than to try to write a wrapper for each old system)
- Fixed new introduced bug in NOT BETWEEN X and X
- Ensure we call commit_by_xid or rollback_by_xid for all engines, even if one engine has failed
- Use octet2hex() for all conversion of string to hex
- Simplify and optimize code

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

into mysql.com:/space/my/mysql-5.0-build

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

into mysql.com:/space/my/mysql-4.1-build

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

into  mysql.com:/home/jimw/my/mysql-5.0-clean

  Disallow conflicting use of variables named "password" and "names". If such
  a variable is declared, and "SET ... = ..." is used for them, an error is
  returned; the user must resolve the conflict by either using `var` (indicating
  that the local variable is set) or by renaming the variable.
  This is necessary since setting "password" and "names" are treated as special
  cases by the parser.

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

  Fixed compilation problem on FreeBSD,
  after discussion with Jani.
  Doesn't FreeBSD follow the standard?
  

  The fix is needed to perform locking on shared data structures
  This is modification of patch proposed by Leandro Santi
  (see http://webs.sinectis.com.ar/lesanti/misc/mysql-4.0.23a-openssl_locking.patch)

into  mysql.com:/users/lthalmann/bkroot/mysql-5.0

into  mysql.com:/home/svoj/devel/mysql/engine/mysql-5.0

into  mysql.com:/users/lthalmann/bk/mysql-5.0

into deer.(none):/home/hf/work/mysql-4.1.13372

into  mysql.com:/users/lthalmann/bk/mysql-5.0

check_equality() finds equalities among field items. It checks input items
to be Item_fields thus skipping view's fields, which are represented by
Item_direct_view_ref. Because of this index wasn't applied in all cases
it can be.

To fix this problem check_equality() now takes real item of
Item_direct_view_ref, except outer view refs (with depended_from set).