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

  Changed test case comment to be more meaningful

  than in previous 4.1.x

Wrongly applied optimization were adding NOT NULL constraint which results in
rejecting valid rows and reduced result set.

The problem was that add_notnull_conds() while checking subquery were adding
NOT NULL constraint to left joined table, to which, normally, optimization 
don't have to be applied.

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

into  krsna.patg.net:/home/patg/mysql-5.0

WHERE statement"

  Fixed bug #11885.
sql_select.cc:
  Fixed bug #11885.
  Predicates of the forms 'a IN (v)' 'a NOT IN (v)' now
  is replaced by 'a=v' and 'a<>v' at the parsing stage.
sql_yacc.yy:
  Fixed bug #11885.
  Predicates of the forms 'a IN (v)' 'a NOT IN (v)' now 
  is replaced by 'a=v' and 'a<>v' at the parsing stage.

  Fixed bug #11853.
  Corrected the code of the range optimization for
  NOT IN and NOT BETWEEN.
range.test, range.result:
  Fixed bug #11853.

into  mysql.com:/media/sda1/mysql/mysql-5.0-merge

into lmy002.wdf.sap.corp:/home/georg/work/mysql-5.0

into  sanja.is.com.ua:/home/bell/mysql/bk/work-bug6-5.0

Moved mysql_set_character_set function to client.c
Changed function prototype for mysql_set_character_set (as suggested
by Konstantin)

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

disabled if ref is built with a key from the updated table

Problem was in add_not_null_conds() optimization function.
It contains following code:
JOIN_TAB *referred_tab= not_null_item->field->table->reginfo.join_tab;
...
add_cond_and_fix(&referred_tab->select_cond, notnull);
For UPDATE described in bug report referred_tab is 0 and dereferencing it
crashes the server.

into  zim.(none):/home/brian/mysql/foo-5.0

deallocation cleanup

into  mysql.com:/opt/local/work/mysql-4.1-root

into  linux.site:/home/reggie/bk/bug7403

 of system vars at PREPARE time": implement a special Item
to handle system variables. This item substitutes itself with 
a basic constant containing variable value at fix_fields.

  than in previous 4.1.x

Wrongly applied optimization were adding NOT NULL constraint which results in
rejecting valid rows and reduced result set.

The problem was that add_notnull_conds() while checking subquery were adding
NOT NULL constraint to left joined table, to which, normally, optimization 
don't have to be applied.

into  sanja.is.com.ua:/home/bell/mysql/bk/work-bug6-5.0

correct value of CURRENT_USER() in SP with "security definer" (BUG#7291)

into  linux.site:/home/reggie/bk/mysql-5.0

into  mysql.com:/home/pem/work/mysql-5.0

into poseidon.ndb.mysql.com:/home/tomas/mysql-5.0

                  using @@var_name in proc
  Made sure we don't lose the tokenizer state when swapping lex in during SET
  parsing.

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

into poseidon.ndb.mysql.com:/home/tomas/mysql-5.0

into poseidon.ndb.mysql.com:/home/tomas/mysql-5.0

test_client_character_set

into poseidon.ndb.mysql.com:/home/tomas/mysql-5.0