into three.local.lan:/home/matthias/Arbeit/mysql-4.1/src

into poseidon.ndb.mysql.com:/home/tomas/mysql-4.1-clean

  removed diskless option for ndb test

into mysql.com:/dbdata/psergey/mysql-4.1-merge-fix

The "insert_update" causes a server crash when using prepared statements

Must clear table->insert_values after completing every prepared statement

(here in client_test.c because we need to check if several PS execution works and the bug shows up with binary protocol only ) 

into mysql.com:/dbdata/psergey/mysql-4.1-merge-fix

 * Backport of safety measures from 5.0: make numeorous replaces:
    s/item->fix_fields()/if (!item->fixed) item->fix_fields()

into mysql.com:/home/jwinstead2/mysql-4.1

 * Added Item_ref::set_properties 
 * Item_ref::Item_ref now expects to get in *item either
     NULL - then fix_fields() will be called later  or 
     ptr to Item it will refer to - then an equivalent of fix_fields() call is performed

into mysql.com:/home/mysql_src/mysql-4.1-clean

  without the PS protocol

into three.local.lan:/home/matthias/Arbeit/mysql-4.1/src

  s/spaces/TAB/

ps-modify1 used the user variables @1, @2, @100 set within ps_query and 
           ps_modify. That architecture was wrong, because the dependence
           of ps_modify1 on ps_query and ps_modify makes the test script
           maintenance and the use of these test cases during bug fixing/
           debugging of single sub test cases very uncomfortable.
Therefore these user variables (@1, @2, @100) are also set within ps-modify1.

The result files of the test cases ps_2myisam, ps_3innodb, ps_4heap, ps_6bdb,
ps_7ndb will be affected by that change and show 3 additional lines, but
nothing else will change.    

  Add running of test suite with --ps-protocol to 'test' target

into mysql.com:/home/jwinstead2/mysql-4.1

into three.local.lan:/home/matthias/Arbeit/mysql-4.1/src

into mysql.com:/dbdata/psergey/mysql-4.1-merge

The problem in 4.1 was the same as in 4.0 - fix_fields() not called for created Item_ref. 
The fix is similar too - initialize Item_refs in ctor (but don't interfere with cases when 
Item_ref is used by subselects). 

into mysql.com:/home/mysql_src/mysql-4.1-clean

into pcgem.rdg.cyberkinetica.com:/usr/home/acurtis/work/wl2274.2

into poseidon.ndb.mysql.com:/home/tomas/mysql-4.1-clean

  quick fix for wrong allocation of size

into sanja.is.com.ua:/home/bell/mysql/bk/mysql-4.1

into poseidon.ndb.mysql.com:/home/tomas/mysql-4.1-clean

changed back to just restricting max meta objects in dict to make sure we can "always" configure ourselves out of unforseen limits

into sanja.is.com.ua:/home/bell/mysql/bk/work-ref-4.1

  UPDATE clause conflicts with SELECT for use of item_list field.
  Alter UPDATE clause to use new lex field update_list
  Tests included

into three.local.lan:/home/matthias/Arbeit/mysql-4.1/src

+ fixed testcase

  dict_load_table(): detect the new table format of MySQL 5.0.3