------------------------------------------------------------
revno: 2738
committer: MySQL Build Team <build@mysql.com>
branch nick: mysql-5.1.31-release
timestamp: Mon 2009-01-19 17:48:05 +0100
message:
  Incorrect test if "--short-product-tag=" was given or not
------------------------------------------------------------
revno: 2737
committer: MySQL Build Team <build@mysql.com>
branch nick: mysql-5.1.31-release
timestamp: Sat 2009-01-17 09:29:40 +0100
message:
  Fixed typo
------------------------------------------------------------
revno: 2736
committer: MySQL Build Team <build@mysql.com>
branch nick: tsmith-5.1.31-b40386
timestamp: Fri 2009-01-16 15:04:11 +0100
message:
  Auto-merge
    ------------------------------------------------------------
    revno: 2734.1.1
    committer: MySQL Build Team <build@mysql.com>
    branch nick: mysql-5.1.31-release
    timestamp: Thu 2009-01-15 20:09:58 +0100
    message:
      Added option "--short-product-tag=<string>" to "make_binary_distribution.sh",
      to enable product name and server suffix to differ.
------------------------------------------------------------
revno: 2735
committer: MySQL Build Team <build@mysql.com>
branch nick: tsmith-5.1.31-b40386
timestamp: Thu 2009-01-15 21:16:18 +0100
message:
  Cherry-pick fix for bug#40386, "Not flushing query cache after truncate", out of 5.1-bugteam branch.
  
  This fix is r3114 from innodb-5.1-ss3603.
------------------------------------------------------------
revno: 2734
tags: clone-5.1.31-build
committer: Georgi Kodinov <joro@sun.com>
branch nick: merge-5.1-bugteam
timestamp: Thu 2009-01-15 07:31:47 +0200
message:
  merge 5.0-bugteam-> 5.1-bugteam
    ------------------------------------------------------------
    revno: 1810.3787.22
    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: 1810.3815.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: 1810.3815.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: 1810.3787.21
    committer: Tatiana A. Nurnberg <azundris@mysql.com>
    branch nick: 50-41470
    timestamp: Fri 2009-01-09 23:06:07 +0100
    message:
      auto-merge
    ------------------------------------------------------------
    revno: 1810.3787.20
    committer: Tatiana A. Nurnberg <azundris@mysql.com>
    branch nick: 50-41470
    timestamp: Fri 2009-01-09 16:49:03 +0100
    message:
      auto-merge
------------------------------------------------------------
revno: 2733
committer: Ramil Kalimullin <ramil@mysql.com>
branch nick: mysql-5.1-bugteam
timestamp: Thu 2009-01-15 00:54:25 +0400
message:
  bug#33094: Error in upgrading from 5.0 to 5.1 when table contains triggers
  
  Post-fix test failure: fixed mysqlcheck.test on Windows platforms.
