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.b10966

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

 - 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  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  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.

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

The bug is thqt we use some nonstandard assembly codes in our strings
source, and some assemblers don't know what to do with them:  Specifically,
Sun's Solaris assembler and Apple's Darwin assembler balk at them.

This patch, rather than trying to test for properties of the assembler, 
which Autoconf doesn't have any decent facilites for, instead tries to
compile the code in question and disables assembly if it fails.

There's still the problem of unportable assembly, but I'll leave that 
to someone who feels like rewriting and debugging it.

into  dl145k.mysql.com:/data0/mkindahl/bk/mysql-5.0-rpl

into  dl145k.mysql.com:/data0/mkindahl/bk/mysql-4.1-rpl

into  maint1.mysql.com:/data/localhome/cmiller/mysql-4.1

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

    
The problem is that the author used the wrong function to send a warning to the 
user about truncation of data.  push_warning() takes a constant string and 
push_warning_printf() takes a format and variable arguments to fill it.

Since the string we were complaining about contains percent characters, the 
printf() code interprets the "%Y" et c. that the user sends.  That's wrong, and
often causes a crash, especially if the date mentions seconds, "%s".

A alternate fix would be to use  push_warning_printf(..., "%s", warn_buff) .