------------------------------------------------------------
revno: 2589
author: df@sun.com
committer: MySQL Build Team <build@mysql.com>
branch nick: mysql-5.0.81-release
timestamp: Thu 2009-04-16 13:30:52 +0200
message:
  adjust version number
------------------------------------------------------------
revno: 2588
tags: clone-5.0.81-build
committer: Chad MILLER <chad@mysql.com>
branch nick: 5.0-community
timestamp: Tue 2009-04-14 13:20:13 -0400
message:
  Merge 5.0.80 release and 5.0 community.  Version left at 5.0.80.
    ------------------------------------------------------------
    revno: 2559.157.58
    committer: MySQL Build Team <build@mysql.com>
    branch nick: mysql-5.0.80-release
    timestamp: Mon 2009-04-13 21:06:24 +0200
    message:
      Merge in missing changes from mysql-5.0.79-release
        ------------------------------------------------------------
        revno: 2559.225.2
        tags: mysql-5.0.79
        author: kent.boortz@sun.com
        committer: MySQL Build Team <build@mysql.com>
        branch nick: mysql-5.0.79-release
        timestamp: Mon 2009-03-09 22:16:24 +0100
        message:
          Back patched libedit portability changes from 5.1.32
        ------------------------------------------------------------
        revno: 2559.225.1
        author: Patrick.Crews@Sun.COM
        committer: MySQL Build Team <build@mysql.com>
        branch nick: mysql-5.0.79-release
        timestamp: Mon 2009-03-09 22:14:52 +0100
        message:
          Test cases adjusted, precision changes "error Corrupt" changed to "status  Operation failed"
    ------------------------------------------------------------
    revno: 2559.157.57
    tags: clone-5.0.80-build
    committer: Georgi Kodinov <joro@sun.com>
    branch nick: fix-5.0-pe-stage
    timestamp: Fri 2009-03-27 16:29:56 +0200
    message:
      tree name changed
    ------------------------------------------------------------
    revno: 2559.157.56
    committer: Georgi Kodinov <joro@sun.com>
    branch nick: fix-5.0-pe-stage
    timestamp: Fri 2009-03-27 16:25:16 +0200
    message:
      fixed a compilation warning
    ------------------------------------------------------------
    revno: 2559.157.55
    committer: Ramil Kalimullin <ramil@mysql.com>
    branch nick: mysql-5.0-pe-stage
    timestamp: Wed 2009-03-25 21:50:42 +0400
    message:
      Auto-merge
        ------------------------------------------------------------
        revno: 2559.224.1
        committer: Tatiana A. Nurnberg <azundris@mysql.com>
        branch nick: mysql-5.0-pe-stage
        timestamp: Wed 2009-03-25 17:10:27 +0100
        message:
          Bug#43748: crash when non-super user tries to kill the replication threads
          
          Fine-tuning. Broke out comparison into method by
          suggestion of Davi. Clarified comments. Reverting
          test-case which I find too brittle; proper test
          case in 5.1+.
    ------------------------------------------------------------
    revno: 2559.157.54
    committer: Ramil Kalimullin <ramil@mysql.com>
    branch nick: mysql-5.0-pe-stage
    timestamp: Wed 2009-03-25 20:48:10 +0400
    message:
      Fix for bug#35383: binlog playback and replication breaks
      due to name_const substitution
      
      Problem:
      "In general, statements executed within a stored procedure
      are written to the binary log using the same rules that
      would apply were the statements to be executed in standalone
      fashion. Some special care is taken when logging procedure
      statements because statement execution within procedures
      is not quite the same as in non-procedure context".
      
      For example, each reference to a local variable in SP's
      statements is replaced by NAME_CONST(var_name, var_value).
      Queries like
      "CREATE TABLE ... SELECT FUNC(local_var ..."
      are logged as
      "CREATE TABLE ... SELECT FUNC(NAME_CONST("local_var", var_value) ..."
      that leads to differrent field names and
      might result in "Incorrect column name" if var_value is long enough.
      
      Fix: in 5.x we'll issue a warning in such a case.
      In 6.0 we should get rid of NAME_CONST().
      
      Note: this issue and change should be described in the documentation
      ("Binary Logging of Stored Programs").
    ------------------------------------------------------------
    revno: 2559.157.53
    committer: Georgi Kodinov <joro@sun.com>
    branch nick: B43748-5.0-pe-stage
    timestamp: Wed 2009-03-25 15:37:21 +0200
    message:
      Bug#43748: crash when non-super user tries to kill the replication threads
      
      (Pushing for Azundris)
            
      We allow security-contexts with NULL users (for
      system-threads and for unauthenticated users).
      If a non-SUPER-user tried to KILL such a thread,
      we tried to compare the user-fields to see whether
      they owned that thread. Comparing against NULL was
      not a good idea.
            
      If KILLer does not have SUPER-privilege, we
      specifically check whether both KILLer and KILLee
      have a non-NULL user before testing for string-
      equality. If either is NULL, we reject the KILL.
    ------------------------------------------------------------
    revno: 2559.157.52
    committer: Leonard Zhou <zhou.li@sun.com>
    branch nick: bugs
    timestamp: Wed 2009-03-25 16:19:09 +0800
    message:
      Fix the test case error in PB.
    ------------------------------------------------------------
    revno: 2559.157.51
    committer: Alexey Kopytov <Alexey.Kopytov@sun.com>
    branch nick: mysql-5.0-bugteam
    timestamp: Tue 2009-03-24 23:50:59 +0300
    message:
      Automerge.
        ------------------------------------------------------------
        revno: 2559.221.3
        committer: Alexey Kopytov <Alexey.Kopytov@sun.com>
        branch nick: my50-bug41486
        timestamp: Tue 2009-03-24 23:44:38 +0300
        message:
          Fix for bug #43801: mysql.test takes too long, fails due to 
                              expired timeout on debx86-b in PB 
          
          Moved the resource-intensive test case for bug #41486 into 
          a separate test file to reduce execution time for mysql.test. 
    ------------------------------------------------------------
    revno: 2559.157.50
    committer: Leonard Zhou <leonard@mysql.com>
    branch nick: bug41719
    timestamp: Tue 2009-03-24 15:29:04 +0800
    message:
      Merge
        ------------------------------------------------------------
        revno: 2559.210.4
        committer: Matthias Leich <Matthias.Leich@sun.com>
        branch nick: mysql-5.0-bugteam-lockmulti-push
        timestamp: Mon 2009-03-23 21:19:41 +0100
        message:
          Merge of fixes into actual tree
            ------------------------------------------------------------
            revno: 2559.223.1
            committer: Matthias Leich <Matthias.Leich@sun.com>
            branch nick: mysql-5.0-bugteam-lockmulti
            timestamp: Mon 2009-03-23 15:22:31 +0100
            message:
              Fix for Bug#43015 and Bug#43065
              
                 Details for Bug#43015 main.lock_multi: Weak code (sleeps etc.)
                 -------------------------------------------------------------
                 - The fix for bug 42003 already removed a lot of the weaknesses mentioned.
                 - Tests showed that there are unfortunately no improvements of this tests
                   in MySQL 5.1 which could be ported back to 5.0.
                 - Remove a superfluous "--sleep 1" around line 195
              
                 Details for Bug#43065 main.lock_multi: This test is too big if the disk is slow
                 -------------------------------------------------------------------------------
                 - move the subtests for the bugs 38499 and 36691 into separate scripts
                 - runtime under excessive parallel I/O load after applying the fix
                   lock_multi           [ pass ]          22887
                   lock_multi_bug38499  [ pass ]         536926
                   lock_multi_bug38691  [ pass ]         258498
        ------------------------------------------------------------
        revno: 2559.210.3
        committer: Sergey Glukhov <Sergey.Glukhov@sun.com>
        branch nick: mysql-5.0-bugteam
        timestamp: Mon 2009-03-23 16:51:39 +0400
        message:
          remove compiler warnings
        ------------------------------------------------------------
        revno: 2559.210.2
        committer: Tatiana A. Nurnberg <azundris@mysql.com>
        branch nick: mysql-5.0-bugteam
        timestamp: Mon 2009-03-23 05:21:45 +0100
        message:
          auto-merge
            ------------------------------------------------------------
            revno: 2559.211.5
            committer: Narayanan V <v.narayanan@sun.com>
            branch nick: mysql-5.0-bugteam-42937-2
            timestamp: Fri 2009-03-20 11:42:55 +0530
            message:
              merging with mysql-5.0-bugteam
                ------------------------------------------------------------
                revno: 2559.222.1
                committer: Narayanan V <v.narayanan@sun.com>
                branch nick: mysql-5.0-bugteam-42937-1
                timestamp: Wed 2009-03-11 12:41:59 +0530
                message:
                  Bug#42937 strings/CHARSET_INFO.txt not included in source distributions
                  
                  The reference manual has instructions for adding new character
                  sets, and refers to the string/CHARSET_INFO.txt file. This file
                  is currently not present in the distribution.
                  
                  Modify the build to include this file in the distribution.
            ------------------------------------------------------------
            revno: 2559.211.4
            committer: Davi Arnaut <Davi.Arnaut@Sun.COM>
            branch nick: 43461-5.0
            timestamp: Thu 2009-03-19 17:20:15 -0300
            message:
              Bug#43461: invalid comparison with string literal in default.c
              
              Don't compare string literals as it results in unspecified behavior.
            ------------------------------------------------------------
            revno: 2559.211.3
            committer: Ignacio Galarza <iggy@mysql.com>
            branch nick: mysql-5.0-bugteam-bug29125
            timestamp: Thu 2009-03-19 09:58:56 -0400
            message:
              auto-merge
                ------------------------------------------------------------
                revno: 2559.212.17
                committer: Bernt M. Johnsen <bernt.johnsen@sun.com>
                branch nick: 5.0-bugteam
                timestamp: Thu 2009-03-19 14:52:35 +0100
                message:
                  Bug#43329 merge from 5.0 GCA-branch
                    ------------------------------------------------------------
                    revno: 2559.218.7
                    committer: Bernt M. Johnsen <bernt.johnsen@sun.com>
                    branch nick: 5.0-gca
                    timestamp: Wed 2009-03-18 15:07:13 +0100
                    message:
                      Bug#43329 prepared for commit on 5.0
                ------------------------------------------------------------
                revno: 2559.212.16
                committer: Staale Smedseng <staale.smedseng@sun.com>
                branch nick: mysql-5.0-bugteam
                timestamp: Thu 2009-03-19 11:27:45 +0100
                message:
                  Bug #42502 huge memory leak possible with timezone 
                  functions
                        
                  Unknown timezone specifications are properly rejected
                  by the server, but are copied into tz_storage before
                  rejection, and hence is retained until end of server 
                  life. With sufficiently large bogus timezone specs, 
                  it is easy to exhaust system memory.
                        
                  Allocation of memory for a copy of the timezone
                  name is delayed until after verification of validity,
                  at the cost of a memcpy of the timezone info. This 
                  only happens once, future lookups will hit the cached
                  structure.
                ------------------------------------------------------------
                revno: 2559.212.15
                committer: Alexey Kopytov <Alexey.Kopytov@sun.com>
                branch nick: mysql-5.0-bugteam
                timestamp: Thu 2009-03-19 13:07:30 +0300
                message:
                  Automerge.
                    ------------------------------------------------------------
                    revno: 2559.221.2
                    committer: Alexey Kopytov <Alexey.Kopytov@sun.com>
                    branch nick: my50-bug41486
                    timestamp: Thu 2009-03-19 13:02:23 +0300
                    message:
                      Fixed test failures in 5.1/6.0 introduced by the patch
                      for bug #41486. Session max_allowed_packet is read-only
                      as of MySQL 5.1.31. In addition, the global variable
                      now has no effect on the current session.
                ------------------------------------------------------------
                revno: 2559.212.14
                committer: Sergey Glukhov <Sergey.Glukhov@sun.com>
                branch nick: mysql-5.0-bugteam
                timestamp: Thu 2009-03-19 12:42:26 +0400
                message:
                  automerge
                    ------------------------------------------------------------
                    revno: 2559.220.3
                    committer: Satya B <satya.bn@sun.com>
                    branch nick: mysql-5.0-bugteam-21360
                    timestamp: Thu 2009-03-19 13:53:24 +0530
                    message:
                      merge to 5.0-bugteam
                    ------------------------------------------------------------
                    revno: 2559.220.2
                    committer: Satya B <satya.bn@sun.com>
                    branch nick: mysql-5.0-bugteam-21360
                    timestamp: Thu 2009-03-19 11:36:37 +0530
                    message:
                      Fix for BUG#21360 - mysqldump error on federated tables
                                              
                      When loading dump created by mysqldump tool an error is
                      thrown saying storage engine for the table doesn't have 
                      an option.
                                              
                      mysqldump tries to re-insert the data into the federated
                      table which causes the error. Since the data is already
                      available on the remote server, mysqldump shouldn't try
                      to dump the data again for FEDERATED tables.
                                              
                      As stated in the bug page, it can be considered similar
                      to the MERGE ENGINE with "view only" nature.
                                              
                      Fixed by adding the "FEDERATED ENGINE" to the exception
                      list to ignore the data.
                ------------------------------------------------------------
                revno: 2559.212.13
                committer: Sergey Glukhov <Sergey.Glukhov@sun.com>
                branch nick: mysql-5.0-bugteam
                timestamp: Thu 2009-03-19 12:37:34 +0400
                message:
                  Bug#41268 Help Text for \c is misleading in client command line interface
                  fixed help message
                ------------------------------------------------------------
                revno: 2559.212.12
                committer: Sergey Glukhov <Sergey.Glukhov@sun.com>
                branch nick: mysql-5.0-bugteam
                timestamp: Thu 2009-03-19 12:20:28 +0400
                message:
                  Bug#41627 Illegal mix of collations in LEAST / GREATEST / CASE
                  Don't throw an error after checking the first and the second arguments.
                  Continue with checking the third and higher arguments and if some of
                  them is stronger according to coercibility rules,
                  then this argument's collation is set as result collation.
                ------------------------------------------------------------
                revno: 2559.212.11
                committer: Alexey Kopytov <Alexey.Kopytov@sun.com>
                branch nick: mysql-5.0-bugteam
                timestamp: Wed 2009-03-18 11:35:52 +0300
                message:
                  Automerge.
                ------------------------------------------------------------
                revno: 2559.221.1
                committer: Alexey Kopytov <Alexey.Kopytov@sun.com>
                branch nick: my50-bug41486
                timestamp: Wed 2009-03-18 11:18:24 +0300
                message:
                  Fix for bug#41486: extra character appears in BLOB for every 
                                     ~40Mb after mysqldump/import 
                          
                  When the input string exceeds the maximum allowed size for the 
                  internal buffer, batch_readline() returns a truncated string. 
                  Since there was no way for a caller to determine whether the 
                  string was truncated or not, the command line client assumed 
                  batch_readline() to always return the whole input string and 
                  appended a newline character. This resulted in garbled data 
                  when importing dumps containing strings longer than the 
                  maximum input buffer size. 
                    
                  Fixed by adding a flag to the batch_readline() interface to 
                  signal a truncated string to the caller. 
                    
                  Other minor problems fixed during patch implementation: 
                   
                  - The maximum allowed buffer size for batch_readline() was set 
                  up depending on the client's max_allowed_packet value. It does 
                  not actully make any sense, as those variables are not 
                  related. The input buffer size limit is now always set to 1 
                  MB. 
                    
                  - fill_buffer() did not always set the EOF flag. 
                   
                  - The input buffer could actually grow twice as the specified 
                  limit due to insufficient checks in intern_read_line(). 
            ------------------------------------------------------------
            revno: 2559.211.2
            committer: Ignacio Galarza <iggy@mysql.com>
            branch nick: mysql-5.0-bugteam-bug29125
            timestamp: Thu 2009-03-19 09:44:58 -0400
            message:
              auto-merge
                ------------------------------------------------------------
                revno: 2559.212.10
                committer: Georgi Kodinov <joro@sun.com>
                branch nick: B22047-5.0-bugteam
                timestamp: Tue 2009-03-17 16:28:05 +0200
                message:
                  merged 5.0-bugteam -> bug 22047
                    ------------------------------------------------------------
                    revno: 2559.220.1
                    committer: Patrick Crews <patrick.crews@sun.com>
                    branch nick: mysql-5.0-bugteam
                    timestamp: Sun 2009-03-15 12:25:14 -0400
                    message:
                      Bug#41307: Tests using include/ndb_backup.inc won't work on Windows due to 'grep' call.
                      
                      Revised patch incorporating cleaner test code brought up during review.
                      Removed the use of grep and accomplished same actions via SQL / use of the server.
                      
                      Runs as before on *nix systems and now runs on Windows without Cygwin as well.
                ------------------------------------------------------------
                revno: 2559.212.9
                committer: Georgi Kodinov <joro@sun.com>
                branch nick: B22047-5.0-bugteam
                timestamp: Fri 2009-03-13 15:51:25 +0200
                message:
                  Bug #22047 : Time in SHOW PROCESSLIST for SQL thread in replication 
                  seems to become negative
                  
                  THD::start_time has a dual meaning : it's either the time since the process
                  entered a given state or is the transaction time returned by e.g. NOW().
                  This causes problems, as sometimes THD::start_time may be set to a value
                  that is correct and needed when used as a base for NOW(), but these times
                  may be arbitrary (SET @@timestamp) or non-local (coming from the master 
                  through the replication feed).
                  If one such non-local time is set there's no way to return a correct value
                  for e.g. SHOW PROCESSLIST or SELECT ... FROM INFORMATION_SCHEMA.PROCESSLIST.
                  Fixed by making the Time column in SHOW PROCESSLIST SIGNED LONG instead of 
                  UNSIGNED LONG and doing the correct conversions.
                        
                  Note that no reliable test suite can be constructed, since it would require
                  knowing the local time and can't be achieved by the means of the current test
                  suite.
                ------------------------------------------------------------
                revno: 2559.212.8
                committer: Chad MILLER <chad@mysql.com>
                branch nick: mysql-5.0-bugteam
                timestamp: Thu 2009-03-12 13:32:13 -0400
                message:
                  Merge bug fix and upstream.
                    ------------------------------------------------------------
                    revno: 2559.218.6
                    committer: Timothy Smith <timothy.smith@sun.com>
                    branch nick: 50
                    timestamp: Wed 2009-03-11 14:54:57 -0600
                    message:
                      Bug #32625: Make test type_bit_innodb more robust
                      
                      Since there is more than one duplicate value in the table, when adding the
                      unique index it is not deterministic which value will be reported as causing a
                      problem.  Replace the reported value with '' so that it doesn't affect the
                      results.
                    ------------------------------------------------------------
                    revno: 2559.218.5
                    committer: Timothy Smith <timothy.smith@sun.com>
                    branch nick: 50
                    timestamp: Wed 2009-03-11 14:52:53 -0600
                    message:
                      Remove outdated and now useless TODO file from sql-bench.  Requested by sales.
                    ------------------------------------------------------------
                    revno: 2559.218.4
                    committer: Georgi Kodinov <joro@sun.com>
                    branch nick: B42434-5.0-bugteam
                    timestamp: Mon 2009-03-09 20:57:03 +0200
                    message:
                      Bug #42434: license of mysys MD5 implementation is not GPL-compatible
                      
                      Took the Xfree implementation (based on the same rewrite as the NDB one)
                      and added it instead of the current implementation.
                      Added a macro to make the calls to MD5 more streamlined. 
                    ------------------------------------------------------------
                    revno: 2559.218.3
                    committer: Georgi Kodinov <joro@sun.com>
                    branch nick: B43354-5.0-bugteam
                    timestamp: Wed 2009-03-11 15:01:35 +0200
                    message:
                      merged 5.0-main -> 5.0-bugteam
                        ------------------------------------------------------------
                        revno: 2559.219.2
                        author: kent.boortz@sun.com
                        committer: MySQL Build Team <build@mysql.com>
                        branch nick: mysql-5.0
                        timestamp: Mon 2009-03-09 19:33:01 +0100
                        message:
                          Raise version number after cloning 5.0.79
                        ------------------------------------------------------------
                        revno: 2559.219.1
                        tags: clone-5.0.79-build
                        committer: Georgi Kodinov <joro@sun.com>
                        branch nick: merge-5.0-pe-stage
                        timestamp: Mon 2009-03-09 15:59:22 +0200
                        message:
                          set the tree name to 5.0-main
                    ------------------------------------------------------------
                    revno: 2559.218.2
                    committer: Georgi Kodinov <joro@sun.com>
                    branch nick: B43354-5.0-bugteam
                    timestamp: Wed 2009-03-11 14:10:44 +0200
                    message:
                      Bug #43354: Use key hint can crash server in explain extended query
                            
                      The copy of the original arguments of a aggregate function was not
                      initialized until after fix_fields().
                      Sometimes (e.g. when there's an error processing the statement)
                      the print() can be called with no corresponding fix_fields() call.
                            
                      Fixed by adding a check if the Item is fixed before using the arguments
                      copy.
                    ------------------------------------------------------------
                    revno: 2559.218.1
                    committer: Matthias Leich <Matthias.Leich@sun.com>
                    branch nick: mysql-5.0-bugteam-42003-push
                    timestamp: Tue 2009-03-10 18:21:35 +0100
                    message:
                      Merge of fix into actual tree
                    ------------------------------------------------------------
                    revno: 2559.217.1
                    committer: Matthias Leich <Matthias.Leich@sun.com>
                    branch nick: mysql-5.0-bugteam-42003-2
                    timestamp: Thu 2009-03-05 14:35:03 +0100
                    message:
                      Merge of fix for Bug#42003 and Bug#43114 into more actual GCA tree
                      modifications according to the reviews are included
                    ------------------------------------------------------------
                    revno: 2559.216.1
                    committer: Matthias Leich <Matthias.Leich@sun.com>
                    branch nick: mysql-5.0-bugteam-42003-1
                    timestamp: Tue 2009-03-03 21:34:18 +0100
                    message:
                      Last slice of fix for Bug#42003 tests missing the disconnect of connections <> default
                      + Fix for Bug#43114 wait_until_count_sessions too restrictive, random PB failures
                      + Removal of a lot of other weaknesses found
                      + modifications according to review
                ------------------------------------------------------------
                revno: 2559.212.7
                committer: Chad MILLER <chad@mysql.com>
                branch nick: mysql-5.0-bugteam
                timestamp: Tue 2009-03-10 12:53:43 -0400
                message:
                  Merge from bugfix tree.
                    ------------------------------------------------------------
                    revno: 2559.215.2
                    committer: Chad MILLER <chad@mysql.com>
                    branch nick: mysql-5.0-bugteam--bug42635
                    timestamp: Mon 2009-03-09 16:58:47 -0400
                    message:
                      Bug#42635: mysqldump includes views that were excluded using the \
                      	--ignore-table option
                      
                      mysqldump would correctly omit temporary tables for views, but would
                      incorrectly still emit all CREATE VIEW statements.
                      
                      Backport a fix from 5.1, where we capture the names we want to emit
                      views for in one pass (the placeholder tables) and in the pass where
                      we actually emit the views, we don't emit a view if it wasn't in that
                      list.
                    ------------------------------------------------------------
                    revno: 2559.215.1
                    committer: Chad MILLER <chad@mysql.com>
                    branch nick: mysql-5.0-bugteam--bug42635
                    timestamp: Mon 2009-03-09 16:56:46 -0400
                    message:
                      Fix non-DBUG return.
                ------------------------------------------------------------
                revno: 2559.212.6
                committer: Patrick Crews <patrick.crews@sun.com>
                branch nick: mysql-5.0-bugteam
                timestamp: Mon 2009-03-09 11:32:07 -0400
                message:
                  Fix of failing funcs_1 tests.
                  Changes are due to changes in precision.
                  Re-record of .result files to account for new server precision.
                ------------------------------------------------------------
                revno: 2559.212.5
                committer: Georgi Kodinov <joro@sun.com>
                branch nick: merge-5.0-pe-stage
                timestamp: Mon 2009-03-09 12:49:18 +0200
                message:
                  fixed a typo
                ------------------------------------------------------------
                revno: 2559.212.4
                committer: Georgi Kodinov <joro@sun.com>
                branch nick: merge-5.0-pe-stage
                timestamp: Mon 2009-03-09 12:22:52 +0200
                message:
                  fixed a win32 compile warning
                ------------------------------------------------------------
                revno: 2559.212.3
                committer: He Zhenxing <zhenxing.he@sun.com>
                branch nick: 5.0-bugteam
                timestamp: Mon 2009-03-09 16:44:18 +0800
                message:
                  Auto merge
                    ------------------------------------------------------------
                    revno: 2559.214.3
                    committer: Kristofer Pettersson <kristofer.pettersson@sun.com>
                    branch nick: mysql-5.0-bugteam
                    timestamp: Fri 2009-03-06 11:49:39 +0100
                    message:
                      Manual merge
                    ------------------------------------------------------------
                    revno: 2559.214.2
                    committer: Kristofer Pettersson <kristofer.pettersson@sun.com>
                    branch nick: mysql-5.0-bugteam
                    timestamp: Thu 2009-03-05 13:37:46 +0100
                    message:
                      Bug#40363 Bug 20023 is not fixed on 5.0
                      
                      This is a back port from 5.1 to 5.0.
                      
                      Fix for BUG 20023: mysql_change_user() resets the value
                      of SQL_BIG_SELECTS.
                        
                      The bug was that SQL_BIG_SELECTS was not properly set
                      in COM_CHANGE_USER.
                        
                      The fix is to update SQL_BIG_SELECTS properly.
                    ------------------------------------------------------------
                    revno: 2559.214.1
                    committer: Kristofer Pettersson <kristofer.pettersson@sun.com>
                    branch nick: mysql-5.0-bugteam
                    timestamp: Fri 2008-11-07 16:23:01 +0100
                    message:
                      automerge
                    ------------------------------------------------------------
                    revno: 2559.213.1
                    committer: Kristofer Pettersson <kristofer.pettersson@sun.com>
                    branch nick: mysql-5.0-bug37416
                    timestamp: Tue 2008-10-14 15:41:35 +0200
                    message:
                      Bug#37416 When SQL_NO_CACHE is used, MySQL still lookup into the query cache
                            
                      The query cache module did not check for the SQL_NO_CACHE keyword before
                      attempting to query the hash lookup table. This had a small performance impact.
                            
                      By introducing a check on the query string before obtaining the hash mutex
                      we can gain some performance if the SQL_NO_CACHE directive is used often.
                ------------------------------------------------------------
                revno: 2559.212.2
                committer: He Zhenxing <zhenxing.he@sun.com>
                branch nick: 5.0-bugteam
                timestamp: Fri 2009-03-06 17:34:47 +0800
                message:
                  Auto merge
                ------------------------------------------------------------
                revno: 2559.212.1
                committer: He Zhenxing <zhenxing.he@sun.com>
                branch nick: 5.0-bugteam
                timestamp: Fri 2009-03-06 17:32:00 +0800
                message:
                  BUG#22082 Slave hangs(holds mutex) on "disk full"
                  
                  When disk is full, server may waiting for free space while
                  writing binlog, relay-log or MyISAM tables. The server will 
                  continue after user have freed some space. But the error
                  message printed was not quite clear about the how often the
                  error message is printed, and there will be a delay before
                  the server continue and user freeing space. And caused users
                  thinking that the server was hanging forever.
                  
                  This patch fixed the problem by making the error messages
                  printed more clear. The error message is split into two part,
                  the first part will only be printed once, and the second part
                  will be printed very 10 times.
                  
                  Message first part:
                  Disk is full writing '<filename>' (Errcode: <errorno>). Waiting
                  for someone to free space... (Expect up to 60 secs delay for 
                  server to continue after freeing disk space)
                  
                  Message second part:
                  Retry in 60 secs, Message reprinted in 600 secs
            ------------------------------------------------------------
            revno: 2559.211.1
            committer: Ignacio Galarza <iggy@mysql.com>
            branch nick: mysql-5.0-bugteam-bug29125
            timestamp: Tue 2009-02-10 17:47:54 -0500
            message:
              Bug#29125 Windows Server X64: so many compiler warnings
              - Remove bothersome warning messages.  This change focuses on the warnings 
              that are covered by the ignore file: support-files/compiler_warnings.supp.
              - Strings are guaranteed to be max uint in length
        ------------------------------------------------------------
        revno: 2559.210.1
        committer: Tatiana A. Nurnberg <azundris@mysql.com>
        branch nick: mysql-5.0-bugteam
        timestamp: Mon 2009-03-23 05:08:32 +0100
        message:
          Bug#43254: SQL_SELECT_LIMIT=0 crashes command line client
          
          When asking what database is selected, client expected
          to *always* get an answer from the server.
          
          We now handle failure more gracefully.
          
          See comments in ticket for a discussion of what happens,
          and how things interlock.
    ------------------------------------------------------------
    revno: 2559.157.49
    committer: Leonard Zhou <leonard@mysql.com>
    branch nick: bug41719
    timestamp: Tue 2009-03-24 08:45:05 +0800
    message:
      BUG#41719 delayed INSERT into timestamp col needs set time_zone for concurrent binlogging
      
      When do 'insert delayed' operation, the time_zone info doesn't be keeped in the row info.
      So when we do insert sometime later, time_zone didn't write into binlog.
      This will cause wrong result for timestamp column in slave.
      
      Our solution is that adding time_zone info with the delayed-row and
      restoring time_zone from row-info when execute that row in the furture by another thread.
      So we can write correct time_zone info into binlog and got correct result in slave.
    ------------------------------------------------------------
    revno: 2559.157.48
    committer: He Zhenxing <zhenxing.he@sun.com>
    branch nick: 5.0-bugteam
    timestamp: Thu 2009-03-05 18:10:44 +0800
    message:
      BUG#37051 Replication rules not evaluated correctly
      
      Backporting patch to 5.0.
    ------------------------------------------------------------
    revno: 2559.157.47
    committer: Timothy Smith <timothy.smith@sun.com>
    branch nick: 50
    timestamp: Mon 2009-03-02 18:00:23 -0700
    message:
      Applying InnoDB snashot 5.0-ss4007, part 3.  Fixes
      
      Bug #41571: MySQL segfaults after innodb recovery
      
      This 5.0 fix will not be pushed into 5.1; a separate fix (from
      innodb-5.1-ss4007) will be pushed into 5.1+.
      
      Detailed revision comments:
      
      r4003 | marko | 2009-01-20 16:12:50 +0200 (Tue, 20 Jan 2009) | 10 lines
      branches/5.0: rec_set_nth_field(): When the field already is SQL null,
      do nothing when it is being changed to SQL null. (Bug #41571)
      
      Normally, MySQL does not pass "do-nothing" updates to the storage engine.
      When it does and a column of an InnoDB table that is in ROW_FORMAT=COMPACT
      is being updated from NULL to NULL, the InnoDB buffer pool will be corrupted
      without this fix.
      
      rb://81 approved by Heikki Tuuri
    ------------------------------------------------------------
    revno: 2559.157.46
    committer: Timothy Smith <timothy.smith@sun.com>
    branch nick: 50
    timestamp: Mon 2009-03-02 17:57:09 -0700
    message:
      Applying InnoDB snashot 5.0-ss4007, part 2.  Fixes
      
      Bug #18828: If InnoDB runs out of undo slots, it returns misleading 'table is full'
      
      This is a backport of code already in 5.1+.  The error message change referred
      to in the detailed revision comments is still pending.
      
      Detailed revision comments:
      
      r3937 | calvin | 2009-01-15 03:11:56 +0200 (Thu, 15 Jan 2009) | 17 lines
      branches/5.0:
      
      Backport the fix for Bug#18828. Return DB_TOO_MANY_CONCURRENT_TRXS
      when we run out of UNDO slots in the rollback segment. The backport
      is requested by MySQL under bug#41529 - Safe handling of InnoDB running
      out of undo log slots.
      
      This is a partial fix since the MySQL error code requested to properly
      report the error condition back to the client has not yet materialized.
      Currently we have #ifdef'd the error code translation in ha_innodb.cc.
      This will have to be changed as and when MySQl add the new requested
      code or an equivalent code that we can then use.
      
      Given the above, currently we will get the old behavior, not the
      "fixed" and intended behavior.
      
      Approved by:	Heikki (on IM)
    ------------------------------------------------------------
    revno: 2559.157.45
    committer: Timothy Smith <timothy.smith@sun.com>
    branch nick: 50
    timestamp: Mon 2009-03-02 17:24:23 -0700
    message:
      Applying InnoDB snashot 5.0-ss4007, part 1.  Fixes
      
      Bug #39939: DROP TABLE/DISCARD TABLESPACE takes long time in buf_LRU_invalidate_tablespace()
      
      This was already fixed in 5.1+; this is a backport to 5.0.
      
      Detailed revision comments:
      
      r2743 | inaam | 2008-10-08 22:18:12 +0300 (Wed, 08 Oct 2008) | 13 lines
      branches/5.0:
      
      Backport of r2742 from branches/5.1:
      
      Fix Bug#39939 DROP TABLE/DISCARD TABLESPACE takes long time in
      buf_LRU_invalidate_tablespace()
      
      Improve implementation of buf_LRU_invalidate_tablespace by attempting
      hash index drop in batches instead of doing it one by one.
      
      Reviewed by: Heikki, Sunny, Marko
      Approved by: Heikki
    ------------------------------------------------------------
    revno: 2559.157.44
    committer: Bernt M. Johnsen <bernt.johnsen@sun.com>
    branch nick: 5.0-bugteam
    timestamp: Mon 2009-03-02 14:26:57 +0100
    message:
      Merged from gca branch (bug 42711)
        ------------------------------------------------------------
        revno: 2559.209.1
        committer: Bernt M. Johnsen <bernt.johnsen@sun.com>
        branch nick: 5.0-gca
        timestamp: Mon 2009-03-02 11:03:13 +0100
        message:
          Prepared BUG#42711 for push
    ------------------------------------------------------------
    revno: 2559.157.43
    committer: Staale Smedseng <staale.smedseng@sun.com>
    branch nick: b29458-50p
    timestamp: Fri 2009-02-27 18:07:58 +0200
    message:
      Commit after merge from 5.0-bugteam
        ------------------------------------------------------------
        revno: 2559.205.5
        committer: Georgi Kodinov <kgeorge@mysql.com>
        branch nick: B41610-5.0-bugteam
        timestamp: Fri 2009-02-27 15:25:06 +0200
        message:
          Bug #41610: key_infix_len can be overwritten causing some group by queries to
          return no rows
          
          The algorithm of determining the best key for loose index scan is doing a loop
          over the available indexes and selects the one that has the best cost.
          It retrieves the parameters of the current index into a set of variables.
          If the cost of using the current index is lower than the best cost so far it 
          copies these variables into another set of variables that contain the 
          information for the best index so far.
          After having checked all the indexes it uses these variables (outside of the 
          index loop) to create the table read plan object instance.
          The was a single omission : the key_infix/key_infix_len variables were used 
          outside of the loop without being preserved in the loop for the best index 
          so far.
          This causes these variables to get overwritten by the next index(es) checked.
          Fixed by adding variables to hold the data for the current index, passing 
          the new variables to the function that assigns values to them and copying 
          the new variables into the existing ones when selecting a new current best 
          index.
          To avoid further such problems moved the declarations of the variables used 
          to keep information about the current index inside the loop's compound 
          statement.
        ------------------------------------------------------------
        revno: 2559.205.4
        committer: Patrick Crews <patrick.crews@sun.com>
        branch nick: mysql-5.0-bugteam
        timestamp: Fri 2009-02-27 15:00:49 +0200
        message:
          Bug#41893:  Removal of trailing space noise causing Pushbuild failure.
        ------------------------------------------------------------
        revno: 2559.205.3
        committer: Patrick Crews <patrick.crews@sun.com>
        branch nick: mysql-5.0-bugteam
        timestamp: Fri 2009-02-27 10:45:19 +0200
        message:
          merge.
            ------------------------------------------------------------
            revno: 2559.206.9
            committer: Georgi Kodinov <kgeorge@mysql.com>
            branch nick: B41354-merge-5.0-bugteam
            timestamp: Fri 2009-02-27 09:41:39 +0200
            message:
              addendum to the fix for bug #41354: fixed the error returned by SELECT *
            ------------------------------------------------------------
            revno: 2559.206.8
            committer: Georgi Kodinov <kgeorge@mysql.com>
            branch nick: B41354-merge-5.0-bugteam
            timestamp: Thu 2009-02-26 19:00:44 +0200
            message:
              Bug #41354: Access control is bypassed when all columns 
              of a view are selected by * wildcard
              
              Backported a part of the fix for 36086 to 5.0
            ------------------------------------------------------------
            revno: 2559.206.7
            committer: Ramil Kalimullin <ramil@mysql.com>
            branch nick: mysql-5.0-bugteam
            timestamp: Thu 2009-02-26 14:11:46 +0400
            message:
              Auto-merge
                ------------------------------------------------------------
                revno: 2559.208.2
                committer: Ramil Kalimullin <ramil@mysql.com>
                branch nick: b19829-5.0-bugteam
                timestamp: Thu 2009-02-26 12:34:15 +0400
                message:
                  Fix for bug#19829:make test Failed in mysql_client_test
                  *with --with-charset=utf8*
                  
                  Problem: wrong LONG TEXT field length is sent to a client 
                  when multibyte server character set used.
                  
                  Fix: always limit field length sent to a client to 2^32,
                  as we store it in 4 byte slot.
                  
                  Note: mysql_client_test changed accordingly.
            ------------------------------------------------------------
            revno: 2559.206.6
            committer: Vladislav Vaintroub <vvaintroub@mysql.com>
            branch nick: mysql-5.0-bugteam
            timestamp: Wed 2009-02-25 17:27:32 +0100
            message:
              merge from 5.0-bugteam
                ------------------------------------------------------------
                revno: 2559.208.1
                committer: Bernt M. Johnsen <bernt.johnsen@sun.com>
                branch nick: mysql-5.0-bugteam
                timestamp: Wed 2009-02-25 14:52:33 +0100
                message:
                  Merged from gca-branch (bug 43111)
                ------------------------------------------------------------
                revno: 2559.207.1
                committer: Bernt M. Johnsen <bernt.johnsen@sun.com>
                branch nick: gca-5.0
                timestamp: Wed 2009-02-25 11:37:30 +0100
                message:
                  Prepare for push of BUG#43111
            ------------------------------------------------------------
            revno: 2559.206.5
            committer: Vladislav Vaintroub <vvaintroub@mysql.com>
            branch nick: mysql-5.0-bugteam
            timestamp: Wed 2009-02-25 16:57:49 +0100
            message:
              Bug#43082: mysqld 32 bit cannot use big buffers due to 2GB
              usermode address space limit.
              
              Fix: use /LARGEADDRESSAWARE link option when linking 32 bit
              executables
            ------------------------------------------------------------
            revno: 2559.206.4
            committer: Sergey Glukhov <Sergey.Glukhov@sun.com>
            branch nick: mysql-5.0-bugteam
            timestamp: Wed 2009-02-25 15:44:50 +0400
            message:
              Bug#40345 MySQLDump prefixes view name with database name when view references other db
              print compact view name if the view belongs to the current database
            ------------------------------------------------------------
            revno: 2559.206.3
            committer: Sergey Glukhov <Sergey.Glukhov@sun.com>
            branch nick: mysql-5.0-bugteam
            timestamp: Wed 2009-02-25 14:20:20 +0400
            message:
              Bug#30305 Create routine in wrong context in SHOW PRIVILEGES
              Changed context of Create routine to Databases.
            ------------------------------------------------------------
            revno: 2559.206.2
            committer: Georgi Kodinov <kgeorge@mysql.com>
            branch nick: B31060-5.0-bugteam
            timestamp: Tue 2009-02-24 15:06:28 +0200
            message:
              Bug #31060: MySQL CLI parser bug 2
                    
              There was a problem when a DELIMITER COMMAND is not the first 
              command on the line. I this case an extra line feed was added
              to the glob buffer and this was causing subsequent attempts 
              to enter this delimiter to fail.
              Fixed by not adding a new line to the glob buffer if the 
              command being added is a DELIMITER
            ------------------------------------------------------------
            revno: 2559.206.1
            committer: Alexey Kopytov <Alexey.Kopytov@sun.com>
            branch nick: mysql-5.0-bugteam
            timestamp: Wed 2009-02-25 10:48:05 +0200
            message:
              Automerge.
            ------------------------------------------------------------
            revno: 2559.200.2
            committer: Alexey Kopytov <Alexey.Kopytov@sun.com>
            branch nick: my50-bug15936
            timestamp: Wed 2009-02-25 10:36:11 +0200
            message:
              Fixed a build failure on Ubuntu 8.10 introduced by the patch
              for bug #15936.
              
              On some platforms fenv.h may #undef the min/max macros
              defined in my_global.h.
              
              Fixed by moving the #include directive for fenv.h from
              mysqld.cc to my_global.h before definitions for min/max.
        ------------------------------------------------------------
        revno: 2559.205.2
        committer: Patrick Crews <patrick.crews@sun.com>
        branch nick: mysql-5.0-bugteam
        timestamp: Thu 2009-02-26 18:00:47 +0200
        message:
          Bug#41893 - main.variables mysql-test fails if new variable like '%alloc%' is added.
          
          Fixed a typo in the bug fix patch.
        ------------------------------------------------------------
        revno: 2559.205.1
        committer: Patrick Crews <patrick.crews@sun.com>
        branch nick: mysql-5.0-bugteam
        timestamp: Thu 2009-02-26 10:57:33 +0200
        message:
          Bug#41893: main.variables mysql-test fails if new variable like '%alloc%' is added.
          
          Started fix in 5.0 as the same issue is here.
          Revising queries used given what appears to be the scope of this test to only select the manipulated variables.
          Added tests for values that are / are not multiples of 1024 to test rounding / constraints.
          This behavior is not currently documented (docs bug has been opened)
    ------------------------------------------------------------
    revno: 2559.157.42
    committer: Staale Smedseng <staale.smedseng@sun.com>
    branch nick: b29458-50p
    timestamp: Fri 2009-02-27 16:11:15 +0200
    message:
      Recommit for merging and pushing
    ------------------------------------------------------------
    revno: 2559.157.41
    committer: Andrei Elkin <aelkin@mysql.com>
    branch nick: bug37313-server_id_binlog
    timestamp: Tue 2009-02-24 16:35:45 +0200
    message:
      merging from 5.0-bt rep to a local branch
        ------------------------------------------------------------
        revno: 2559.198.9
        committer: Alexey Botchkov <holyfoot@mysql.com>
        branch nick: 50mrg
        timestamp: Tue 2009-02-24 15:22:37 +0400
        message:
          merging.
            ------------------------------------------------------------
            revno: 2559.204.1
            committer: Alexey Botchkov <holyfoot@mysql.com>
            branch nick: 31435
            timestamp: Tue 2008-11-11 14:42:32 +0400
            message:
              Bug#31435 ha_innodb.cc:3983: ulint convert_search_mode_to_innobase(ha_rkey_function): Asse 
                  I think we don't need to issue an error statement in the convert_search_mode_to_innobase().
                  Returning the PAGE_CUR_UNSUPP value is enough as allows to handle this
                  case depending on the requirements.
              
              per-file comments:
                sql/ha_innodb.cc 
              Bug#31435 ha_innodb.cc:3983: ulint convert_search_mode_to_innobase(ha_rkey_function): Asse 
                   no error issued in convert_search_mode_to_innobase.
                   ha_innobase::records_in_range() returns HA_POS_ERROR if search mode isn't supported.
        ------------------------------------------------------------
        revno: 2559.198.8
        committer: Chad MILLER <chad@mysql.com>
        branch nick: 5.0-bugteam
        timestamp: Tue 2009-02-24 12:31:42 +0200
        message:
          Merge bug 39370 fix from bug tree.
            ------------------------------------------------------------
            revno: 2559.203.1
            committer: Chad MILLER <chad@mysql.com>
            branch nick: 5.0-bugteam--bug39370
            timestamp: Tue 2009-02-24 12:05:37 +0200
            message:
              Bug#39370: wrong output for error code 153
              
              Add all HA error numbers and descriptions to perror.
              
              Add reminder to header.
              
              This is already fixed in smarter ways in future codebases, and this 
              codebase is unlikely to change, since new development is forbidden
              here.
        ------------------------------------------------------------
        revno: 2559.198.7
        committer: Davi Arnaut <Davi.Arnaut@Sun.COM>
        branch nick: 41110-5.0
        timestamp: Tue 2009-02-24 10:15:21 +0100
        message:
          Bug#41110: crash with handler command when used concurrently with alter table
          Bug#41112: crash in mysql_ha_close_table/get_lock_data with alter table
          
          The problem is that the server wasn't handling robustly failures
          to re-open a table during a HANDLER .. READ statement. If the
          table needed to be re-opened due to it's storage engine being
          altered to one that doesn't support HANDLER, a reference (dangling
          pointer) to a closed table could be left in place and accessed in
          later attempts to fetch from the table using the handler. Also,
          if the server failed to set a error message if the re-open
          failed. These problems could lead to server crashes or hangs.
          
          The solution is to remove any references to a closed table and
          to set a error if reopening a table during a HANDLER .. READ
          statement fails.
          
          There is no test case in this change set as the test depends on
          a testing feature only available on 5.1 and later.
        ------------------------------------------------------------
        revno: 2559.198.6
        committer: Tatiana A. Nurnberg <azundris@mysql.com>
        branch nick: 50-37400_
        timestamp: Tue 2009-02-24 09:31:42 +0100
        message:
          automerge
            ------------------------------------------------------------
            revno: 2559.202.1
            committer: Tatiana A. Nurnberg <azundris@mysql.com>
            branch nick: 50-37400
            timestamp: Thu 2009-02-19 04:58:10 +0100
            message:
              Bug#37400: mysql: Bad help message for charset command
              
              Typo existed in help-text for command "charset" in mysql
              client, making the parameter-name different for long and
              short forms of the command for no good reason.
              
              Fixed.
        ------------------------------------------------------------
        revno: 2559.198.5
        committer: Tatiana A. Nurnberg <azundris@mysql.com>
        branch nick: 50-42027_
        timestamp: Tue 2009-02-24 09:06:02 +0100
        message:
          automerge
            ------------------------------------------------------------
            revno: 2559.201.1
            committer: Tatiana A. Nurnberg <azundris@mysql.com>
            branch nick: 50-42027
            timestamp: Mon 2009-02-16 15:38:18 +0100
            message:
              Bug#42027: Incorrect parsing of debug and verbose options for mysqldumpslow
              
              Options got normalised to long rather than short options
              since we gave primary name and alias in wrong order.
              Consequently querying for the option using the short
              options (the correct primary name) didn't work, rendering
              the options in question inaccessible.
              
              We restore the right order of the universe, or at least
              the alii for --debug and --verbose.
        ------------------------------------------------------------
        revno: 2559.198.4
        committer: Tatiana A. Nurnberg <azundris@mysql.com>
        branch nick: 50-33550_
        timestamp: Tue 2009-02-24 08:05:30 +0100
        message:
          automerge
            ------------------------------------------------------------
            revno: 2559.199.4
            committer: Alexey Kopytov <Alexey.Kopytov@sun.com>
            branch nick: mysql-5.0-bugteam
            timestamp: Mon 2009-02-23 14:53:51 +0200
            message:
              Automerge.
            ------------------------------------------------------------
            revno: 2559.200.1
            committer: Alexey Kopytov <Alexey.Kopytov@sun.com>
            branch nick: my50-bug15936
            timestamp: Mon 2009-02-23 14:28:26 +0200
            message:
              Fix for bug #15936: "round" differs on Windows to Unix
              
              Both of our own implementations of rint(3) were inconsistent with the
              most common behavior of rint() on those platforms that have it: round
              to nearest, break ties by rounding to nearest even.
              
              Fixed by leaving just one implementation of rint() in our source tree,
              and changing its behavior to match the most common native
              implementations on other platforms.
        ------------------------------------------------------------
        revno: 2559.198.3
        committer: Tatiana A. Nurnberg <azundris@mysql.com>
        branch nick: 50-33550_
        timestamp: Mon 2009-02-23 13:14:17 +0100
        message:
          auto-merge
            ------------------------------------------------------------
            revno: 2559.199.3
            committer: Patrick Crews <patrick.crews@sun.com>
            branch nick: mysql-5.0-bugteam
            timestamp: Fri 2009-02-20 08:40:28 -0500
            message:
              automerge
            ------------------------------------------------------------
            revno: 2559.199.2
            committer: Patrick Crews <patrick.crews@sun.com>
            branch nick: mysql-5.0-bugteam
            timestamp: Thu 2009-02-19 16:35:29 -0500
            message:
              Bug#38831:  11 test cases fail on Windows due to missing commands
              
              Re-enabling mysqlbinlog.test on Windows - removed the use of grep/sed
            ------------------------------------------------------------
            revno: 2559.199.1
            committer: Patrick Crews <patrick.crews@sun.com>
            branch nick: mysql-5.0-bugteam
            timestamp: Thu 2009-02-19 15:37:40 -0500
            message:
              Bug#38831: 11 test cases fail on Windows due to missing commands
              
              Replaced Unix calls with mysql-test-run's built-in functions / SQL manipulation where possible.
              Replaced error codes with error names as well.
              Disabled two tests on Windows due to more complex Unix command usage
              See Bug#41307, Bug#41308
        ------------------------------------------------------------
        revno: 2559.198.2
        committer: Tatiana A. Nurnberg <azundris@mysql.com>
        branch nick: 50-33550_
        timestamp: Mon 2009-02-23 12:53:04 +0100
        message:
          auto-merge
        ------------------------------------------------------------
        revno: 2559.198.1
        committer: Tatiana A. Nurnberg <azundris@mysql.com>
        branch nick: 50-33550_
        timestamp: Thu 2009-02-19 17:33:28 +0100
        message:
          Bug#33550: mysqldump 4.0 compatibility broken
          
          mysqldump included character_set_client magic
          that is unknown before 4.1 even when asked for
          an appropriate compatibility mode.
          
          In compatibility (3.23, 4.0) mode, we do not
          output charset statements (not even in a
          "comment conditional"), nor do we do magic on
          the server, even if the server is sufficient
          new (4.1+). Table-names will be output converted
          to the charset requested by mysqldump; if such
          a conversion is not possible (Ivrit -> Latin),
          mysqldump will fail.
        ------------------------------------------------------------
        revno: 2559.197.1
        committer: Tatiana A. Nurnberg <azundris@mysql.com>
        branch nick: 50-33550
        timestamp: Mon 2009-02-02 18:19:07 +0100
        message:
          Bug#33550: mysqldump 4.0 compatibility broken
          
          mysqldump included character_set_client magic
          that is unknown before 4.1 even when asked for
          an appropriate compatibility mode.
          
          In compatibility (3.23, 4.0) mode, we do not
          output charset statements (not even in a
          "comment conditional"), nor do we do magic on
          the server, even if the server is sufficient
          new (4.1+). Table-names will be output converted
          to the charset requested by mysqldump; if such
          a conversion is not possible (Ivrit -> Latin),
          mysqldump will fail.
    ------------------------------------------------------------
    revno: 2559.157.40
    committer: Andrei Elkin <aelkin@mysql.com>
    branch nick: bug37313-server_id_binlog
    timestamp: Tue 2009-02-24 16:17:34 +0200
    message:
      fixing compilation warning and adding flush logs to test of bug#37313
    ------------------------------------------------------------
    revno: 2559.157.39
    committer: Andrei Elkin <aelkin@mysql.com>
    branch nick: bug37313-server_id_binlog
    timestamp: Fri 2009-02-20 13:55:43 +0200
    message:
      Bug #37313 BINLOG Contains Incorrect server id
        
      Signed integer format specifier forced to print the binlog header with server_id
      negative if the unsigned value sets the sign-bit ON.
        
      Fixed with correcting the specifier to correspond to typeof(server_id) == ulong.
    ------------------------------------------------------------
    revno: 2559.157.38
    committer: Georgi Kodinov <joro@sun.com>
    branch nick: B42419-merge-5.0-bugteam
    timestamp: Fri 2009-02-20 11:42:35 +0200
    message:
      fixed a warning
    ------------------------------------------------------------
    revno: 2559.157.37
    committer: Georgi Kodinov <joro@sun.com>
    branch nick: B42419-merge-5.0-bugteam
    timestamp: Fri 2009-02-20 11:12:06 +0200
    message:
      Bug #42419: test suite fix
      
      Moved the test case for the bug into a separate file (and restored the 
      original innodb_mysql test setup).
      Used the new wait_show_condition test macro to avoid the usage of sleep
    ------------------------------------------------------------
    revno: 2559.157.36
    committer: Georgi Kodinov <joro@sun.com>
    branch nick: B42419-merge-5.0-bugteam
    timestamp: Thu 2009-02-19 18:26:19 +0200
    message:
      merged bug 42419 to 5.0-bugteam
        ------------------------------------------------------------
        revno: 2559.196.1
        committer: Georgi Kodinov <joro@sun.com>
        branch nick: B42419-5.0-bugteam
        timestamp: Thu 2009-02-19 17:30:03 +0200
        message:
          Bug #42419: Server crash with "Pure virtual method called" on two concurrent
          connections
          The problem is that tables can enter open table cache for a thread without 
          being properly cleaned up. This can happen if make_join_statistics() fails 
          to read a const table because of e.g. a deadlock. It does set a member of 
          TABLE structure to a value it allocates, but doesn't clean-up this setting 
          on error nor does it set the rest of the members in JOIN to allow for 
          automatic cleanup.
          As a result when such an error occurs and the next statement depends re-uses 
          the table from the open tables cache it will get it with this 
          TABLE::reginfo.join_tab pointing to a memory area that's freed.
          Fixed by making sure make_join_statistics() cleans up TABLE::reginfo.join_tab 
          on error.
    ------------------------------------------------------------
    revno: 2559.157.35
    committer: Sergey Glukhov <Sergey.Glukhov@sun.com>
    branch nick: mysql-5.0-bugteam
    timestamp: Thu 2009-02-19 17:20:44 +0400
    message:
      Bug#37601 Cast Is Not Done On Row Comparison
      In case of ROW item each compared pair does not
      check if argumet collations can be aggregated and
      thus appropiriate item conversion does not happen.
      The fix is to add the check and convertion for ROW
      pairs.
    ------------------------------------------------------------
    revno: 2559.157.34
    committer: Alexey Kopytov <Alexey.Kopytov@sun.com>
    branch nick: mysql-5.0-bugteam
    timestamp: Thu 2009-02-19 12:02:11 +0300
    message:
      Automerge.
        ------------------------------------------------------------
        revno: 2559.195.1
        committer: Alexey Kopytov <Alexey.Kopytov@sun.com>
        branch nick: my50-bug41078
        timestamp: Thu 2009-02-19 11:49:35 +0300
        message:
          Fix for bug #41078: With CURSOR_TYPE_READ_ONLY mysql_stmt_fetch()                          
          returns short string value. 
           
          Multibyte character sets were not taken into account when 
          calculating max_length in Item_param::convert_str_value(). As a 
          result, string parameters of a prepared statement could be 
          truncated later when calculating string length in characters by 
          dividing length in bytes by the charset's mbmaxlen value (e.g. in 
          Field_varstring::store()). 
           
          Fixed by taking charset's mbmaxlen into account when calculating 
          max_length in Item_param::convert_str_value().
    ------------------------------------------------------------
    revno: 2559.157.33
    committer: Sergey Glukhov <Sergey.Glukhov@sun.com>
    branch nick: mysql-5.0-bugteam
    timestamp: Wed 2009-02-18 15:53:30 +0400
    message:
      automerge
        ------------------------------------------------------------
        revno: 2559.194.1
        committer: Georgi Kodinov <joro@sun.com>
        branch nick: B26724-5.0-bugteam
        timestamp: Wed 2009-02-18 12:18:38 +0200
        message:
          Bug #26724: mysql command line client, ignores input to internal cmd after space
                
          Removed the misleading "NOTE:" from the \h command. 
    ------------------------------------------------------------
    revno: 2559.157.32
    committer: Sergey Glukhov <Sergey.Glukhov@sun.com>
    branch nick: mysql-5.0-bugteam
    timestamp: Tue 2009-02-17 18:22:48 +0400
    message:
      Bug#25830 SHOW TABLE STATUS behaves differently depending on table name(for 5.0 only)
      replace wild_case_compare with my_wildcmp which is multibyte safe function
    ------------------------------------------------------------
    revno: 2559.157.31
    committer: Georgi Kodinov <joro@sun.com>
    branch nick: merge-5.0-bugteam
    timestamp: Mon 2009-02-16 12:54:03 +0200
    message:
      merged 5.1-main -> 5.1-bugteam
        ------------------------------------------------------------
        revno: 2559.193.1
        committer: Georgi Kodinov <joro@sun.com>
        branch nick: merge-5.0-bugteam
        timestamp: Wed 2009-02-11 12:04:40 +0200
        message:
          changed the tree id pending a merge of 5.0-bugteam -> 5.0-main
    ------------------------------------------------------------
    revno: 2559.157.30
    committer: Alexey Kopytov <Alexey.Kopytov@sun.com>
    branch nick: mysql-5.0-bugteam
    timestamp: Sun 2009-02-15 12:26:08 +0300
    message:
      Fixed PB failures on IA64 hosts introduced by the patch for bug #21205.
    ------------------------------------------------------------
    revno: 2559.157.29
    committer: Alexey Kopytov <Alexey.Kopytov@sun.com>
    branch nick: mysql-5.0-bugteam
    timestamp: Sat 2009-02-14 20:12:14 +0300
    message:
      Added missing DROP TABLE to type_float.result.
    ------------------------------------------------------------
    revno: 2559.157.28
    committer: Alexey Kopytov <Alexey.Kopytov@sun.com>
    branch nick: mysql-5.0-bugteam
    timestamp: Sat 2009-02-14 18:58:07 +0300
    message:
      Fixed several test failures in the funcs_1 suite introduced by the patch for bug #21205.
    ------------------------------------------------------------
    revno: 2559.157.27
    committer: Alexey Kopytov <Alexey.Kopytov@sun.com>
    branch nick: mysql-5.0-bugteam
    timestamp: Sat 2009-02-14 18:36:57 +0300
    message:
      Fixed bdb_gis and ndb_gis test failures in PB introduced by the patch for bug #21205.
    ------------------------------------------------------------
    revno: 2559.157.26
    committer: Alexey Kopytov <Alexey.Kopytov@sun.com>
    branch nick: mysql-5.0-bugteam
    timestamp: Sat 2009-02-14 12:09:35 +0300
    message:
      Merge from dev tree.
        ------------------------------------------------------------
        revno: 2559.192.1
        committer: Alexey Kopytov <Alexey.Kopytov@sun.com>
        branch nick: my50-bug21205
        timestamp: Wed 2009-01-28 20:59:08 +0300
        message:
          Fix for bug #21205: Different number of digits for float/double/real in --ps-protocol
          
          Various parts of code used different 'precision' arguments for sprintf("%g") when converting
          floating point numbers to a string. This led to differences in results in some cases 
          depending on whether the text-based or prepared statements protocol is used for a query.
          
          Fixed by changing arguments to sprintf("%g") to always be 15 (DBL_DIG) so that results are
          consistent regardless of the protocol.
          
          This patch will be null-merged to 6.0 as the problem does not exists there (fixed by the
          patch for WL#2934).
    ------------------------------------------------------------
    revno: 2559.157.25
    committer: Davi Arnaut <Davi.Arnaut@Sun.COM>
    branch nick: mysql-5.0-bugteam
    timestamp: Fri 2009-02-13 17:26:20 -0200
    message:
      Remove test case for bug 40264.
      Dirty close tricky does not work on Windows.
    ------------------------------------------------------------
    revno: 2559.157.24
    committer: Alexey Kopytov <Alexey.Kopytov@sun.com>
    branch nick: mysql-5.0-bugteam
    timestamp: Fri 2009-02-13 19:17:07 +0300
    message:
      Merge from dev tree.
        ------------------------------------------------------------
        revno: 2559.191.1
        committer: Alexey Kopytov <Alexey.Kopytov@sun.com>
        branch nick: mysql-5.0-bugteam
        timestamp: Tue 2009-02-10 15:38:56 +0300
        message:
          Fix for bug #41868: crash or memory overrun with concat + upper,
                              date_format functions
          
          String::realloc() did not check whether the existing string data fits in
          the newly allocated buffer for cases when reallocating a String object
          with external buffer (i.e.alloced == FALSE).  This could lead to memory
          overruns in some cases.
    ------------------------------------------------------------
    revno: 2559.157.23
    committer: Matthias Leich <Matthias.Leich@sun.com>
    branch nick: mysql-5.0-bugteam-push1
    timestamp: Fri 2009-02-13 13:55:29 +0100
    message:
      Merge actual tree -> local GCA tree, no conflicts
        ------------------------------------------------------------
        revno: 2559.188.5
        committer: Georgi Kodinov <joro@sun.com>
        branch nick: B33813-merge-5.0-bugteam
        timestamp: Thu 2009-02-12 16:39:33 +0200
        message:
          merged 5.0-bugteam to a working tree
            ------------------------------------------------------------
            revno: 2559.190.1
            committer: Sergey Vojtovich <svoj@mysql.com>
            branch nick: mysql-5.0-bugteam-bug36737
            timestamp: Thu 2009-02-12 13:49:44 +0400
            message:
              BUG#36737 - having + full text operator crashes mysql
                    
              MATCH() function accepts column list as an argument. It was possible to override
              this requirement with aliased non-column select expression. Which results in
              server crash.
              
              With this fix aliased non-column select expressions are not accepted by MATCH()
              function, returning an error.
        ------------------------------------------------------------
        revno: 2559.188.4
        committer: Georgi Kodinov <joro@sun.com>
        branch nick: B33813-merge-5.0-bugteam
        timestamp: Thu 2009-02-12 16:36:43 +0200
        message:
          Bug #33813: Schema names are case-sensitive in DROP FUNCTION
                
          Additional fix:
           1. Revert the unification of DROP FUNCTION
          and DROP PROCEDURE, because DROP FUNCTION can be used to
          drop UDFs (that have a non-qualified name and don't require
          database name to be present and valid).
           2. Fixed the case sensitivity problem by adding a call to 
          check_db_name() (similar to the sp_name production).
        ------------------------------------------------------------
        revno: 2559.188.3
        committer: Georgi Kodinov <joro@sun.com>
        branch nick: B33813-merge-5.0-bugteam
        timestamp: Thu 2009-02-12 11:27:06 +0200
        message:
          merged bug 33813 to 5.0-bugteam 
            ------------------------------------------------------------
            revno: 2559.189.1
            committer: Georgi Kodinov <joro@sun.com>
            branch nick: B33813-5.0-bugteam
            timestamp: Tue 2009-02-10 11:58:19 +0200
            message:
              Bug #33813: Schema names are case-sensitive in DROP FUNCTION
              
              The parser was not using the correct fully-qualified-name
              production for DROP FUNCTION.
              Fixed by copying the production from DROP PROCEDURE.
              Tested in the windows specific suite to make sure it's 
              tested on a case-insensitive file system.
        ------------------------------------------------------------
        revno: 2559.188.2
        committer: Georgi Kodinov <joro@sun.com>
        branch nick: B42433-5.0-bugteam
        timestamp: Tue 2009-02-10 20:19:03 +0200
        message:
          fixed a libedit compilation problem
        ------------------------------------------------------------
        revno: 2559.188.1
        committer: Georgi Kodinov <joro@sun.com>
        branch nick: B42433-5.0-bugteam
        timestamp: Tue 2009-02-10 14:39:14 +0200
        message:
          From jperkin :  Merge libedit 2.11 and related files, 
          based on NetBSD CVS as of 2009/02/06 20:09:00.
    ------------------------------------------------------------
    revno: 2559.157.22
    committer: Matthias Leich <Matthias.Leich@sun.com>
    branch nick: mysql-5.0-bugteam-42003-1
    timestamp: Mon 2009-02-09 21:52:40 +0100
    message:
      This belongs to the fix for
      Bug#42003 tests missing the disconnect of connections <> default
      second slice
      Content:
      1. wait_until_count_sessions.inc
         - One PB run of a test using this routine failed because
           5 seconds timeout were exceeded. Although I have some doubts
           if the assigned timeout was really too small, I increase the
           value to 10. We waste the additional 5 seconds only if the
           tests fails anyway.
         - Print the content of the PROCESSLIST if the poll routine fails
      2. minor improvements of formatting
      3. query_cache_notembedded:
         Activate the wait_until_count_sessions.inc routine which was
         unfortunately forgotten in the changeset before.
    ------------------------------------------------------------
    revno: 2559.157.21
    committer: Matthias Leich <Matthias.Leich@sun.com>
    branch nick: mysql-5.0-bugteam-42003-1
    timestamp: Mon 2009-02-09 12:44:01 +0100
    message:
      Merge of ifx into GCA tree
      no conflicts
        ------------------------------------------------------------
        revno: 2559.187.1
        committer: Matthias Leich <Matthias.Leich@sun.com>
        branch nick: mysql-5.0-bugteam-42003
        timestamp: Thu 2009-02-05 21:47:23 +0100
        message:
          2. Slice of fix for Bug#42003 tests missing the disconnect of connections <> default
             - If missing: add "disconnect <session>"
             - If physical disconnect of non "default" sessions is not finished
               at test end: add routine which waits till this happened
          + additional improvements
            - remove superfluous files created by the test
            - replace error numbers by error names
            - remove trailing spaces, replace tabs by spaces
            - unify writing of bugs within comments
            - correct comments
            - minor changes of formatting
          Fixed tests:
            backup
            check
            compress
            grant
            information_schema
            multi_update
            overflow
            packet
            query_cache_not_embedded
            sp-threads
            subselect
            synchronization
            timezone_grant
    ------------------------------------------------------------
    revno: 2559.157.20
    committer: Timothy Smith <timothy.smith@sun.com>
    branch nick: 50
    timestamp: Sat 2009-02-07 16:24:16 +0100
    message:
      Auto-merge 5.0-build -> 5.0-bugteam
        ------------------------------------------------------------
        revno: 2559.177.9
        committer: Joerg Bruehe <joerg@mysql.com>
        branch nick: push-5.0
        timestamp: Sat 2009-02-07 09:42:51 +0100
        message:
          Merge main 5.0 -> 5.0-build
            ------------------------------------------------------------
            revno: 2559.186.4
            author: 
            committer: MySQL Build Team <build@mysql.com>
            branch nick: mysql-5.0
            timestamp: Sat 2009-02-07 05:47:21 +0100
            message:
              Raise version number after cloning 5.0.78
            ------------------------------------------------------------
            revno: 2559.186.3
            tags: mysql-5.0.78, clone-5.0.78-build
            committer: Timothy Smith <timothy.smith@sun.com>
            branch nick: 50
            timestamp: Fri 2009-02-06 19:38:39 +0100
            message:
              Auto merge fix for Bug 42525 from 5.0-bugteam
            ------------------------------------------------------------
            revno: 2559.186.2
            committer: Timothy Smith <timothy.smith@sun.com>
            branch nick: 50
            timestamp: Fri 2009-02-06 15:51:36 +0100
            message:
              Auto merge from main 5.0
            ------------------------------------------------------------
            revno: 2559.186.1
            committer: Timothy Smith <timothy.smith@sun.com>
            branch nick: 50
            timestamp: Fri 2009-02-06 15:07:45 +0100
            message:
              Handle renamed nwbootstrap -> nwbuild
        ------------------------------------------------------------
        revno: 2559.177.8
        committer: Joerg Bruehe <joerg@mysql.com>
        branch nick: push-5.0
        timestamp: Fri 2009-02-06 21:58:08 +0100
        message:
          Merge main 5.0 into 5.0-build
            ------------------------------------------------------------
            revno: 2559.181.8
            committer: Georgi Kodinov <joro@sun.com>
            branch nick: merge-5.0-bugteam
            timestamp: Fri 2009-02-06 15:39:29 +0200
            message:
              merged 5.0-main -> 5.0-bugteam
            ------------------------------------------------------------
            revno: 2559.185.1
            committer: Georgi Kodinov <joro@sun.com>
            branch nick: merge-5.0-bugteam
            timestamp: Tue 2009-02-03 11:04:22 +0200
            message:
              changed the version in .bzr-mysql/default.conf
        ------------------------------------------------------------
        revno: 2559.177.7
        committer: Joerg Bruehe <joerg@mysql.com>
        branch nick: push-5.0
        timestamp: Fri 2009-02-06 21:25:04 +0100
        message:
          Final merge of 5.0.72sp1 into 5.0-build
          This involves just the tag, no file changes - they were all present before.
        ------------------------------------------------------------
        revno: 2559.177.6
        committer: Timothy Smith <timothy.smith@sun.com>
        branch nick: 50
        timestamp: Wed 2009-02-04 04:20:42 +0100
        message:
          The nwbootstrap script depended on BitKeeper, and was fairly complicated.  It's much
          simpler to just use the source .tar.gz to do a build.  So the script has been renamed
          to nwbuild, and simplified.
    ------------------------------------------------------------
    revno: 2559.157.19
    committer: Tatiana A. Nurnberg <azundris@mysql.com>
    branch nick: 50-42525
    timestamp: Fri 2009-02-06 18:47:54 +0100
    message:
      auto-merge
        ------------------------------------------------------------
        revno: 2559.181.7
        committer: Alexey Kopytov <Alexey.Kopytov@sun.com>
        branch nick: mysql-5.0-bugteam
        timestamp: Fri 2009-02-06 12:51:11 +0300
        message:
          Temporarily reverted patch for bug #41868 as it was causing problems in PB.
        ------------------------------------------------------------
        revno: 2559.181.6
        committer: Alexey Kopytov <Alexey.Kopytov@sun.com>
        branch nick: mysql-5.0-bugteam
        timestamp: Thu 2009-02-05 15:48:30 +0300
        message:
          Merge to team tree.
            ------------------------------------------------------------
            revno: 2559.184.2
            committer: Alexey Kopytov <Alexey.Kopytov@sun.com>
            branch nick: mysql-5.0-bugteam
            timestamp: Thu 2009-02-05 15:07:11 +0300
            message:
              Merge from team tree.
            ------------------------------------------------------------
            revno: 2559.184.1
            committer: Alexey Kopytov <Alexey.Kopytov@sun.com>
            branch nick: mysql-5.0-bugteam
            timestamp: Tue 2009-02-03 20:19:01 +0300
            message:
              Fix for bug #41868: crash or memory overrun with concat + upper, date_format
                                  functions
                    
              String::realloc() did not check whether the existing string data fits in the newly
              allocated buffer for cases when reallocating a String object with external buffer
              (i.e.alloced == FALSE).  This could lead to memory overruns in some cases.
        ------------------------------------------------------------
        revno: 2559.181.5
        committer: Gleb Shchepa <gshchepa@mysql.com>
        branch nick: mysql-5.0-bugteam
        timestamp: Thu 2009-02-05 13:30:39 +0400
        message:
          Bug #42037: Queries containing a subquery with DISTINCT and
                      ORDER BY could cause a server crash
          
          Dependent subqueries like
          
            SELECT COUNT(*) FROM t1, t2 WHERE t2.b
             IN (SELECT DISTINCT t2.b FROM t2 WHERE t2.b = t1.a)
          
          caused a memory leak proportional to the
          number of outer rows.
          
          
          The make_simple_join() function has been modified to
          JOIN class method to store join_tab_reexec and
          table_reexec values in the parent join only
          (make_simple_join of tmp_join may access these values
          via 'this' pointer of the parent JOIN).
          
          NOTE: this patch doesn't include standard test case (this is
          "out of memory" bug). See bug #42037 page for test cases.
        ------------------------------------------------------------
        revno: 2559.181.4
        committer: Ramil Kalimullin <ramil@mysql.com>
        branch nick: mysql-5.0-bugteam
        timestamp: Thu 2009-02-05 11:43:39 +0400
        message:
          Fix for bug#42014: Crash, name_const with collate
          
          Problem: some queries using NAME_CONST(.. COLLATE ...)
          lead to server crash due to failed type cast.
          
          Fix: return the underlying item's type in case of
          NAME_CONST(.. COLLATE ...) to avoid wrong casting.
        ------------------------------------------------------------
        revno: 2559.181.3
        committer: Chad MILLER <chad@mysql.com>
        branch nick: 5.0-bugteam
        timestamp: Wed 2009-02-04 13:57:33 -0500
        message:
          Merge from bug tree.
            ------------------------------------------------------------
            revno: 2559.183.1
            committer: Chad MILLER <chad@mysql.com>
            branch nick: 5.0-bugteam--bug32136
            timestamp: Wed 2008-11-26 10:51:59 -0500
            message:
              Bug#32136: mysqld_multi --defaults-file not respected while using \
                            --mysqld=mysqld_safe
              
              The server run didn't know the correct section to read in a
              configuration file, and would read from "[mysqld]" even though
              mysqld_multi had already read the defaults and made them into explicit
              parameters. 
              
              Worse, the "defaults-file" parameter says that it means "Read only
              this configuration file, do not read the standard system-wide and
              user-specific files", which should apply not only to mysql-multi, but
              to the server also.
              
              So, now if "defaults-file" is given, put "no-defaults" before all the
              explicit parameters we read from the defaults-file and feed to the
              mysqld or mysqld_safe.
        ------------------------------------------------------------
        revno: 2559.181.2
        committer: Matthias Leich <Matthias.Leich@sun.com>
        branch nick: mysql-5.0-bugteam-push
        timestamp: Wed 2009-02-04 16:34:28 +0100
        message:
          Merge last changesets into tree, no conflicts
            ------------------------------------------------------------
            revno: 2559.182.2
            committer: Sergey Vojtovich <svoj@mysql.com>
            branch nick: mysql-5.0-bugteam-bug32047
            timestamp: Wed 2009-02-04 15:46:23 +0400
            message:
              BUG#32047 - 'Spurious' errors while opening MERGE tables
              
              Accessing well defined MERGE table may return an error
              stating that the merge table is incorrectly defined. This
              happens if MERGE child tables were accessed before and we
              failed to open another incorrectly defined MERGE table in
              this connection.
              
              myrg_open() internally used my_errno as a variable for determining
              failure, and thus could be tricked into a wrong decision by other
              uses of my_errno.
              
              With this fix we use function local boolean flag instead of my_errno
              to determine failure.
            ------------------------------------------------------------
            revno: 2559.182.1
            committer: Patrick Crews <patrick.crews@sun.com>
            branch nick: mysql-5.0-bugteam
            timestamp: Mon 2009-02-02 17:30:02 -0500
            message:
              Bug#39369: execution of "variables.test" with "check-testcases" show differences.
              
              The original symptoms of this bug have been fixed as a consequence of other bug fixes.
              Taking this time to correct some formatting, such as replacing error numbers with names.
              Beginning this with 5.0
        ------------------------------------------------------------
        revno: 2559.181.1
        committer: Matthias Leich <Matthias.Leich@sun.com>
        branch nick: mysql-5.0-bugteam-42003
        timestamp: Mon 2009-02-02 22:20:25 +0100
        message:
          1. Slice of fix for Bug#42003 tests missing the disconnect of connections <> default
             - If missing: add "disconnect <session>"
             - If physical disconnect of non "default" sessions is not finished
               at test end: add routine which waits till this happened
          + additional improvements like
            - remove superfluous files created by the test
            - replace error numbers by error names
            - remove trailing spaces, replace tabs by spaces
            - unify writing of bugs within comments
            - correct comments
            - minor changes of formatting
          Modifications according to the code review are included.
          Fixed tests:
          grant2
          grant3
          lock_tables_lost_commit
          mysqldump
          openssl_1
          outfile
    ------------------------------------------------------------
    revno: 2559.157.18
    committer: Tatiana A. Nurnberg <azundris@mysql.com>
    branch nick: 50-42525
    timestamp: Fri 2009-02-06 18:25:08 +0100
    message:
      Bug#42525: TIMEDIFF function
      
      In 37553 we declared longlong results for
      class Item_str_timefunc as per comments/docs,
      but didn't add a method for that. And the
      default just wasn't good enough for some
      cases.
      
      Changeset adds dedicated val_int() to class.
    ------------------------------------------------------------
    revno: 2559.157.17
    committer: Tatiana A. Nurnberg <azundris@mysql.com>
    branch nick: 50-41370_
    timestamp: Sat 2009-01-31 02:07:36 +0100
    message:
      auto-merge
        ------------------------------------------------------------
        revno: 2559.180.1
        committer: Tatiana A. Nurnberg <azundris@mysql.com>
        branch nick: 50-41370
        timestamp: Fri 2009-01-30 17:12:24 +0100
        message:
          Bug#41370: TIMESTAMP field does not accepts NULL from FROM_UNIXTIME()
          
          When storing a NULL to a TIMESTAMP NOT NULL DEFAULT ...,
          NULL returned from some functions threw a 'cannot be NULL error.'
          
          NULL-returns now correctly result in the timestamp-field being
          assigned its default value.
    ------------------------------------------------------------
    revno: 2559.157.16
    committer: Georgi Kodinov <joro@sun.com>
    branch nick: merge-5.0-bugteam
    timestamp: Fri 2009-01-30 13:21:53 +0200
    message:
      merged 5.0-main -> 5.0-bugteam
        ------------------------------------------------------------
        revno: 2559.177.5
        committer: Joerg Bruehe <joerg@mysql.com>
        branch nick: push-5.0
        timestamp: Thu 2009-01-29 22:43:52 +0100
        message:
          Raise the version number in this (enterprise) tree, 5.0.77 will be a community build.
        ------------------------------------------------------------
        revno: 2559.177.4
        committer: Bjorn Munch <Bjorn.Munch@sun.com>
        branch nick: mysql-5.0-build
        timestamp: Wed 2009-01-28 14:44:22 +0100
        message:
          merge
            ------------------------------------------------------------
            revno: 2559.179.1
            committer: Bjorn Munch <Bjorn.Munch@sun.com>
            branch nick: 5.0-42216
            timestamp: Wed 2009-01-28 14:14:05 +0100
            message:
              Bug #42216 mysqltest: Use of diff belonging to current OS, with wrong option for Solaris
              Check for existence of diff fails on Solaris due to unsupported "-v"
              Fix is to do this check only on Windows where it was needed
        ------------------------------------------------------------
        revno: 2559.177.3
        committer: Kent Boortz <kent@kent-amd64>
        branch nick: mysql-5.0-build-bug42278
        timestamp: Fri 2009-01-23 02:59:03 +0100
        message:
          From 5.0.48 the NDB client libraries has been missing in the cluster
          packages, this is now corrected (Bug#42278)
    ------------------------------------------------------------
    revno: 2559.157.15
    committer: Georgi Kodinov <joro@sun.com>
    branch nick: B35396-merge-5.0-bugteam
    timestamp: Thu 2009-01-29 14:45:24 +0200
    message:
      merged 35396 to 5.0-bugteam
        ------------------------------------------------------------
        revno: 2559.174.8
        committer: Georgi Kodinov <joro@sun.com>
        branch nick: B35396-5.0-bugteam
        timestamp: Thu 2009-01-29 14:40:48 +0200
        message:
          Bug #35396: Abnormal query times in slow query log
                      
          If the system time is adjusted back during a query execution
          (resulting in the end time being earlier than the start time)
          the code that prints to the slow query log gets confused and 
          prints unsigned negative numbers.
                      
          Fixed by not logging the statements that would have negative
          execution time due to time shifts.
          No test case since this would involve changing the system time.
    ------------------------------------------------------------
    revno: 2559.157.14
    committer: Gleb Shchepa <gshchepa@mysql.com>
    branch nick: mysql-5.0-bugteam
    timestamp: Wed 2009-01-28 22:46:45 +0400
    message:
      Bug #39069: <row constructor> IN <table-subquery> seriously
                  messed up
      
      "ROW(...) IN (SELECT ... FROM DUAL)" always returned TRUE.
      
      Item_in_subselect::row_value_transformer rewrites "ROW(...)
      IN SELECT" conditions into the "EXISTS (SELECT ... HAVING ...)"
      form.
      For a subquery from the DUAL pseudotable resulting HAVING
      condition is an expression on constant values, so further
      transformation with optimize_cond() eliminates this HAVING
      condition and resets JOIN::having to NULL.
      Then JOIN::exec treated that NULL as an always-true-HAVING
      and that caused a bug.
      
      To distinguish an optimized out "HAVING TRUE" clause from
      "HAVING FALSE" we already have the JOIN::having_value flag.
      However, JOIN::exec() ignored JOIN::having_value as described
      above as if it always set to COND_TRUE.
      
      The JOIN::exec method has been modified to take into account
      the value of the JOIN::having_value field.
    ------------------------------------------------------------
    revno: 2559.157.13
    committer: Davi Arnaut <Davi.Arnaut@Sun.COM>
    branch nick: mysql-5.0-bugteam
    timestamp: Wed 2009-01-28 14:33:33 -0200
    message:
      Remove test case for bug 40264.
      Dirty close tricky does not work on Windows.
    ------------------------------------------------------------
    revno: 2559.157.12
    committer: Georgi Kodinov <joro@sun.com>
    branch nick: B42366-5.0-bugteam
    timestamp: Wed 2009-01-28 16:18:50 +0200
    message:
      Bug #42366: server-cert.pem expired: "Not After : Jan 27 08:54:13 2009 GMT"
            
      Re-generated the PKI files needed.
      Removed the ones that are not needed.
      Updated the tests to reference the correct SSL subject.
    ------------------------------------------------------------
    revno: 2559.157.11
    committer: Chad MILLER <chad@mysql.com>
    branch nick: mysql-5.0-bugteam
    timestamp: Mon 2009-01-26 12:34:55 -0500
    message:
      Merge from team tree.
        ------------------------------------------------------------
        revno: 2559.174.7
        committer: Davi Arnaut <Davi.Arnaut@Sun.COM>
        branch nick: 40264-5.0
        timestamp: Thu 2009-01-22 08:28:01 -0200
        message:
          Bug#40264: Aborted cached query causes query to hang indefinitely on next cache hit
          
          The problem is that the query cache was storing partial results
          if the statement failed when sending the results to the client.
          This could cause clients to hang when trying to read the results
          from the cache as they would, for example, wait indefinitely for
          a eof packet that wasn't saved.
          
          The solution is to always discard the caching of a query that
          failed to send its results to the associated client.
        ------------------------------------------------------------
        revno: 2559.174.6
        committer: Georgi Kodinov <joro@sun.com>
        branch nick: B38637-merge-5.0-bugteam
        timestamp: Fri 2009-01-16 16:48:41 +0200
        message:
          auto merge
            ------------------------------------------------------------
            revno: 2559.178.1
            committer: Georgi Kodinov <kgeorge@mysql.com>
            branch nick: B38637-5.0-bugteam
            timestamp: Fri 2008-10-17 13:55:16 +0300
            message:
              Bug #38637: COUNT DISTINCT prevents NULL testing in HAVING clause
              
              IS NULL was not checking the correct row in a HAVING context.
              At the first row of a new group (where the HAVING clause is evaluated)
              the column and SELECT list references in the HAVING clause should 
              refer to the last row of the previous group and not to the current one. 
              This was not done for IS NULL, because it was using Item::is_null() doesn't
              have a  Item_is_null_result() counterpart to access the data from the 
              last row of the previous group. Note that all the Item::val_xxx() functions 
              (e.g. Item::val_int()) have their _result counterparts (e.g. Item::val_int_result()).
              
              Fixed by implementing a is_null_result() (similarly to int_result()) and
              calling this instead of is_null() column and SELECT list references inside
              the HAVING clause.
        ------------------------------------------------------------
        revno: 2559.174.5
        committer: Georgi Kodinov <joro@sun.com>
        branch nick: merge-5.0-bugteam
        timestamp: Fri 2009-01-16 13:19:42 +0200
        message:
          merged 5.0-main -> 5.0-bugteam
            ------------------------------------------------------------
            revno: 2559.177.2
            committer: Joerg Bruehe <joerg@mysql.com>
            branch nick: push-5.0
            timestamp: Thu 2009-01-15 12:08:09 +0100
            message:
              Merge some tool fixes from the 5.0.72sp1 build back into the tree.
              
              This is not the final merge of that release build, but we need early
              access to these tool fixes (use of "awk" in the BDB configuration).
            ------------------------------------------------------------
            revno: 2559.177.1
            committer: Joerg Bruehe <joerg@mysql.com>
            branch nick: push-5.0
            timestamp: Thu 2009-01-15 11:48:31 +0100
            message:
              Merge the changes of the 5.0.66sp1 build back into the tree.
            ------------------------------------------------------------
            revno: 2559.103.8
            tags: mysql-5.0.66sp1
            author: Jonathan Perkin <jperkin@sun.com>
            committer: mysqldev <mysqldev@production.mysql.com>
            branch nick: mysql-5.0.66sp1-release
            timestamp: Thu 2008-10-23 21:46:46 +0200
            message:
              Revert part of last change, it was not related to a security fix.
            ------------------------------------------------------------
            revno: 2559.103.7
            author: Jonathan Perkin <jperkin@sun.com>
            committer: mysqldev <mysqldev@production.mysql.com>
            branch nick: mysql-5.0.66sp1-release
            timestamp: Thu 2008-10-23 19:39:56 +0200
            message:
              Merge fixes for bug#32167 and bug#37428 into 5.0.66sp1
            ------------------------------------------------------------
            revno: 2559.103.6
            author: Jonathan Perkin <jperkin@sun.com>
            committer: mysqldev <mysqldev@production.mysql.com>
            branch nick: mysql-5.0.66sp1-release
            timestamp: Thu 2008-10-23 19:36:48 +0200
            message:
              Merge fix for bug#38296 into 5.0.66sp1
            ------------------------------------------------------------
            revno: 2559.103.5
            author: Jonathan Perkin <jperkin@sun.com>
            committer: mysqldev <mysqldev@production.mysql.com>
            branch nick: mysql-5.0.66sp1-release
            timestamp: Thu 2008-10-23 19:04:52 +0200
            message:
              Raise version number for 5.0.66sp1
        ------------------------------------------------------------
        revno: 2559.174.4
        committer: Georgi Kodinov <joro@sun.com>
        branch nick: B38795-merge-5.0-bugteam
        timestamp: Thu 2009-01-15 16:15:38 +0200
        message:
          merged Bug 38795 to 5.0-bugteam
            ------------------------------------------------------------
            revno: 2559.176.1
            committer: Georgi Kodinov <joro@sun.com>
            branch nick: B38795-5.0-bugteam
            timestamp: Tue 2009-01-13 13:09:12 +0200
            message:
              Bug #38795: Automatic search depth and nested join's results in server crash
                    
              The greedy optimizer tracks the current level of nested joins and the position
              inside these by setting and maintaining a state that's global for the whole FROM
              clause.
              This state was correctly maintained inside the selection of the next partial plan
              table (in best_extension_by_limited_search()). 
              greedy_search() also moves the current position by adding the last partial match 
              table when there's not enough tables in the partial plan found by 
              best_extension_by_limited_search().
              This may require update of the global state variables that describe the current
              position in the plan if the last table placed by greedy_search is not a top-level 
              join table.
              Fixed by updating the state after placing the partial plan table in greedy_search()
              in the same way this is done on entering the best_extension_by_limited_search().
              Fixed the signature of the function called to update the state : 
              check_interleaving_with_nj
        ------------------------------------------------------------
        revno: 2559.174.3
        committer: Alexander Nozdrin <alik@sun.com>
        branch nick: 5.0-bugteam
        timestamp: Thu 2009-01-15 13:10:20 +0300
        message:
          Pull from 5.0-bugteam
            ------------------------------------------------------------
            revno: 2559.175.2
            committer: Davi Arnaut <Davi.Arnaut@Sun.COM>
            branch nick: 36326-5.0
            timestamp: Thu 2009-01-15 07:52:06 -0200
            message:
              Auto-merge from 5.1-bugteam
            ------------------------------------------------------------
            revno: 2559.175.1
            committer: Davi Arnaut <Davi.Arnaut@Sun.COM>
            branch nick: 36326-5.0
            timestamp: Tue 2009-01-13 20:07:06 -0200
            message:
              Bug#36326: nested transaction and select
              
              The problem is that the query cache stores packets containing
              the server status of the time when the cached statement was run.
              This might lead to a wrong transaction status in the client side
              if a statement is cached during a transaction and is later served
              outside a transaction context (and vice-versa).
              
              The solution is to take into account the transaction status when
              storing in and serving from the query cache.
        ------------------------------------------------------------
        revno: 2559.174.2
        committer: Alexander Nozdrin <alik@sun.com>
        branch nick: 5.0-bugteam-bug31222
        timestamp: Thu 2009-01-15 12:36:34 +0300
        message:
          Backport patch for Bug#31222 (com_% global status counters behave randomly
          with mysql_change_user) to 5.0.
        ------------------------------------------------------------
        revno: 2559.174.1
        committer: Georgi Kodinov <joro@sun.com>
        branch nick: merge-5.0-bugteam
        timestamp: Thu 2009-01-15 06:35:18 +0200
        message:
          merge 5.0-main to 5.0-bugteam
        ------------------------------------------------------------
        revno: 2559.173.2
        committer: MySQL Build Team <build@mysql.com>
        branch nick: mysql-5.0
        timestamp: Thu 2009-01-15 00:14:07 +0100
        message:
          Oops, bumped version too high.  Drop it back down from 5.0.78 to 5.0.77.
        ------------------------------------------------------------
        revno: 2559.173.1
        author: timothy.smith@sun.com
        committer: MySQL Build Team <build@mysql.com>
        branch nick: mysql-5.0
        timestamp: Wed 2009-01-14 20:16:10 +0100
        message:
          Raise version number after cloning 5.0.76
    ------------------------------------------------------------
    revno: 2559.157.10
    committer: Chad MILLER <chad@mysql.com>
    branch nick: mysql-5.0-bugteam
    timestamp: Wed 2009-01-14 11:15:11 -0500
    message:
      Merge from dev tree.
        ------------------------------------------------------------
        revno: 2559.145.6
        committer: Chad MILLER <chad@mysql.com>
        branch nick: mysql-5.0--bug38145
        timestamp: Wed 2009-01-14 11:11:31 -0500
        message:
          Bug#38145: .frm file isn't sync'd with sync_frm enabled
          
          Views weren't sync()d the same way other structures were.
          
          In creating the FRM for views, obey the same rules for variable 
          "sync_frm" as for everything else.
        ------------------------------------------------------------
        revno: 2559.145.5
        committer: Chad MILLER <chad@mysql.com>
        branch nick: mysql-5.0--bug38145
        timestamp: Wed 2009-01-14 11:10:36 -0500
        message:
          Fix comment.  Boolean function returns true/false, not zero/one.
    ------------------------------------------------------------
    revno: 2559.157.9
    committer: Tatiana A. Nurnberg <azundris@mysql.com>
    branch nick: 50-41470
    timestamp: Fri 2009-01-09 23:06:07 +0100
    message:
      auto-merge
        ------------------------------------------------------------
        revno: 2559.171.4
        committer: Georgi Kodinov <joro@sun.com>
        branch nick: B41437-merge-5.0-bugteam
        timestamp: Fri 2009-01-09 20:30:55 +0200
        message:
          fixed a compile warning
        ------------------------------------------------------------
        revno: 2559.171.3
        committer: Georgi Kodinov <joro@sun.com>
        branch nick: B41437-merge-5.0-bugteam
        timestamp: Fri 2009-01-09 17:08:42 +0200
        message:
          merged 41437 to 5.0-bugteam
        ------------------------------------------------------------
        revno: 2559.172.1
        committer: Georgi Kodinov <joro@sun.com>
        branch nick: B41437-5.0-bugteam
        timestamp: Fri 2009-01-09 13:50:18 +0200
        message:
          Bug #41437: Value stored in 'case' lacks charset, causes segfault
          
          When substituting system constant functions with a constant result
          the server was not expecting that the function may return NULL.
          Fixed by checking for NULL and returning Item_null (in the relevant
          collation) if the result of the system constant function was NULL.
    ------------------------------------------------------------
    revno: 2559.157.8
    committer: Tatiana A. Nurnberg <azundris@mysql.com>
    branch nick: 50-41470
    timestamp: Fri 2009-01-09 16:49:03 +0100
    message:
      auto-merge
        ------------------------------------------------------------
        revno: 2559.171.2
        committer: Patrick Crews <patrick.crews@sun.com>
        branch nick: mysql-5.0-new
        timestamp: Wed 2009-01-07 15:55:07 -0500
        message:
          merge
        ------------------------------------------------------------
        revno: 2559.171.1
        committer: Patrick Crews <patrick.crews@sun.com>
        branch nick: mysql-5.0-new
        timestamp: Mon 2009-01-05 12:10:22 -0500
        message:
          Bug#38833: mysql-test-run needs diff.  Problem w/ error handling in calling diff on Windows.
          
          Added function to check for diff and return an error message if the utility is not present.
          Previously, the way we did this didn't work on Windows, but did work on *Nix systems.
    ------------------------------------------------------------
    revno: 2559.157.7
    committer: Tatiana A. Nurnberg <azundris@mysql.com>
    branch nick: 50-41470
    timestamp: Thu 2009-01-08 10:25:31 +0100
    message:
      Bug#41470: DATE_FORMAT() crashes the complete server with a valid date
      
      Passing dubious "year zero" in non-zero date (not "0000-00-00") could
      lead to negative value for year internally, while variable was unsigned.
      This led to Really Bad Things further down the line.
      
      Now doing calculations with signed type for year internally.
