------------------------------------------------------------
revno: 2800
tags: clone-5.0.84-build
committer: Georgi Kodinov <joro@sun.com>
branch nick: merge-5.0-bugteam
timestamp: Tue 2009-07-07 10:49:38 +0300
message:
  tree name change
------------------------------------------------------------
revno: 2799
committer: Georgi Kodinov <joro@sun.com>
branch nick: merge-5.0-bugteam
timestamp: Mon 2009-07-06 20:00:43 +0300
message:
  disable ndb_autodiscover2 : dependent on the disabled ndb_autodiscover
------------------------------------------------------------
revno: 2798
committer: Georgi Kodinov <joro@sun.com>
branch nick: merge-5.0-bugteam
timestamp: Mon 2009-07-06 17:44:25 +0300
message:
  Bug#45972: disable the test case in 5.0
------------------------------------------------------------
revno: 2797
committer: Georgi Kodinov <joro@sun.com>
branch nick: merge-5.0-bugteam
timestamp: Mon 2009-07-06 13:27:19 +0300
message:
  Bug #35148: ndb_autodiscover3 disabled
------------------------------------------------------------
revno: 2796
committer: Georgi Kodinov <joro@sun.com>
branch nick: merge-5.0-bugteam
timestamp: Mon 2009-07-06 13:23:35 +0300
message:
  Bug #35148: disabled testcase loaddata_autocom_ndb
------------------------------------------------------------
revno: 2795
committer: Georgi Kodinov <joro@sun.com>
branch nick: merge-5.0-bugteam
timestamp: Mon 2009-07-06 13:20:41 +0300
message:
  Bug #45521: disabled the test case
------------------------------------------------------------
revno: 2794
committer: Georgi Kodinov <joro@sun.com>
branch nick: merge-5.0-bugteam
timestamp: Mon 2009-07-06 13:15:40 +0300
message:
  Bug #38499 : test marked as a big test : takes approx 275 secs on a P4 2.4
  GHz.
------------------------------------------------------------
revno: 2793
committer: Georgi Kodinov <joro@sun.com>
branch nick: merge-5.0-bugteam
timestamp: Mon 2009-07-06 12:01:56 +0300
message:
  Bug#38315 and Bug#35148: disabled sporadically failing NDB tests 
------------------------------------------------------------
revno: 2792
committer: Sergey Glukhov <Sergey.Glukhov@sun.com>
branch nick: mysql-5.0-bugteam
timestamp: Fri 2009-07-03 13:35:00 +0500
message:
  Bug#45806 crash when replacing into a view with a join!
  The crash happend because for views which are joins
  we have table_list->table == 0 and 
  table_list->table->'any method' call leads to crash.
  The fix is to perform table_list->table->file->extra()
  method for all tables belonging to view.
------------------------------------------------------------
revno: 2791
committer: Bernt M. Johnsen <bernt.johnsen@sun.com>
branch nick: 5.0-bugteam
timestamp: Fri 2009-07-03 10:36:10 +0200
message:
  Prepare for push
    ------------------------------------------------------------
    revno: 2789.1.1
    committer: Bernt M. Johnsen <bernt.johnsen@sun.com>
    branch nick: 5.0-gca
    timestamp: Fri 2009-07-03 10:19:32 +0200
    message:
      Bug#15866 Prepared for push on 5.0
------------------------------------------------------------
revno: 2790
committer: Matthias Leich <Matthias.Leich@sun.com>
branch nick: mysql-5.0-bugteam-work
timestamp: Thu 2009-07-02 13:22:12 +0200
message:
  Fix for Bug#45902 rpl_sp fails sporadically in check testcases
  Details:
  - Add "sync_slave_with_master" at test end
  - Restore the initial value of log_bin_trust_function_creators
------------------------------------------------------------
revno: 2789
committer: Staale Smedseng <staale.smedseng@sun.com>
branch nick: 45790-50
timestamp: Wed 2009-07-01 14:09:44 +0200
message:
  Bug #45790 Potential DoS vector: Writing of user input to log
  without proper formatting
        
  The problem is that a suitably crafted database identifier
  supplied to COM_CREATE_DB or COM_DROP_DB can cause a SIGSEGV,
  and thereby a denial of service. The database name is printed
  to the log without using a format string, so potential
  attackers can control the behavior of my_b_vprintf() by
  supplying their own format string. A CREATE or DROP privilege
  would be required.
        
  This patch supplies a format string to the printing of the
  database name. A test case is added to mysql_client_test.
------------------------------------------------------------
revno: 2788
committer: Staale Smedseng <staale.smedseng@sun.com>
branch nick: 43414-50
timestamp: Mon 2009-06-29 15:17:01 +0200
message:
  Merge from 5.0-bt