------------------------------------------------------------
revno: 2732
committer: Chad MILLER <chad@mysql.com>
branch nick: mysql-5.1-bugteam
timestamp: Wed 2009-01-14 10:56:37 -0500
message:
  Merge from bugteam trunk.
    ------------------------------------------------------------
    revno: 2709.26.5
    committer: Ramil Kalimullin <ramil@mysql.com>
    branch nick: b33094-5.1-bugteam
    timestamp: Wed 2009-01-14 18:50:51 +0400
    message:
      Fix for
      bug#33094: Error in upgrading from 5.0 to 5.1 when table contains
      triggers
      and
      #41385: Crash when attempting to repair a #mysql50# upgraded table
      with triggers.
      
      Problem:
      1. trigger code didn't assume a table name may have
      a "#mysql50#" prefix, that may lead to a failing ASSERT().
      2. "ALTER DATABASE ... UPGRADE DATA DIRECTORY NAME" failed
      for databases with "#mysql50#" prefix if any trigger.
      3. mysqlcheck --fix-table-name didn't use UTF8 as a default
      character set that resulted in (parsing) errors for tables with
      non-latin symbols in their names and definitions of triggers.
      
      Fix:
      1. properly handle table/database names with "#mysql50#" prefix.
      2. handle --default-character-set mysqlcheck option;
      if mysqlcheck is launched with --fix-table-name or --fix-db-name
      set default character set to UTF8 if no --default-character-set
      option given.
      
      Note: if given --fix-table-name or --fix-db-name option,
      without --default-character-set mysqlcheck option
      default character set is UTF8.
    ------------------------------------------------------------
    revno: 2709.26.4
    committer: He Zhenxing <zhenxing.he@sun.com>
    branch nick: 5.1-bugteam
    timestamp: Wed 2009-01-14 17:32:25 +0800
    message:
      Auto merge
        ------------------------------------------------------------
        revno: 2730.1.1
        committer: Matthias Leich <Matthias.Leich@sun.com>
        branch nick: mysql-5.1-bugteam-push
        timestamp: Tue 2009-01-13 16:42:37 +0100
        message:
          Merge into actual tree
        ------------------------------------------------------------
        revno: 2728.2.4
        committer: Matthias Leich <Matthias.Leich@sun.com>
        branch nick: mysql-5.1-bugteam-combined1
        timestamp: Tue 2009-01-13 15:04:28 +0100
        message:
          Merge of fix for bug
             41776 type_date.test may fail if run around midnight.
          into GCA tree.
        ------------------------------------------------------------
        revno: 2728.2.3
        committer: Matthias Leich <Matthias.Leich@sun.com>
        branch nick: mysql-5.1-bugteam-combined1
        timestamp: Tue 2009-01-13 14:39:04 +0100
        message:
          Merge of fix for bug
             41111 events_bugs fails sporadically on pushbuild
          into GCA tree
            ------------------------------------------------------------
            revno: 2725.3.1
            committer: Matthias Leich <Matthias.Leich@sun.com>
            branch nick: mysql-5.1-bugteam-work1
            timestamp: Fri 2009-01-09 15:10:03 +0100
            message:
              1. Fix for Bug#41111 events_bugs fails sporadically on pushbuild
              2. Avoid bad effects of bug 41925 Warning 1366 Incorrect string value:
                                                ...  for column processlist.info
              3. Add poll routines which ensure that subtests meet stable scenarios.
                 This does not change the sense of the subtests.
        ------------------------------------------------------------
        revno: 2728.2.2
        committer: Matthias Leich <Matthias.Leich@sun.com>
        branch nick: mysql-5.1-bugteam-combined1
        timestamp: Tue 2009-01-13 14:26:24 +0100
        message:
          Merge of fix for bug
          41932 funcs_1: is_collation_character_set_applicability path too long for tar
          into GCA tree
            ------------------------------------------------------------
            revno: 2728.3.1
            committer: Matthias Leich <Matthias.Leich@sun.com>
            branch nick: mysql-5.1-bugteam-work2
            timestamp: Wed 2009-01-07 22:38:03 +0100
            message:
              Fix of Bug#41932 funcs_1: is_collation_character_set_applicability path too long for tar
        ------------------------------------------------------------
        revno: 2728.2.1
        committer: Matthias Leich <Matthias.Leich@sun.com>
        branch nick: mysql-5.1-bugteam-combined1
        timestamp: Tue 2009-01-13 14:09:24 +0100
        message:
          Fix for Bug#40377 sporadic pushbuild failure in log_state: result mismatch
          + add workaround for bug 38124
          + messages into the protocol when sessions are switched
          + replace error numbers by error names
          + reset of system variables to initial values per subtest
          + remove a file created by this test
          + minor improvements in structure and formatting
    ------------------------------------------------------------
    revno: 2709.26.3
    committer: He Zhenxing <zhenxing.he@sun.com>
    branch nick: 5.1-bugteam
    timestamp: Wed 2009-01-14 16:27:32 +0800
    message:
      BUG#41986 Replication slave does not pick up proper AUTO_INCREMENT value for Innodb tables
      
      The next number (AUTO_INCREMENT) field of the table for write
      rows events are not initialized, and cause some engines (innodb)
      not correctly update the tables's auto_increment value.
      
      This patch fixed this problem by honor next number fields if present.
