into  rama.(none):/home/jimw/my/mysql-5.0-16881

into  rama.(none):/home/jimw/my/mysql-5.0-19498

into  neptunus.(none):/home/msvensson/mysql/mysql-5.0-maint

 - Since error 1186 is not found among NDB error codes, the message retuned should indicate that.

 - Allow "query" to be used as a prefix for focing a command to be sent to server
 - Add testcases

 - Add test case

into  neptunus.(none):/home/msvensson/mysql/mysql-5.0-maint

  - Add test case(execute perror)
  - Check if strerror has returned NULL and set msg to "Unknown Error" in that case
  - Thanks to Steven Xie for pointing out how to fix. 

into  neptunus.(none):/home/msvensson/mysql/mysql-5.0-maint

into  neptunus.(none):/home/msvensson/mysql/mysql-5.0-maint

into  neptunus.(none):/home/msvensson/mysql/mysql-5.0-maint

 - Add printout in write_footer to tell that mysqldump has completed.
   Ex: -- Dump completed 2006-07-24  8:55:05

into  mysql.com:/usr/home/ram/work/5.0.b19370

into  mysql.com:/usr/home/ram/work/5.0.b19370

into  mysql.com:/usr/home/ram/work/5.0.b8143

into  mysql.com:/usr/home/ram/work/5.0.b19370

into  mysql.com:/usr/home/ram/work/5.0.b10966

  This was only demonstrated by the use of PASSWORD(), it was not related to
  that function at all. The calculation of the size of a field in the results
  of a UNION did not take into account the possible growth of a string field
  when being converted to the aggregated character set.

into  neptunus.(none):/home/msvensson/mysql/mysql-5.0-maint

into  neptunus.(none):/home/msvensson/mysql/mysql-5.0-maint

 - "set @@character_set_database" should be ignored by servers prior to 4.1.1

into  maint1.mysql.com:/data/localhome/msvensson/my50-bug19517

into  maint1.mysql.com:/data/localhome/msvensson/my50-bug19517

into  neptunus.(none):/home/msvensson/mysql/mysql-5.0-maint

"I want to have the current delimiter in the prompt so that I can know at 
a glance which is set."

Add a 'l' format specifier that represents the current statement delimiter.

  When a default of '' was specified for TEXT/BLOB columns, the specification
  was silently ignored. This is presumably to be nice to applications (or
  people) who generate their column definitions in a not-very-clever fashion.

  For clarity, doing this now results in a warning, or an error in strict
  mode.

into  moonbone.local:/work/tmp_merge-5.0-opt-mysql

into  rama.(none):/home/jimw/my/mysql-5.0-17903

into  moonbone.local:/work/tmp_merge-5.0-opt-mysql

into  moonbone.local:/work/tmp_merge-4.1-opt-mysql

into  moonbone.local:/work/tmp_merge-5.0-opt-mysql

into  production.mysql.com:/usersnfs/abotchkov/mysql-5.0.mrg

 - Add a check that length of field to uncompress is longer than 4 bytes.
   This can be dones as the length of uncompressed data is written as 
   first four bytes of field and thus it can't be valid compressed data.

into  mysql.com:/home/hf/work/mysql-5.0.mrg

into  neptunus.(none):/home/msvensson/mysql/mysql-5.0

into  neptunus.(none):/home/msvensson/mysql/mysql-5.0-maint

into  neptunus.(none):/home/msvensson/mysql/mysql-5.0-maint