------------------------------------------------------------
revno: 2587
tags: mysql-5.0.77
committer: Joerg Bruehe <joerg@mysql.com>
branch nick: community-5.0
timestamp: Wed 2009-01-28 15:01:04 +0100
message:
  Merge tool fixes which were done while building 5.0.72sp1
  (all connected with using Solaris to run the Bootstrap on)
  into the community tree.
  
  The other changes listed here are backports from 5.0.74
  which are in both the enterprise and the community tree already.
    ------------------------------------------------------------
    revno: 2559.156.9
    tags: mysql-5.0.72sp1
    committer: Joerg Bruehe <joerg@mysql.com>
    branch nick: clone-5.0.72sp1
    timestamp: Mon 2009-01-26 22:06:42 +0100
    message:
      Backport of a fix done by Kent for bug#42278
      into the 5.0.72sp1 branch.
      
      Original changeset (in the main 5.0 branch):
      > committer: Kent Boortz <kent@kent-amd64>
      > branch nick: mysql-5.0-build-bug42278
      > timestamp: Fri 2009-01-23 02:59:03 +0100
    ------------------------------------------------------------
    revno: 2559.156.8
    committer: Joerg Bruehe <joerg@mysql.com>
    branch nick: clone-5.0.72sp1
    timestamp: Tue 2009-01-13 14:52:22 +0100
    message:
      Tool fix, needed for "compile-dist" to succeed on Solaris:
      The default "awk" there cannot handle some of the scripts
      which are used by BDB for configuration.
      
      The fix:
      1) Introduce a variable "AWK" in some of the BDB shell scripts,
      2) search "gawk" and give it precedence over "awk"
         when assigning a value to the "AWK" variable,
         fail if neither is found,
      3) use that variable when calling an "awk" program with one
         of the critical scripts.
      
      The perfect solution would be to use the "awk" program found
      by "configure", but we cannot follow that approach because
      BDB's configuration is handled as a special case before the
      overall "configure" is run. Because of this,
      1) the "configure" result isn't yet available,
      2) "configure" will not handle these BDB files.
      Searching "gawk" is a (not-so-nice) way out.
      
      Note that all this need not be perfectly portable,
      it is needed only when we create a source distribution tarball
      from a develkopment tree.
    ------------------------------------------------------------
    revno: 2559.156.7
    tags: clone-5.0.72sp1-build
    committer: Joerg Bruehe <joerg@mysql.com>
    branch nick: clone-5.0.72sp1
    timestamp: Mon 2009-01-12 22:02:40 +0100
    message:
      Set the version: 5.0.72sp1
    ------------------------------------------------------------
    revno: 2559.156.6
    committer: Joerg Bruehe <joerg@mysql.com>
    branch nick: clone-5.0.72sp1
    timestamp: Mon 2009-01-12 17:40:29 +0100
    message:
      Backport of a 5.0.74 fix into 5.0.72sp1:
      
      Bug #39920: MySQL cannot deal with Leap Second expression in string literal.
      
      Updated MySQL time handling code to react correctly on UTC leap second additions.
      MySQL functions that return the OS current time, like e.g. CURDATE(), NOW() etc
      will return :59:59 instead of :59:60 or 59:61.
      As a result the reader will receive :59:59 for 2 or 3 consecutive seconds
      during the leap second.
      
      Original changesets:
      > revision-id: kgeorge@mysql.com-20081201141835-rg8nnnadujj5wl9f
      > parent: gshchepa@mysql.com-20081114172557-xh0jlzwal8ze3cy6
      > committer: Georgi Kodinov <kgeorge@mysql.com>
      > branch nick: B39920-5.0-bugteam
      > timestamp: Mon 2008-12-01 16:18:35 +0200
      
      > revision-id: kgeorge@mysql.com-20081201154106-c310zzy5or043rqa
      > parent: kgeorge@mysql.com-20081201145656-6kjq91oga5nxbbob
      > committer: Georgi Kodinov <kgeorge@mysql.com>
      > branch nick: B39920-merge-5.0-bugteam
      > timestamp: Mon 2008-12-01 17:41:06 +0200
    ------------------------------------------------------------
    revno: 2559.156.5
    committer: Joerg Bruehe <joerg@mysql.com>
    branch nick: clone-5.0.72sp1
    timestamp: Mon 2009-01-12 17:24:00 +0100
    message:
      Backport of a 5.0.74 fix into 5.0.72sp1:
      
      Bug#34760 Character set autodetection appears to fail
      the problem is the same as reported in bug#20835,
      so the fix is backport of bug#20835 patch.
      
      Original changeset:
      > revision-id: sergey.glukhov@sun.com-20081121123959-58ffhp2nitg7f40h
      > parent: ramil@mysql.com-20081120100836-gct60cm67b1rui29
      > committer: Sergey Glukhov <Sergey.Glukhov@sun.com>
      > branch nick: mysql-5.0-bugteam
      > timestamp: Fri 2008-11-21 16:39:59 +0400
    ------------------------------------------------------------
    revno: 2559.156.4
    committer: Joerg Bruehe <joerg@mysql.com>
    branch nick: clone-5.0.72sp1
    timestamp: Mon 2009-01-12 17:18:53 +0100
    message:
      Backport of a 5.0.74 fix into 5.0.72sp1:
      
      BUG#38842 - Fix for 25951 seems incorrect
      
      Original changeset:
      > revision-id: svoj@mysql.com-20081111091051-54pr96nf1z2s30gx
      > parent: vvaintroub@mysql.com-20081110201804-bi98gcs9avsf58ff
      > committer: Sergey Vojtovich <svoj@mysql.com>
      > branch nick: mysql-5.0-bugteam-bug38842
      > timestamp: Tue 2008-11-11 13:10:51 +0400
    ------------------------------------------------------------
    revno: 2559.156.3
    committer: Joerg Bruehe <joerg@mysql.com>
    branch nick: clone-5.0.72sp1
    timestamp: Mon 2009-01-12 17:09:03 +0100
    message:
      Backport of a 5.0.74 fix into 5.0.72sp1:
      
      Bug #40021: Renaming view fails, archived .frm for view is
                  missing after downgrade
      
      Original changeset:
      > revision-id: gshchepa@mysql.com-20081114172557-xh0jlzwal8ze3cy6
      > parent: ramil@mysql.com-20081114074229-vj4fvfrpmz8jfub9
      > committer: Gleb Shchepa <gshchepa@mysql.com>
      > branch nick: mysql-5.0-bugteam
      > timestamp: Fri 2008-11-14 21:25:57 +0400
    ------------------------------------------------------------
    revno: 2559.156.2
    committer: Joerg Bruehe <joerg@mysql.com>
    branch nick: clone-5.0.72sp1
    timestamp: Mon 2009-01-12 16:46:19 +0100
    message:
      Backport of a 5.0.74 fix into 5.0.72sp1:
      
      Remove bashisms from BUILD/compile-dist and configure.in,
      so Bootstrap works on Solaris box;
      - force GNU make in compile-dist;
      - remove unportable "grep -q" from configure.in
      
      Original changeset:
        revision-id: build@mysql.com-20081203041148-icwscut3bk09ds47
        parent: kgeorge@mysql.com-20081202125040-eiu6s7bk6s96s4xh
        author: timothy.smith@sun.com
        committer: MySQL Build Team <build@mysql.com>
        branch nick: mysql-5.0.74-release
        timestamp: Wed 2008-12-03 05:11:48 +0100