------------------------------------------------------------
revno: 2787
committer: Satya B <satya.bn@sun.com>
branch nick: mysql-5.0-bugteam
timestamp: Mon 2009-06-29 17:57:22 +0530
message:
  Additional Fix for BUG#40565 - Update Query Results in "1 Row Affected" 
                                 But Should Be "Zero Rows"
  
  
  After applying the innodb snapshot 5.0-ss5406 for bug#40565, the windows push build
  tests failed because of the missing cast of void * pointer in row0sel.c file
  
  Informed the innodb developers and received patch by email.
------------------------------------------------------------
revno: 2786
committer: Alexey Kopytov <Alexey.Kopytov@Sun.com>
branch nick: mysql-5.0-bugteam
timestamp: Fri 2009-06-26 17:59:43 +0400
message:
  Automerge.
    ------------------------------------------------------------
    revno: 2777.1.1
    committer: Alexey Kopytov <Alexey.Kopytov@Sun.com>
    branch nick: my50-bug41710
    timestamp: Thu 2009-06-18 17:11:47 +0400
    message:
      Bug #41710: MySQL 5.1.30 crashes on the latest OpenSolaris 10 
       
      Change the default optimization level for Sun Studio to "-O1". 
      This is a workaround for a Sun Studio bug (see bug #41710 
      comments for details): 
       
      1. Use $GCC instead of $ac_cv_prog_gcc to check for gcc, since 
      the first one is the only documented way to do it. 
       
      2. Use $GXX instead of $ac_cv_prog_cxx_g to check for g++, 
      since the latter is set to "yes" when the C++ compiler accepts 
      "-g" which is the case for both g++ and CC. 
       
      3. When building with Sun Studio, set the default values for 
      CFLAGS/CXXFLAGS to "-O1", since unlike GCC, Sun Studio 
      interprets "-O" as "-xO3" (see the manual pages for cc and CC). 
