Actually it is not a bug but right behavior observed as pefomance 
degradation after we have forced Item_field::fix_fields() to 
re-execute each time when we are executing prep stmt.

This patch implements small optimization which heals this bad 
behavior. We are caching field position in TABLE::field array in
Item's member and are using this position for speeding up field
lookups in fix_fields() in case of its re-execution.

into serg.mylan:/usr/home/serg/Abk/mysql-4.1

is specified, the default is SESSION.

  Conditional compilation

  Don't dump default implicit weights

into serg.mylan:/usr/home/serg/Abk/mysql-4.1

dropping of tables added to the testcase

Bug#1428

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

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

into greg-laptop.:C:/cygwin/bk/mysql-4.1

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

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

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

some db comparison code cleupup
removed compiler warnings

  new file

  Delete: mysys/uca-dump.c

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

into serg.mylan:/usr/home/serg/Abk/mysql-4.1

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

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

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

Portability fixes

  Correct previous bk commit comment about page splits: actually, in versions < 4.0.19 space utilization is very poor if 1500 - 8000 byte rows are inserted in the order of the primary key

  Improve space utilization if we have 3 kB - 8 kB rows to insert in the order of the primary key
btr0cur.c:
  Fix bug: The row count and key cardinality estimate was grossly too small if each clustered index page only contained one record

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

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

   "-apple-darwin7.3.0-powerpc") - this is needed as we now will provide
   Mac OS X 10.2.x and Mac OS X 10.3.x PGKs (and it's more in line of
   how we name all other packages)