------------------------------------------------------------
revno: 2731
committer: Chad MILLER <chad@mysql.com>
branch nick: mysql-5.1-bugteam
timestamp: Tue 2009-01-13 10:50:22 -0500
message:
  Merge fix for bug 38364.
    ------------------------------------------------------------
    revno: 2727.2.3
    committer: Chad MILLER <chad@mysql.com>
    branch nick: mysql-5.1-bugteam--bug38364
    timestamp: Mon 2009-01-12 14:48:02 -0500
    message:
      Bug#38364: gen_lex_hash segmentation fault in debug build
      Bug#36428: MY_MUTEX_INIT_FAST is used before initialization
      
      On some thread implementations, we need a fake mutex attri-
      bute as a placeholder, which we define as a global variable,
      "my_fast_mutexattr".  Well. that must be initialized before 
      used in any mutexes, and the ordering of initializations in 
      the API function  my_init()  was wrong.
      
      Now, put my_thread_global_init(), which initializes the attri-
      butes that mutexes require.
------------------------------------------------------------
revno: 2730
committer: Davi Arnaut <Davi.Arnaut@Sun.COM>
branch nick: 41889-5.1
timestamp: Tue 2009-01-13 13:06:31 -0200
message:
  Auto-merge from upstream 5.1-bugteam
    ------------------------------------------------------------
    revno: 2728.1.8
    committer: Patrick Crews <patrick.crews@sun.com>
    branch nick: mysql-5.1-binlog_bug
    timestamp: Mon 2009-01-12 18:45:35 -0500
    message:
      Bug#41888: Test binlog.binlog_database causing binlog_innodb to fail on Pushbuild.
      
      Added cleanup of status variables to the end of binlog_database.
      Re-recorded .result file to account for cleanup statement.
      NOTE:  binlog.binlog_innodb also has had an FLUSH STATUS; statement added to it as well, but
      adding this cleanup as a preventative measure.
    ------------------------------------------------------------
    revno: 2728.1.7
    committer: Georgi Kodinov <joro@sun.com>
    branch nick: B41543-merge-5.1-bugteam
    timestamp: Mon 2009-01-12 18:17:15 +0200
    message:
      Fixed a warning in sql_profile.cc
    ------------------------------------------------------------
    revno: 2728.1.6
    committer: Georgi Kodinov <joro@sun.com>
    branch nick: B41543-merge-5.1-bugteam
    timestamp: Mon 2009-01-12 17:52:46 +0200
    message:
      merged 41453 to 5.1-bugteam
        ------------------------------------------------------------
        revno: 2727.3.1
        committer: Georgi Kodinov <joro@sun.com>
        branch nick: B41543-5.1-bugteam
        timestamp: Fri 2009-01-09 14:04:47 +0200
        message:
          Bug #41543: Assertion `m_status == DA_ERROR' failed in Diagnostics_area::sql_errno
          
          No need to mask the error code returned by getting the next row to end of file when
          doing filesort.
    ------------------------------------------------------------
    revno: 2728.1.5
    committer: Davi Arnaut <Davi.Arnaut@Sun.COM>
    branch nick: mysql-5.1-bugteam
    timestamp: Mon 2009-01-12 10:48:33 -0200
    message:
      Post-merge fix for bug 37016: Update test case for row-based logging.
    ------------------------------------------------------------
    revno: 2728.1.4
    committer: Tatiana A. Nurnberg <azundris@mysql.com>
    branch nick: 51-31177v2
    timestamp: Mon 2009-01-12 06:32:49 +0100
    message:
      Bug#31177: Server variables can't be set to their current values
      
      Bounds-checks and blocksize corrections were applied to user-input,
      but constants in the server were trusted implicitly. If these values
      did not actually meet the requirements, the user could not set change
      a variable, then set it back to the (wonky) factory default or maximum
      by explicitly specifying it (SET <var>=<value> vs SET <var>=DEFAULT).
      
      Now checks also apply to the server's presets. Wonky values and maxima
      get corrected at startup. Consequently all non-offsetted values the user
      sees are valid, and users can set the variable to that exact value if
      they so desire.
    ------------------------------------------------------------
    revno: 2728.1.3
    committer: Tatiana A. Nurnberg <azundris@mysql.com>
    branch nick: 51-41470
    timestamp: Fri 2009-01-09 22:26:51 +0100
    message:
      auto-merge
        ------------------------------------------------------------
        revno: 2725.2.4
        committer: Georgi Kodinov <joro@sun.com>
        branch nick: B41437-merge-5.1-bugteam
        timestamp: Fri 2009-01-09 20:35:02 +0200
        message:
          merged 5.0-bugteam -> 5.1-bugteam
            ------------------------------------------------------------
            revno: 1810.3813.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: 2725.2.3
        committer: Georgi Kodinov <joro@sun.com>
        branch nick: B41437-merge-5.1-bugteam
        timestamp: Fri 2009-01-09 19:51:52 +0200
        message:
          merged 41437 to 5.1-bugteam
            ------------------------------------------------------------
            revno: 1810.3813.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: 1810.3814.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: 1810.3813.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: 2725.2.2
        committer: Mattias Jonsson <mattias.jonsson@sun.com>
        branch nick: topush-51-bugteam
        timestamp: Fri 2009-01-09 14:21:29 +0100
        message:
          merge
        ------------------------------------------------------------
        revno: 2725.2.1
        committer: Mattias Jonsson <mattias.jonsson@sun.com>
        branch nick: topush-51-bugteam
        timestamp: Fri 2009-01-09 14:18:08 +0100
        message:
          Bug#40972: Partition pruning can lead to crash for bad dates
          
          post push fix, added test found a valgrind warning
    ------------------------------------------------------------
    revno: 2728.1.2
    committer: Tatiana A. Nurnberg <azundris@mysql.com>
    branch nick: 51-41470
    timestamp: Fri 2009-01-09 16:48:02 +0100
    message:
      auto-merge
        ------------------------------------------------------------
        revno: 2725.1.4
        committer: Sven Sandberg <sven@mysql.com>
        branch nick: 5.1-bugteam
        timestamp: Fri 2009-01-09 13:49:24 +0100
        message:
          BUG#41924: high-level replication functions are not commented
          Adding comments to some of the high-level functions in replication.
        ------------------------------------------------------------
        revno: 2725.1.3
        committer: Sven Sandberg <sven@mysql.com>
        branch nick: 5.1-bugteam
        timestamp: Fri 2009-01-09 11:37:08 +0100
        message:
          Merged fix of BUG#41961 in 5.1-bugteam with recent changes in 5.1-bugteam
            ------------------------------------------------------------
            revno: 2727.1.8
            committer: Davi Arnaut <Davi.Arnaut@Sun.COM>
            branch nick: 37016-5.1
            timestamp: Fri 2009-01-09 08:20:32 -0200
            message:
              Bug#37016: TRUNCATE TABLE removes some rows but not all
              
              The special TRUNCATE TABLE (DDL) transaction wasn't being properly
              rolled back if a error occurred during row by row deletion. The
              error can be caused by a foreign key restriction imposed by InnoDB
              SE and would cause the server to erroneously issue a implicit
              commit.
              
              The solution is to rollback the transaction if a truncation via row
              by row deletion fails, otherwise commit. All effects of a TRUNCATE 
              ABLE operation are rolled back if a row by row deletion fails.
        ------------------------------------------------------------
        revno: 2725.1.2
        committer: Sven Sandberg <sven@mysql.com>
        branch nick: 5.1-bugteam
        timestamp: Fri 2009-01-09 11:35:26 +0100
        message:
          merge fix of BUG#41961 in 5.1-bugteam with recent changes in 5.1-bugteam
            ------------------------------------------------------------
            revno: 2727.1.7
            committer: Horst Hunger <horst@mysql.com>
            branch nick: mysql-5.1-36875
            timestamp: Fri 2009-01-09 10:25:02 +0100
            message:
              due to merge.
                ------------------------------------------------------------
                revno: 2727.2.2
                committer: Davi Arnaut <Davi.Arnaut@Sun.COM>
                branch nick: 41348-5.1
                timestamp: Thu 2009-01-08 16:28:30 -0200
                message:
                  Auto-merge from upstream 5.1-bugteam
                ------------------------------------------------------------
                revno: 2727.2.1
                committer: Davi Arnaut <Davi.Arnaut@Sun.COM>
                branch nick: 41348-5.1
                timestamp: Wed 2009-01-07 10:11:37 -0200
                message:
                  Bug#41348: INSERT INTO tbl SELECT * FROM temp_tbl overwrites
                             locking type of temp table
                  
                  The problem is that INSERT INTO .. SELECT FROM .. and CREATE
                  TABLE .. SELECT FROM a temporary table could inadvertently
                  overwrite the locking type of the temporary table. The lock
                  type of temporary tables should be a write lock by default.
                  
                  The solution is to reset the lock type of temporary tables
                  back to its default value after they are used in a statement.
            ------------------------------------------------------------
            revno: 2727.1.6
            committer: Horst Hunger <horst@mysql.com>
            branch nick: mysql-5.1-36875
            timestamp: Thu 2009-01-08 19:13:57 +0100
            message:
              Patch for bug#36875: Inserted review results.
            ------------------------------------------------------------
            revno: 2727.1.5
            committer: Mattias Jonsson <mattias.jonsson@sun.com>
            branch nick: topush-51-bugteam
            timestamp: Thu 2009-01-08 11:17:21 +0100
            message:
              merge
                ------------------------------------------------------------
                revno: 2709.26.2
                committer: Timothy Smith <timothy.smith@sun.com>
                branch nick: 51
                timestamp: Thu 2009-01-08 03:16:22 +0100
                message:
                  Auto-merge from upstream 5.1-bugteam
                ------------------------------------------------------------
                revno: 2709.26.1
                committer: Timothy Smith <timothy.smith@sun.com>
                branch nick: 51
                timestamp: Thu 2009-01-08 03:06:54 +0100
                message:
                  Fix a few problems after latest bunch of InnoDB snapshot changes:
                  
                  The binlog_innodb test was sensitive to what tests ran before it.  Now run
                  FLUSH STATUS before performing operations that need to be checked.
                  
                  sys_var_thd_ulong::update() was improperly casting an option value from
                  ulonglong to ulong before comparing it to the max allowed value.  On systems
                  where ulong and ulonglong are of different size, this caused values greater
                  than ULONG_MAX to wrap around (not be truncated to ULONG_MAX, which appears to
                  have been the intention of the original coder), and caused some checks to work
                  incorrectly.  This wasn't generally visible to the user, because later checks
                  would prevent the wrapped-around value from being used.  But it caused warning
                  messages to differ between 32- and 64-bit platforms.  Fix is to just remove the
                  cast.  Also added a DBUG_ASSERT to ensure that the value really is capped
                  properly before finally stuffing it into the ulong.
            ------------------------------------------------------------
            revno: 2727.1.4
            committer: Mattias Jonsson <mattias.jonsson@sun.com>
            branch nick: topush-51-bugteam
            timestamp: Wed 2009-01-07 23:30:10 +0100
            message:
              merge
                ------------------------------------------------------------
                revno: 2709.25.1
                committer: Mattias Jonsson <mattias.jonsson@sun.com>
                branch nick: b36312-51-bugteam
                timestamp: Fri 2008-12-19 09:23:15 +0100
                message:
                  Bug#36312: InnoDB DATA_FREE BUG?
                  
                  Problem is that DATA_FREE in SHOW TABLE STATUS
                  is not correct when not using innodb_file_per_table.
                  
                  The solution is to use I_S.PARTITIONS instead.
                  
                  This is only a small fix for correcting mean record length and
                  always return 0 if the table is empty.
            ------------------------------------------------------------
            revno: 2727.1.3
            committer: Mattias Jonsson <mattias.jonsson@sun.com>
            branch nick: topush-51-bugteam
            timestamp: Wed 2009-01-07 23:28:49 +0100
            message:
              merge
                ------------------------------------------------------------
                revno: 2709.24.1
                committer: Mattias Jonsson <mattias.jonsson@sun.com>
                branch nick: b40972-51-bugteam
                timestamp: Sun 2008-12-28 12:33:49 +0100
                message:
                  Bug#40972: some sql execution lead the whole databse crashing
                  
                  Problem was an errornous date that lead to end partition
                  was before the start, leading to a crash.
                  
                  Solution was to check greater or equal instead of only
                  equal between start and end partition.
                  
                  NOTE: partitioning pruning handles incorrect dates
                  differently than index lookup, which can give different
                  results in a partitioned table versus a non partitioned
                  table for queries having 'bad' dates in the where clause.
            ------------------------------------------------------------
            revno: 2727.1.2
            committer: Patrick Crews <patrick.crews@sun.com>
            branch nick: mysql-5.1-bugteam
            timestamp: Wed 2009-01-07 15:52:15 -0500
            message:
              merge
            ------------------------------------------------------------
            revno: 2727.1.1
            committer: Patrick Crews <patrick.crews@sun.com>
            branch nick: mysql-5.1-bugteam
            timestamp: Mon 2009-01-05 17:25:03 -0500
            message:
              merge 5.0 -> 5.1
            ------------------------------------------------------------
            revno: 1810.3813.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: 2725.1.1
        committer: Sven Sandberg <sven@mysql.com>
        branch nick: 5.1-bugteam
        timestamp: Fri 2009-01-09 10:48:01 +0100
        message:
          BUG#41961: Some log_event types do not skip post-header when reading
          Problem: when the server reads a log_event from file, it should read
          the post-header lengths from the format_description_log_event. Some
          event types which currently have post-header length 0 did not do this,
          and instead had a hard-coded zero length for the post-header. That
          means the current server version will not be able to read future
          versions of these events.
          Fix: make the reader functions read the post-header.
    ------------------------------------------------------------
    revno: 2728.1.1
    committer: Tatiana A. Nurnberg <azundris@mysql.com>
    branch nick: 51-41470
    timestamp: Fri 2009-01-09 14:22:15 +0100
    message:
      auto-merge
    ------------------------------------------------------------
    revno: 1810.3787.19
    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: 2729
