into  mysql.com:/usr/home/bar/mysql-5.1.b20086

into  bk-internal.mysql.com:/data0/bk/mysql-5.1-kt

into  dator5.(none):/home/pappa/bug19281

into  bk-internal.mysql.com:/data0/bk/mysql-5.1-kt

into  dator5.(none):/home/pappa/bug19281

into  clam.ndb.mysql.com:/space/pekka/ndb/version/my51-bug18102

Need to flag when a copy is needed to not overwrite a create_info
object connected to the lex structure

into  mysql.com:/usr/home/ram/work/mysql-5.1

into  bk-internal.mysql.com:/data0/bk/mysql-5.1-kt

into  mysql.com:/users/lthalmann/bk/MERGE/mysql-5.1-merge

into  mysql.com:/users/lthalmann/bk/MERGE/mysql-5.1-merge

into  mysql.com:/users/lthalmann/bk/MERGE/mysql-5.0-merge

into  mysql.com:/home/marty/MySQL/mysql-5.1

into  poseidon.ndb.mysql.com:/home/tomas/mysql-5.1-new-ndb

into  mysql.com:/home/marty/MySQL/mysql-5.1

The problem appeared because the same values produced different hash
during INSERT and SELECT for VARCHAR data type.
Fix:
VARCHAR required special treatment to avoid hashing of length bytes
(leftmost one or two bytes) as well as trailing bytes beyond real length,
which could contain garbage. Fix is done by introducing hash() - new method
in the Field class.

into  mysql.com:/home/marty/MySQL/mysql-5.1

into  poseidon.ndb.mysql.com:/home/tomas/mysql-5.1-new-ndb

into  mysql.com:/home/alik/MySQL/devel/5.1-merged

  Corrected test case result

into  dator5.(none):/home/pappa/bug19281

In addition to include "mysql_upgrade" in a RPM, it should also be called
when the RPM is upgraded.

New test cases

into  dator5.(none):/home/pappa/bug16000

into  dator5.(none):/home/pappa/bug19281

into  dator5.(none):/home/pappa/bug19309

into  dator5.(none):/home/pappa/bug19281

into  poseidon.ndb.mysql.com:/home/tomas/mysql-5.1-new-ndb