Don't close connection to mysql before 'safe_exit', that is done in 'safe_exit' if it decides to exit.

 tFlag => opt_no_create_info
 dFlag => opt_no_data

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

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

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.

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

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

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

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

 - Fix for "bug#16755 Please find a SSL library that is FLOSS-Exception / LGPL copyrighted"

into  orca.ndb.mysql.com:/space_old/pekka/ndb/version/my50

into  anubis.greendragongames.com:/home/greenman/workspace-mysql/mysql/merge-4.1_2_5.0

into  mysql.com:/home/tnurnberg/work/mysql-5.0-21014

mysqldump did not select the correct database before trying to dump
views from it. this resulted in an empty result set, which in turn
startled mysql-dump into a core-dump.  this only happened for views,
not for tables, and was only visible with multiple databases that
weren't by sheer luck in the order mysqldump required, anyway. this
fixes by selecting the correct database before dumping views; it also
catches the empty set-condition if it should occur for other reasons.

into  mysql.com:/home/hf/work/mysql-4.1.16017

into  zippy.(none):/home/cmiller/work/mysql/m41-maint--07AB5

into  zippy.(none):/home/cmiller/work/mysql/m41-maint--07AB5

into  zippy.(none):/home/cmiller/work/mysql/m50--07C2P

into  zippy.(none):/home/cmiller/work/mysql/m50-maint--07C2P

into  zippy.(none):/home/cmiller/work/mysql/m50-maint--07C2P

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

into  anubis.greendragongames.com:/home/greenman/workspace-mysql/mysql/pending/bug-4.1-15977

do not look for client-specific commands while inside a multi-line comment.
we will allow multi-comments pretty much anywhere within SQL-statements,
but client-specific commands (help, use, print, ...) must be the first token
in the input.

  The character set was not being properly initialized in CAST() with
  a type like "CHAR(2) BINARY", which resulted in incorrect results or
  even a crash.