committer: Davi Arnaut <Davi.Arnaut@Sun.COM>
branch nick: 41889-5.1
timestamp: Thu 2009-01-08 10:31:34 -0200
message:
  Bug#41889: Test main.innodb_bug38231 is failing w/embedded server (server crash)
  
  The problem is that a mysql connection instance is not thread-safe
  and reentrant, meaning that it can't be used concurrently and can't
  be re-entered while it's already running. This applies for any form
  of the server (embedded or not), but this rule can be violated in a
  test case if the test sends a new command without waiting for the
  result of previous command that was sent asynchronously and this can
  lead to hangs when over a network or to crashes under embedded server
  as the server query execution path will be re-entered concurrently
  with the same connection structure.
  
  The solution is to rework the test case so that the aforementioned
  rule is obeyed.
------------------------------------------------------------
revno: 2728
committer: Vladislav Vaintroub <vvaintroub@mysql.com>
branch nick: mysql-5.1-bugteam
timestamp: Wed 2009-01-07 13:44:32 +0100
message:
   fix misspelling
------------------------------------------------------------
revno: 2727
committer: Georgi Kodinov <joro@sun.com>
branch nick: fix-5.1-bugteam
timestamp: Mon 2009-01-05 20:47:28 +0200
message:
  merged 5.0-bugteam -> 5.1-bugteam
    ------------------------------------------------------------
    revno: 1810.3787.18
    tags: clone-5.0.76-build
    committer: Georgi Kodinov <joro@sun.com>
    branch nick: fix-5.0-bugteam
    timestamp: Mon 2009-01-05 18:04:14 +0200
    message:
      merge 5.0 -> 5.0-bugteam
    ------------------------------------------------------------
    revno: 1810.3787.17
    committer: Georgi Kodinov <kgeorge@mysql.com>
    branch nick: fix-5.0-bugteam
    timestamp: Mon 2009-01-05 12:37:56 +0200
    message:
      Reverted the fix for bug #25830 because of omissions and non-complete test
      case.