------------------------------------------------------------
revno: 2785
committer: Satya B <satya.bn@sun.com>
branch nick: mysql-5.0-bugteam
timestamp: Thu 2009-06-25 15:20:26 +0530
message:
  Applying InnoDB snashot 5.0-ss5406, part 2. Fixes BUG#40565
  
  BUG#40565 - Update Query Results in "1 Row Affected" But Should Be "Zero Rows"
  
  Detailed revision comments:
  
  r5232 | marko | 2009-06-03 14:31:04 +0300 (Wed, 03 Jun 2009) | 21 lines
  branches/5.0: Merge r3590 from branches/5.1 in order to fix Bug #40565
  (Update Query Results in "1 Row Affected" But Should Be "Zero Rows").
  
  Also, add a test case for Bug #40565.
  
  rb://128 approved by Heikki Tuuri
    ------------------------------------------------------------------------
    r3590 | marko | 2008-12-18 15:33:36 +0200 (Thu, 18 Dec 2008) | 11 lines
  
    branches/5.1: When converting a record to MySQL format, copy the default
    column values for columns that are SQL NULL.  This addresses failures in
    row-based replication (Bug #39648).
  
    row_prebuilt_t: Add default_rec, for the default values of the columns in
    MySQL format.
  
    row_sel_store_mysql_rec(): Use prebuilt->default_rec instead of
    padding columns.
  
    rb://64 approved by Heikki Tuuri
    ------------------------------------------------------------------------
------------------------------------------------------------
revno: 2784
committer: Satya B <satya.bn@sun.com>
branch nick: mysql-5.0-bugteam
timestamp: Thu 2009-06-25 15:06:12 +0530
message:
  Applying InnoDB snashot 5.0-ss5406, part 1. Fixes BUG#38479
  
  BUG#38479 - valgrind warnings in show table status for innodb tables
  
  Detailed revision comments:
  
  r5080 | vasil | 2009-05-22 14:45:34 +0300 (Fri, 22 May 2009) | 6 lines
  branches/5.0:
  
  Fix Bug#38479 valgrind warnings in show table status for innodb tables
  
  by initializing prebuilt->hint_need_to_fetch_extra_cols.
------------------------------------------------------------
revno: 2783
committer: Georgi Kodinov <joro@sun.com>
branch nick: mysql-5.0-bugteam
timestamp: Mon 2009-06-22 14:50:46 +0300
message:
  automerge
    ------------------------------------------------------------
    revno: 2774.1.1
    committer: Georgi Kodinov <gkodinov@mysql.com>
    branch nick: merge-5.0-bugteam
    timestamp: Tue 2009-06-16 10:27:53 +0200
    message:
      fixed version
------------------------------------------------------------
revno: 2782
committer: Matthias Leich <Matthias.Leich@sun.com>
branch nick: mysql-5.0-bugteam-cs_coll
timestamp: Fri 2009-06-19 18:53:10 +0200
message:
  Merge of latest changes into local tree, no conflicts
    ------------------------------------------------------------
    revno: 2780.1.1
    committer: Georgi Kodinov <joro@sun.com>
    branch nick: B36654-5.0-bugteam
    timestamp: Fri 2009-06-19 15:52:20 +0300
    message:
      Bug #36654: mysqld_multi cannot start instances with different versions 
      occasionally.
      
      mysql_multi can call mysqld_safe. In doing this it's not changing the 
      current working directory. This may cause confusion in the case where 
      mysqld_multi is handling instances of servers of different versions 
      and the current working directory is the installation directory of one 
      of these servers.
      
      Fixed by enhancing the meaning of basedir in [mysqldN] sections of 
      mysqld_multi. If specified, mysqld_multi will change the current 
      working directory to the basedir directory before starting the server 
      in mysqld_multi ... start ... and then change it back to what it was.
------------------------------------------------------------
revno: 2781
committer: Matthias Leich <Matthias.Leich@sun.com>
branch nick: mysql-5.0-bugteam-cs_coll
timestamp: Fri 2009-06-19 17:21:20 +0200
message:
  Merge of fix for bug 40545, 40209, 40618, 38346 into tree
    ------------------------------------------------------------
    revno: 2728.4.1
    committer: Matthias Leich <Matthias.Leich@sun.com>
    branch nick: mysql-5.0-bugteam-ccs
    timestamp: Fri 2009-06-19 17:04:25 +0200
    message:
      Fix for Bug#40545, Bug#40209, Bug#40618, Bug#38346
      
        Details:
        - Limit the queries to character sets and collations
          which are most probably available in all build types.
          But try to preserve the intention of the tests.
        - Remove the variants adjusted to some build types.
      
        Note:
        1. The results of the review by Bar are included.
        2. I am not able to check the correctness of this patch
           on any existing build type and any MySQL version.
           So it could happen that the new test fails somewhere.
------------------------------------------------------------
revno: 2780
committer: V Narayanan<v.narayanan@sun.com>
branch nick: mysql-5.0-bugteam-43572-1
timestamp: Fri 2009-06-19 17:29:21 +0530
message:
  Bug#43572 Handle failures from hash_init
        
  Failure to allocate memory for the hash->array element,
  caused hash_init to return without initializing the other
  members of the hash. Thus although the dynamic array
  buffer may be allocated at a later point in the code, the
  incompletely initialized hash caused fatal failures.
  
  This patch moves the initialization of the other members
  of the hash above the array allocation, so that the usage
  of this hash will not result in fatal failures.
------------------------------------------------------------
revno: 2779
committer: Staale Smedseng <staale.smedseng@sun.com>
branch nick: 32223n-50
timestamp: Fri 2009-06-19 11:27:19 +0200
message:
  Bug #32223 SETting max_allowed_packet variable
        
  Inconsistent behavior of session variable max_allowed_packet 
  (and net_buffer_length); only assignment to the global variable 
  has any effect, without this being obvious to the user.
        
  The patch for Bug#22891 is backported to 5.0, making the two
  session variables read-only. As this is a backport to GA 
  software, the error used when trying to assign to the read-
  only variable is ER_UNKNOWN_ERROR. The error message is the 
  same as in 5.1+.
------------------------------------------------------------
revno: 2778
committer: Alfranio Correia <alfranio.correia@sun.com>
branch nick: mysql-5.0-bugteam-push
timestamp: Thu 2009-06-18 18:28:47 +0100
message:
  auto-merge mysql-5.0-bugteam (local) --> mysql-5.0-bugteam
    ------------------------------------------------------------
    revno: 2769.1.1
    committer: Alfranio Correia <alfranio.correia@sun.com>
    branch nick: mysql-5.0-bugteam
    timestamp: Thu 2009-06-11 02:08:40 +0100
    message:
      BUG#34687 Error in bin-log after shutdown restart binlog was not closed properly
      
      While reading a binary log that is being used by a master or was not properly
      closed, most likely due to a crash, the following warning message is being
      printed out: "Warning: this binlog was not closed properly. Most probably mysqld
      crashed writing it.". This was scaring our users as the message was not taking
      into account the possibility of the file is being just used by the master.
      
      To avoid unnecessarily scaring our users, we replace the original message by the
      following one: Warning: "this binlog is either is use or was not closed properly.".
------------------------------------------------------------
revno: 2777
committer: Alexey Kopytov <Alexey.Kopytov@Sun.com>
branch nick: mysql-5.0-bugteam
timestamp: Wed 2009-06-17 21:00:39 +0400
message:
  Automerge.
    ------------------------------------------------------------
    revno: 2775.1.1
    committer: Staale Smedseng <staale.smedseng@sun.com>
    branch nick: 43414-50
    timestamp: Wed 2009-06-17 15:54:01 +0200
    message:
      Bug #43414 Parenthesis (and other) warnings compiling MySQL 
      with gcc 4.3.2
            
      Compiling MySQL with gcc 4.3.2 and later produces a number of 
      warnings, many of which are new with the recent compiler
      versions.
                        
      This bug will be resolved in more than one patch to limit the
      size of changesets. This is the second patch, fixing more
      of the warnings.
------------------------------------------------------------
revno: 2776
committer: Alexey Kopytov <Alexey.Kopytov@Sun.com>
branch nick: mysql-5.0-bugteam
timestamp: Wed 2009-06-17 20:10:48 +0400
message:
  Disabled embedded server for the test case for bug #45236.
------------------------------------------------------------
revno: 2775
committer: Alexey Kopytov <Alexey.Kopytov@Sun.com>
branch nick: mysql-5.0-bugteam
timestamp: Wed 2009-06-17 16:36:45 +0400
message:
  Automerge.
    ------------------------------------------------------------
    revno: 2763.1.1
    committer: Alexey Kopytov <Alexey.Kopytov@Sun.com>
    branch nick: my50-bug45236
    timestamp: Wed 2009-06-10 11:24:47 +0400
    message:
      Bug #45236: large blob inserts from mysqldump fail, possible 
                  memory issue ? 
       
      The mysql command line client could misinterpret some character 
      sequences as commands under some circumstances. 
       
      The upper limit for internal readline buffer was raised to 1 GB 
      (the same as for server's max_allowed_packet) so that any input 
      line is processed by add_line() as a whole rather than in 
      chunks.
------------------------------------------------------------
revno: 2774
committer: Georgi Kodinov <gkodinov@mysql.com>
branch nick: merge-5.0-bugteam
timestamp: Mon 2009-06-15 17:58:23 +0200
message:
  automerge
    ------------------------------------------------------------
    revno: 2772.1.1
    committer: Bernt M. Johnsen <bernt.johnsen@sun.com>
    branch nick: 5.0-bugteam
    timestamp: Mon 2009-06-15 17:14:00 +0200
    message:
      Bug#32357 Prepared for push on 5.0-bugteam branch
------------------------------------------------------------
revno: 2773
committer: Georgi Kodinov <gkodinov@mysql.com>
branch nick: merge-5.0-bugteam
timestamp: Mon 2009-06-15 17:29:26 +0200
message:
  merged 5.0-main to 5.0-bugteam
    ------------------------------------------------------------
    revno: 2715.5.10
    committer: Joerg Bruehe <joerg@mysql.com>
    branch nick: push-5.0
    timestamp: Thu 2009-06-11 16:32:47 +0200
    message:
      Merge main 5.0 -> 5.0-build
        ------------------------------------------------------------
        revno: 2756.1.3
        author: Joerg.Bruehe@Sun.COM
        committer: MySQL Build Team <build@mysql.com>
        branch nick: mysql-5.0
        timestamp: Thu 2009-06-11 13:49:04 +0200
        message:
          Merge back mysql-5.0.74sp1-release, no changes in current files
            ------------------------------------------------------------
            revno: 2710.21.15
            tags: clone-5.0.74sp1-build, mysql-5.0.74sp1
            committer: Daniel Fischer <df@sun.com>
            branch nick: mysql-5.0-QSP
            timestamp: Thu 2009-04-30 15:38:00 +0200
            message:
              after-backport fixes
            ------------------------------------------------------------
            revno: 2710.21.14
            committer: Daniel Fischer <df@sun.com>
            branch nick: mysql-5.0-QSP
            timestamp: Thu 2009-04-30 13:53:30 +0200
            message:
              missing files for libedit
            ------------------------------------------------------------
            revno: 2710.21.13
            committer: Daniel Fischer <df@sun.com>
            branch nick: mysql-5.0-QSP
            timestamp: Thu 2009-04-30 13:38:10 +0200
            message:
              adjust version string
            ------------------------------------------------------------
            revno: 2710.21.12
            committer: Daniel Fischer <df@sun.com>
            branch nick: mysql-5.0-QSP
            timestamp: Thu 2009-04-30 13:35:25 +0200
            message:
              backport #34773, commit 61127
            ------------------------------------------------------------
            revno: 2710.21.11
            committer: Daniel Fischer <df@sun.com>
            branch nick: mysql-5.0-QSP
            timestamp: Thu 2009-04-30 13:14:37 +0200
            message:
              backport #39591, commit 59390
            ------------------------------------------------------------
            revno: 2710.21.10
            committer: Daniel Fischer <df@sun.com>
            branch nick: mysql-5.0-QSP
            timestamp: Thu 2009-04-30 13:03:29 +0200
            message:
              backport #41437, commit 62803
            ------------------------------------------------------------
            revno: 2710.21.9
            committer: Daniel Fischer <df@sun.com>
            branch nick: mysql-5.0-QSP
            timestamp: Thu 2009-04-30 12:57:03 +0200
            message:
              backport #41456, commit 61847
            ------------------------------------------------------------
            revno: 2710.21.8
            committer: Daniel Fischer <df@sun.com>
            branch nick: mysql-5.0-QSP
            timestamp: Thu 2009-04-30 12:52:45 +0200
            message:
              backport #41470, commit 62661
            ------------------------------------------------------------
            revno: 2710.21.7
            committer: Daniel Fischer <df@sun.com>
            branch nick: mysql-5.0-QSP
            timestamp: Thu 2009-04-30 12:45:37 +0200
            message:
              backport #42014, commit 65523
            ------------------------------------------------------------
            revno: 2710.21.6
            committer: Daniel Fischer <df@sun.com>
            branch nick: mysql-5.0-QSP
            timestamp: Thu 2009-04-30 12:42:50 +0200
            message:
              missing files from 42419
            ------------------------------------------------------------
            revno: 2710.21.5
            committer: Daniel Fischer <df@sun.com>
            branch nick: mysql-5.0-QSP
            timestamp: Thu 2009-04-30 12:38:22 +0200
            message:
              backport 42366, copying certificates from 5.0
            ------------------------------------------------------------
            revno: 2710.21.4
            committer: Daniel Fischer <df@sun.com>
            branch nick: mysql-5.0-QSP
            timestamp: Thu 2009-04-30 12:36:18 +0200
            message:
              backport #42419, commits 66925, 66999
            ------------------------------------------------------------
            revno: 2710.21.3
            committer: Daniel Fischer <df@sun.com>
            branch nick: mysql-5.0-QSP
            timestamp: Thu 2009-04-30 12:16:50 +0200
            message:
              backport #43748, applying commits 70359 and 70377
            ------------------------------------------------------------
            revno: 2710.21.2
            committer: Daniel Fischer <df@sun.com>
            branch nick: mysql-5.0-QSP
            timestamp: Thu 2009-04-30 12:04:37 +0200
            message:
              Backported libedit changes.
        ------------------------------------------------------------
        revno: 2756.1.2
        author: hery.ramilison@sun.com
        committer: MySQL Build Team <build@mysql.com>
        branch nick: mysql-5.0
        timestamp: Fri 2009-05-29 19:45:32 +0200
        message:
          Raise version number after cloning 5.0.83
    ------------------------------------------------------------
    revno: 2715.5.9
    committer: Joerg Bruehe <joerg@mysql.com>
    branch nick: push-5.0
    timestamp: Thu 2009-05-28 21:58:48 +0200
    message:
      Merge main 5.0 into 5.0-build
        ------------------------------------------------------------
        revno: 2756.1.1
        tags: mysql-5.0.83, clone-5.0.83-build
        committer: Georgi Kodinov <joro@sun.com>
        branch nick: merge-5.0-bugteam
        timestamp: Thu 2009-05-28 10:35:29 +0300
        message:
          changed the version
    ------------------------------------------------------------
    revno: 2715.5.8
    committer: Joerg Bruehe <joerg@mysql.com>
    branch nick: push-5.0
    timestamp: Wed 2009-05-27 09:49:26 +0200
    message:
      Merge main 5.0 -> 5.0-build
      
      This is the integration of the "community" source extensions
      into build calls for Windows and for RPMs.
    ------------------------------------------------------------
    revno: 2715.5.7
    committer: Joerg Bruehe <joerg@mysql.com>
    branch nick: push-5.0
    timestamp: Fri 2009-05-15 11:54:55 +0200
    message:
      Merge main 5.0 -> 5.0-build
    ------------------------------------------------------------
    revno: 2715.5.6
    committer: Daniel Fischer <df@sun.com>
    branch nick: mysql-5.0-build
    timestamp: Tue 2009-05-12 13:09:16 +0200
    message:
      merge bug#42888
        ------------------------------------------------------------
        revno: 2710.84.2
        committer: Daniel Fischer <df@sun.com>
        branch nick: mysql-5.0-build-42888
        timestamp: Tue 2009-02-24 14:54:04 +0100
        message:
          include collections in dist
        ------------------------------------------------------------
        revno: 2710.84.1
        committer: Daniel Fischer <df@sun.com>
        branch nick: mysql-5.0-build-42888
        timestamp: Tue 2009-02-24 11:42:11 +0100
        message:
          bug#42888: Add collections of test runs to make it both configurable and
          transparent what kinds of tests we run during integration testing.
    ------------------------------------------------------------
    revno: 2715.5.5
    committer: Kent Boortz <kent@kent-amd64>
    branch nick: mysql-5.0-build-bug44643
    timestamp: Sat 2009-05-09 23:43:48 +0200
    message:
      Use /usr/bin/perl as standard Perl install path (bug#44643)
------------------------------------------------------------
revno: 2772
committer: Georgi Kodinov <joro@sun.com>
branch nick: B44810-5.0-bugteam
timestamp: Mon 2009-06-15 16:38:15 +0300
message:
  Bug #44810: index merge and order by with low sort_buffer_size
  crashes server!
  
  The problem affects the scenario when index merge is followed by a filesort
  and the sort buffer is not big enough for all the sort keys.
  In this case the filesort function will read the data to the end through the 
  index merge quick access method (and thus closing the cursor etc), 
  but will leave the pointer to the quick select method in place.
  It will then create a temporary file to hold the results of the filesort and
  will add it as a sort output file (in sort.io_cache).
  Note that filesort will copy the original 'sort' structure in an automatic
  variable and restore it after it's done.
  As a result at exiting filesort() we have a sort.io_cache filled in and 
  nothing else (as a result of close of the cursors at end of reading data 
  through index merge).
  Now create_sort_index() will note that there is a select and will clean it up
  (as it's been used already by filesort() reading the data in). While doing that
  a special case in the index merge destructor will clean up the sort.io_cache,
  assuming it's an output of the index merge method and is not needed anymore.
  As a result the code that tries to read the data back from the filesort output 
  will get no data in both memory and disk and will crash.
        
  Fixed similarly to how filesort() does it : by copying the sort.io_cache structure
  to a local variable, removing the pointer to the io_cache (so that it's not freed 
  by QUICK_INDEX_MERGE_SELECT::~QUICK_INDEX_MERGE_SELECT) and restoring the original 
  structure (together with the valid pointer) after the cleanup is done.
  This is a safe thing to do because all the structures are already cleaned up by
  hitting the end of the index merge's read method (QUICK_INDEX_MERGE_SELECT::get_next()) 
  and the cleanup code being written in a way that tolerates repeating cleanups.
------------------------------------------------------------
revno: 2771
committer: Georgi Kodinov <joro@sun.com>
branch nick: B45386-5.0-bugteam
timestamp: Fri 2009-06-12 17:06:59 +0300
message:
  fixed the build-tags command
------------------------------------------------------------
revno: 2770
committer: Georgi Kodinov <joro@sun.com>
branch nick: B45386-5.0-bugteam
timestamp: Fri 2009-06-12 15:38:55 +0300
message:
  Bug #45386: Wrong query result with MIN function in field list, 
  WHERE and GROUP BY clause
  
  Loose index scan may use range conditions on the argument of 
  the MIN/MAX aggregate functions to find the beginning/end of 
  the interval that satisfies the range conditions in a single go.
  These range conditions may have open or closed minimum/maximum 
  values. When the comparison returns 0 (equal) the code should 
  check the type of the min/max values of the current interval 
  and accept or reject the row based on whether the limit is 
  open or not.
  There was a wrong composite condition on checking this and it was
  not working in all cases.
  Fixed by simplifying the conditions and reversing the logic.
------------------------------------------------------------
revno: 2769
committer: Davi Arnaut <Davi.Arnaut@Sun.COM>
branch nick: mysql-5.0-bugteam
timestamp: Wed 2009-06-10 10:59:59 -0300
message:
  Bug#41190: shared memory connections do not work in Vista, if server started from cmdline
  
  Backport to MySQL 5.0/1 fix by Vladislav Vaintroub:
  
  In Vista and later and also in when using terminal services, when
  server is started from  command line, client cannot connect to it
  via shared memory protocol.
  
  This is a regression introduced when  Bug#24731 was fixed.  The
  reason is that client is trying to attach to shared memory using
  global kernel object  namespace (all kernel objects are prefixed
  with Global\). However, server started from the command line in
  Vista and later will create shared memory and events using current
  session namespace. Thus, client is unable to find the server and
  connection fails.
  
  The fix for the client is to first try to find server using "local"
  names  (omitting Global\  prefix) and only if server is not found,
  trying global namespace.
------------------------------------------------------------
revno: 2768
committer: Staale Smedseng <staale.smedseng@sun.com>
branch nick: 43414-50
timestamp: Tue 2009-06-09 18:11:21 +0200
message:
  Bug #43414 Parenthesis (and other) warnings compiling MySQL 
  with gcc 4.3.2
        
  Compiling MySQL with gcc 4.3.2 and later produces a number of 
  warnings, many of which are new with the recent compiler
  versions.
        
  This bug will be resolved in more than one patch to limit the
  size of changesets. This is the first patch, fixing a number 
  of the warnings, predominantly "suggest using parentheses 
  around && in ||", and empty for and while bodies.
------------------------------------------------------------
revno: 2767
committer: Tatiana A. Nurnberg <azundris@mysql.com>
branch nick: 50-32149
timestamp: Sat 2009-06-06 18:06:42 +0200
message:
  auto-merge
    ------------------------------------------------------------
    revno: 2764.1.7
    committer: Davi Arnaut <Davi.Arnaut@Sun.COM>
    branch nick: mysql-5.0-bugteam
    timestamp: Sat 2009-06-06 12:26:39 -0300
    message:
      Don't mix declarations and code (not widely portable).
------------------------------------------------------------
revno: 2766
committer: Tatiana A. Nurnberg <azundris@mysql.com>
branch nick: 50-32149
timestamp: Fri 2009-06-05 23:29:37 +0200
message:
  auto-merge
    ------------------------------------------------------------
    revno: 2764.1.6
    committer: Georgi Kodinov <joro@sun.com>
    branch nick: B45286-5.0-bugteam
    timestamp: Fri 2009-06-05 19:27:48 +0300
    message:
      automerge
        ------------------------------------------------------------
        revno: 2764.3.1
        committer: Georgi Kodinov <joro@sun.com>
        branch nick: B43532-5.0-bugteam
        timestamp: Fri 2009-06-05 17:59:23 +0300
        message:
          Bug #43532 : backport of the 5.1 code to 5.0 mysqltest
    ------------------------------------------------------------
    revno: 2764.1.5
    committer: Georgi Kodinov <joro@sun.com>
    branch nick: B45286-5.0-bugteam
    timestamp: Fri 2009-06-05 19:23:44 +0300
    message:
      Addendum to Bug #45286 : implement reviewer's remarks.
    ------------------------------------------------------------
    revno: 2764.1.4
    committer: Georgi Kodinov <joro@sun.com>
    branch nick: B45286-5.0-bugteam
    timestamp: Fri 2009-06-05 18:14:56 +0300
    message:
      Bug #45286: compilation warnings on mysql-5.0-bugteam on MacOSX
      
      Implemented a way to circumvent the always true comparison by
      having nested macros (as suggested on review).
    ------------------------------------------------------------
    revno: 2764.1.3
    committer: Georgi Kodinov <joro@sun.com>
    branch nick: B45286-5.0-bugteam
    timestamp: Fri 2009-06-05 15:05:26 +0300
    message:
      Bug #45286: compilation warnings on mysql-5.0-bugteam on MacOSX
      
      Fixed the 5.0-bugteam MacOSX warnings.
    ------------------------------------------------------------
    revno: 2764.1.2
    committer: Bernt M. Johnsen <bernt.johnsen@sun.com>
    branch nick: 5.0-bugteam
    timestamp: Thu 2009-06-04 16:13:16 +0200
    message:
      Bug#15866 Split of main.sp and main.sp-fib. Merged from 5.0 gca
        ------------------------------------------------------------
        revno: 2764.2.1
        committer: Bernt M. Johnsen <bernt.johnsen@sun.com>
        branch nick: 5.0-gca
        timestamp: Thu 2009-06-04 13:38:53 +0200
        message:
          Bug#15866 main.sp-fib split from main.sp
    ------------------------------------------------------------
    revno: 2764.1.1
    committer: Georgi Kodinov <joro@sun.com>
    branch nick: B36995-5.0-bugteam
    timestamp: Thu 2009-06-04 12:52:40 +0300
    message:
      Bug #36995: valgrind error in remove_const during subquery executions
      
      When copying the Item class one must copy its attributes as well.
------------------------------------------------------------
revno: 2765
committer: Tatiana A. Nurnberg <azundris@mysql.com>
branch nick: 50-32149
timestamp: Fri 2009-06-05 00:23:08 +0200
message:
  Bug#32149: Long semaphore wait for adaptive hash latch
  
  Holding on to the temporary inno hash index latch is an optimization in
  many cases, but a pessimization in some others.
  
  Release temporary latches for those corner cases we (or rather, or customers,
  thanks!) have identified, that is, when we are about to do something that
  might take a really long time, like REPAIR or filesort.
------------------------------------------------------------
revno: 2764
committer: Sergey Glukhov <Sergey.Glukhov@sun.com>
branch nick: mysql-5.0-bugteam
timestamp: Thu 2009-06-04 10:28:45 +0500
message:
  Bug#44798 MySQL engine crashes when creating stored procedures with execute_priv=N
  The crash happens because of uninitialized
  lex->ssl_cipher, lex->x509_subject, lex->x509_issuer variables.
  The fix is to add initialization of these variables for
  stored procedures&functions.
------------------------------------------------------------
revno: 2763
committer: Sergey Glukhov <Sergey.Glukhov@sun.com>
branch nick: mysql-5.0-bugteam
timestamp: Tue 2009-06-02 11:38:13 +0500
message:
  Bug#45152 crash with round() function on longtext column in a derived table
  The crash happens due to wrong max_length value which is set on
  Item_func_round::fix_length_and_dec() stage. The value is set to
  args[0]->max_length which is too big in case of LONGTEXT(LONGBLOB) fields.
  The fix is to set max_length using float_length() function.
------------------------------------------------------------
revno: 2762
committer: Alexey Kopytov <Alexey.Kopytov@sun.com>
branch nick: mysql-5.0-bugteam
timestamp: Mon 2009-06-01 16:42:24 +0400
message:
  Automerge.
    ------------------------------------------------------------
    revno: 2747.2.1
    committer: Alexey Kopytov <Alexey.Kopytov@sun.com>
    branch nick: my50-bug44767
    timestamp: Wed 2009-05-27 14:20:57 +0400
    message:
      Bug #44767: invalid memory reads in password() and   
                  old_password() functions   
      The PASSWORD() and OLD_PASSWORD() functions could lead to   
      memory reads outside of an internal buffer when used with BLOB   
      arguments.   
        
      String::c_ptr() assumes there is at least one extra byte  
      in the internally allocated buffer when adding the trailing  
      '\0'.  This, however, may not be the case when a String object  
      was initialized with externally allocated buffer.  
        
      The bug was fixed by adding an additional "length" argument to  
      make_scrambled_password_323() and make_scrambled_password() in  
      order to avoid String::c_ptr() calls for  
      PASSWORD()/OLD_PASSWORD().  
        
      However, since the make_scrambled_password[_323] functions are  
      a part of the client library ABI, the functions with the new  
      interfaces were implemented with the 'my_' prefix in their  
      names, with the old functions changed to be wrappers around  
      the new ones to maintain interface compatibility.  
------------------------------------------------------------
revno: 2761
committer: He Zhenxing <zhenxing.he@sun.com>
branch nick: 5.0-bugteam
timestamp: Sun 2009-05-31 20:10:59 +0800
message:
  post fix of test result
------------------------------------------------------------
revno: 2760
committer: He Zhenxing <zhenxing.he@sun.com>
branch nick: 5.0-bugteam
timestamp: Sun 2009-05-31 17:16:12 +0800
message:
  Auto merge
    ------------------------------------------------------------
    revno: 2758.1.1
    committer: Davi Arnaut <Davi.Arnaut@Sun.COM>
    branch nick: 34309-5.0
    timestamp: Sat 2009-05-30 12:38:36 -0300
    message:
      MySQL 5.0 backport of Chad Miller's patch for Bug#34309:
      
      Bug#34309: '_PC' macro redefinition
      
      For reasons that are now a mystery, we had defined a CPP symbol to
      help ancient compilers work better (in some way that's lost to history).
      This interferes with at least one modern compiler.
      
      Now, don't define the _PC symbol.  Those other underscore-leading
      symbols are suspect also, but at least the names aren't inscrutable.
      Let's leave them for now.
------------------------------------------------------------
revno: 2759
committer: He Zhenxing <zhenxing.he@sun.com>
branch nick: 5.0-bugteam
timestamp: Sun 2009-05-31 11:26:58 +0800
message:
  BUG#43263 BEGIN skipped in some replicate-do-db cases
  
  BEGIN/COMMIT/ROLLBACK was subject to replication db rules, and
  caused the boundary of a transaction not recognized correctly 
  when these queries were ignored by the rules.
  
  Fixed the problem by skipping replication db rules for these
  statements.
------------------------------------------------------------
revno: 2758
committer: Sergey Glukhov <Sergey.Glukhov@sun.com>
branch nick: mysql-5.0-bugteam
timestamp: Thu 2009-05-28 16:19:49 +0500
message:
  test case fix
------------------------------------------------------------
revno: 2757
committer: Sergey Glukhov <Sergey.Glukhov@sun.com>
branch nick: mysql-5.0-bugteam
timestamp: Thu 2009-05-28 13:34:30 +0500
message:
  Bug#37268 'binary' character set makes CLI-internal commands case sensitive
  The fix is to use case insensitive collation
  for mysql client command search.
