The flag alias_name_used was not set on for the outer references
in subqueries. It resulted in replacement of any outer reference
resolved against an alias for a full field name when the frm 
representation of a view with a subquery was generated. 
If the subquery and the outer query referenced the same table in
their from lists this replacement effectively changed the meaning
of the view and led to wrong results for selects from this view. 

Modified several functions to ensure setting the right value of
the alias_name_used flag for outer references resolved against
aliases.
 

into  magare.gmz:/home/kgeorge/mysql/autopush/B19342-5.0-opt

into  magare.gmz:/home/kgeorge/mysql/autopush/B19342-5.0-opt

Several problems here :
 1. The conversion to double of an hex string const item
 was not taking into account the unsigned flag.
 
 2. IN was not behaving in the same was way as comparisons
 when performed over an INT/DATE/DATETIME/TIMESTAMP column
 and a constant. The ordinary comparisons in that case 
 convert the constant to an INTEGER value and do int 
 comparisons. Fixed the IN to do the same.
 
 3. IN is not taking into account the unsigned flag when 
 calculating <expr> IN (<int_const1>, <int_const2>, ...).
 Extended the implementation of IN to store and process
 the unsigned flag for its arguments.

into  magare.gmz:/home/kgeorge/mysql/autopush/B26537-5.0-opt

  Post fix for bug#25122.

to return NULL for non-NULL arguments.
This is not the case as it can return NULL
for invalid hexidecimal strings.
Fixed by setting the maybe_null flag.

into  moonbone.local:/mnt/gentoo64/work/25122-bug-5.0-opt-mysql

When INSERT is done over a view the table being inserted into is 
checked to be unique among all views tables. But if the view contains
self-joined table an error will be thrown even if all tables are used under
different aliases.

The unique_table() function now also checks tables' aliases when needed.

in build.

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

  Post fix for bug#23800.

  Post fix for bug#23800.
  Copy the table name of an Item_outer_ref to the conventional memory.

into  moonbone.local:/mnt/gentoo64/work/23800-bug1-5.0-opt-mysql

  Post fix for bug#23800.
  The Item_field constructor now increases the select_n_where_fields counter.
sql_yacc.yy:
  Post fix for bug#23800.
  Take into account fields that might be added by subselects.
sql_lex.h:
  Post fix for bug#23800.
  Added the select_n_where_fields variable to the st_select_lex class.
sql_lex.cc:
  Post fix for bug#23800.
  Initialization of the select_n_where_fields variable.

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

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

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

Suppress compiler warnings from bdb and (for the moment) warnings from ndb

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

Fixed a couple of usage of not initialized warnings (unlikely cases)

into  dl145s.mysql.com:/users/mhansson/mysql/autopush/5.0o-bug24010

it doesn't select.

This bug was fixed along with bug #16861: User defined variable can 
have a wrong value if a tmp table was used.

There the fix consisted of Item_func_set_user_var overloading the method
Item::save_in_field. Consider the query from the test case:


INSERT INTO foo( bar, baz )
SELECT 
  bar,
  @newBaz := 1 + baz
FROM 
  foo
WHERE 
  quux <= 0.1;

Here the assignment expression '@newBaz := 1 + baz' is represented by an 
Item_func_set_user_var. Its member method save_in_field, which writes the 
value of this assignment into the result field, writes the val_xxx() value, 
which is not updated at this point. In the fix introduced by the patch,
the save_in_field method reads the actual variable value instead.

See also comment for 
ChangeSet@1.2368.1.3, 2007-01-09 23:24:56+03:00, evgen@moonbone.local +4 -0
and comment for
Item_func_set_user_var::save_in_field (item_func.cc)

into  moonbone.local:/mnt/gentoo64/work/23800-bug1-5.0-opt-mysql

created for sorting.

Any outer reference in a subquery was represented by an Item_field object.
If the outer select employs a temporary table all such fields should be
replaced with fields from that temporary table in order to point to the 
actual data. This replacement wasn't done and that resulted in a wrong
subquery evaluation and a wrong result of the whole query.

Now any outer field is represented by two objects - Item_field placed in the
outer select and Item_outer_ref in the subquery. Item_field object is
processed as a normal field and the reference to it is saved in the
ref_pointer_array. Thus the Item_outer_ref is always references the correct
field. The original field is substituted for a reference in the
Item_field::fix_outer_field() function.

New function called fix_inner_refs() is added to fix fields referenced from
inner selects and to fix references (Item_ref objects) to these fields.

The new Item_outer_ref class is a descendant of the Item_direct_ref class.
It additionally stores a reference to the original field and designed to
behave more like a field.

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

This also fixes a bug in counting number of rows that are updated when we have many simultanous queries

into  trift2.:/MySQL/M50/push-5.0

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

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

Fixed that --extern works with mysql-test-run.pl
Small trivial cleanups

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

into  trift2.:/MySQL/M50/merge-5.0

into  bk-internal.mysql.com:/data0/bk/mysql-5.0-engines

The declaration of "thr_client_alarm" had got lost, keep it in "mysys/thr_alarm.c".

into  trift2.:/MySQL/M41/merge-4.1