------------------------------------------------------------
revno: 2726
committer: Georgi Kodinov <joro@sun.com>
branch nick: fix-5.1-bugteam
timestamp: Mon 2009-01-05 18:10:20 +0200
message:
  merged 5.1-main -> 5.1-bugteam
    ------------------------------------------------------------
    revno: 2646.31.9
    committer: Joerg Bruehe <joerg@mysql.com>
    branch nick: push-5.1
    timestamp: Sun 2008-12-28 16:18:08 +0100
    message:
      Merge the bashism removal from 5.0 up to 5.1-build
        ------------------------------------------------------------
        revno: 1810.3769.20
        committer: Joerg Bruehe <joerg@mysql.com>
        branch nick: push-5.0
        timestamp: Sun 2008-12-28 14:34:58 +0100
        message:
          Merge from main 5.0 tree (includes 5.0.74), in preparation for pushing back.
        ------------------------------------------------------------
        revno: 1810.3812.1
        committer: Joerg Bruehe <joerg@mysql.com>
        branch nick: mysql-5.0
        timestamp: Wed 2008-12-17 19:55:08 +0100
        message:
          Merge the 5.0.74 build into the main tree.
        ------------------------------------------------------------
        revno: 1810.3811.1
        tags: mysql-5.0.74
        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
        message:
          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
    ------------------------------------------------------------
    revno: 2646.31.8
    committer: Kent Boortz <kent@kent-amd64>
    branch nick: mysql-5.1-build
    timestamp: Sun 2008-12-28 08:03:44 +0100
    message:
      Merge
        ------------------------------------------------------------
        revno: 1810.3769.19
        committer: Kent Boortz <kent@kent-amd64>
        branch nick: mysql-5.0-build
        timestamp: Sun 2008-12-28 07:57:09 +0100
        message:
          Increased thread stack size to 128K, as this is the minimum (Bug#41577)
    ------------------------------------------------------------
    revno: 2646.31.7
    committer: Kent Boortz <kent@kent-amd64>
    branch nick: mysql-5.1-build
    timestamp: Sun 2008-12-28 08:00:23 +0100
    message:
      Make sure cluster builds include all charsets
    ------------------------------------------------------------
    revno: 2646.31.6
    committer: Bjorn Munch <Bjorn.Munch@sun.com>
    branch nick: mysql-5.1-build
    timestamp: Mon 2008-12-15 15:14:56 +0100
    message:
      Bug #31983 Running mysql-test from RPM fails for NDB
      Adds $glob_basedir/sbin to search path when needed
        ------------------------------------------------------------
        revno: 1810.3769.18
        committer: Bjorn Munch <Bjorn.Munch@sun.com>
        branch nick: mysql-5.0-build
        timestamp: Fri 2008-12-12 15:10:56 +0100
        message:
          Bug #31983 Running mysql-test from RPM fails for NDB
          Added $glob_basedir/sbin to search path for relevant binaries
        ------------------------------------------------------------
        revno: 1810.3769.17
        committer: Joerg Bruehe <joerg@mysql.com>
        branch nick: push-5.0
        timestamp: Thu 2008-12-04 14:43:48 +0100
        message:
          Merge main 5.0 to 5.0-build
    ------------------------------------------------------------
    revno: 2646.31.5
    committer: Joerg Bruehe <joerg@mysql.com>
    branch nick: push-5.1
    timestamp: Wed 2008-12-10 21:14:50 +0100
    message:
      Merge main 5.1 into 5.1-build
    ------------------------------------------------------------
    revno: 2646.31.4
    author: timothy.smith@sun.com
    committer: Build Team <bteam@astra04>
    branch nick: mysql-5.1-build
    timestamp: Thu 2008-11-27 00:02:10 +0100
    message:
      Merge from mysql-5.1.30-release
    ------------------------------------------------------------
    revno: 2661.92.6
    committer: Build Team <bteam@astra04>
    branch nick: mysql-5.1.30-release
    timestamp: Tue 2008-11-25 03:04:58 +0100
    message:
      mysql-test/r/partition.result
      mysql-test/t/partition.test
      sql/ha_partition.cc
        Bug#40954: Crash in MyISAM index code with concurrency test using partitioned tables
        Problem was usage of read_range_first with an empty key.
        Solution was to not to give a key if it was empty. (real author Mattias Jonsson)
      
      storage/archive/archive_reader.c
      client/mysqlslap.c
        Aligned the copyright texts output from "--version" of tools, to
        let internal tools be able to change them if needed.
      
      storage/ndb/test/tools/connect.cpp
      storage/ndb/test/run-test/atrt.hpp
        Corrected a few GPL headers not restricted to GPL version 2
      
      Makefile.am
        Added missing --report-features to the 'test-bt-fast' target
      
      support-files/mysql.spec.sh
        Reversed the removal of the "%define license GPL" in as internal
        tools depended on it
    ------------------------------------------------------------
    revno: 2661.92.5
    tags: mysql-5.1.30
    author: kent.boortz@sun.com
    committer: Build Team <bteam@astra04>
    branch nick: mysql-5.1.30-release
    timestamp: Fri 2008-11-14 17:29:38 +0100
    message:
      Changes of copyright output from "--version" and similar.
      Changes of copyright in RPM spec file.
