In mysqlbinlog, there was a problem with how we escaped the content of a string user variable.
To be perfect, we should have escaped with character_set_client. But this charset is unknown
to mysqlbinlog. So the simplest is to print the string in hex. This is unreadable but
100% safe with any charset (checked with Bar), no more need to bother with character_set_client.

to ha_innodb.cc and ha_innodb.h

into bar.intranet.mysql.r18.ru:/usr/home/bar/mysql-4.1

into mc05.(none):/space2/tomas/mysql-4.1-ndb-test

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

  Fix Bug #4047: remove the improvement ported from 4.0 that made InnoDB to remember the original select_lock_type inside LOCK TABLES

into mc05.(none):/space2/tomas/mysql-4.1-ndb-test

into poseidon.bredbandsbolaget.se:/home/tomas/mysql-4.1-ndb

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

into mysql.com:/home/jonas/src/mysql-4.1-ndb

into mysql.com:/home/jonas/src/mysql-4.1-ndb

into poseidon.bredbandsbolaget.se:/home/tomas/mysql-4.1-ndb

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

into mc05.(none):/space2/tomas/mysql-4.1

into gluh.mysql.r18.ru:/home/gluh/MySQL-BUGS/mysql-4.1

  WL#1160.
  Adding variable-conformant startup options for --default-character-set and --default-collation

  Dump could fail to load because of --default-character-set command line option.
  More safe dump is now produces, --default-character-set doesn't matter.

  Bug #3990  	`--with-charset' ./configure's switch doesn'taffect mysql client library.

into brian-akers-computer.local:/Users/brian/mysql/mysql-4.1

A couple of small changes to ha_example (mainly comments). 

into brian-akers-computer.local:/Users/brian/mysql/mysql-4.1

into brian-akers-computer.local:/Users/brian/mysql/mysql-4.1

No need for mysql_commit, especially after DDL statements.