Minor refactoring to remove compile warnings and possibly fix the
Solaris test failures.

Corrective patch to fix test failures in pushbuild and add assertions
to help debug rpl_extraColmaster test failures.

Changed test to enable easier debugging. 

This patch includes changes to result files for tests issuing BINLOG
queries. The values have changed due to a size difference in the
table map.

Fixing tests and results to work when replicating to fewer columns on
slave than on master. One test that previously should fail, now works,
and some log positions have changed as a result of adding metadata to
the events.

This patch adds the ability to store extra field metadata in the table
map event. This data can include pack_length() or field_lenght() for
fields such as CHAR or VARCHAR enabling developers to add code that
can check for compatibilty between master and slave columns. More 
importantly, the extra field metadata can be used to store data from the
master correctly should a VARCHAR field on the master be <= 255 bytes 
while the same field on the slave is > 255 bytes. 

The patch also includes the needed changes to unpack to ensure that data
which is smaller on the master can be unpacked correctly on the slave.

WL#3915 : (NDB) master's cols > slave

Slave starts accepting and handling rows of master's tables which have more columns.
The most important part of implementation is how to caclulate the amount of bytes to
skip for unknown by slave column.

into  kindahl-laptop.dnsalias.net:/home/bk/b27972-mysql-5.1-rpl

Removing a RESET MASTER inside the test since that will change binlog
positions in such a manner that the dual masters lose track of where
they acually are.

Adding code to filter out slave SQL errors since these are checked by
the tests themselves.

into  dl145h.mysql.com:/data0/mkindahl/mysql-5.1-2team

into  bodhi.(none):/opt/local/work/mysql-5.1-runtime

into  bodhi.(none):/opt/local/work/mysql-5.1-runtime

into  bodhi.(none):/opt/local/work/mysql-5.1-runtime

into  bodhi.(none):/opt/local/work/mysql-5.0-runtime

Changed the default location of the log output to LOG_FILE,
for backward compatibility with MySQL 5.0

into  bodhi.(none):/opt/local/work/mysql-5.1-runtime

into  bodhi.(none):/opt/local/work/mysql-5.1-runtime

into  bodhi.(none):/opt/local/work/mysql-5.0-runtime

into  trift2.:/MySQL/M51/push-5.1

into  mysql.com:/home/kent/bk/tmp3/mysql-5.0-build

into  mysql.com:/home/kent/bk/tmp3/mysql-5.1-build

into  gleb.loc:/home/uchum/work/bk/5.1-opt

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

into  bodhi.(none):/opt/local/work/mysql-5.1-runtime

into  trift-lap.none:/MySQL/M51/push-5.1

into  trift-lap.none:/MySQL/M50/push-5.0

into  trift-lap.none:/MySQL/M51/push-5.1

into  pippilotta.erinye.com:/shared/home/df/mysql/build/mysql-5.1-build

into  pippilotta.erinye.com:/shared/home/df/mysql/build/mysql-5.0-build

into  gleb.loc:/home/uchum/work/bk/5.1-opt

into  gleb.loc:/home/uchum/work/bk/5.1-opt

into  gleb.loc:/home/uchum/work/bk/5.0-opt

into  gleb.loc:/home/uchum/work/bk/5.1-opt

into  pippilotta.erinye.com:/shared/home/df/mysql/build/mysql-5.0.46

The Item_date_typecast::val_int function doesn't reset null_value flag.
This makes all values that follows the first null value to be treated as nulls
and led to a wrong result.

Now the Item_date_typecast::val_int function correctly sets the null_value flag
for both null and non-null values.

into  trift2.:/MySQL/M51/push-5.1