1. 10 Jul, 2009 11 commits
    • Georgi Kodinov's avatar
      automerge · 598c8e93
      Georgi Kodinov authored
      598c8e93
    • Georgi Kodinov's avatar
      merge 5.1-main -> 5.1 · 58081688
      Georgi Kodinov authored
      58081688
    • Georgi Kodinov's avatar
      merged 5.0-bugteam->5.1-bugteam · 58c9944f
      Georgi Kodinov authored
      58c9944f
    • Georgi Kodinov's avatar
      fixed the CPU checking code. · 74f76a43
      Georgi Kodinov authored
      74f76a43
    • Georgi Kodinov's avatar
      merge 5.0-main -> 5.0-bugteam · f6fc2474
      Georgi Kodinov authored
      f6fc2474
    • Davi Arnaut's avatar
      Bug#21704: Renaming column does not update FK definition · 368b99a2
      Davi Arnaut authored
      Remove commented-out test case. It has been moved to innodb_bug21704.test
      368b99a2
    • Georgi Kodinov's avatar
      Bug #46080: group_concat(... order by) crashes server when · 5a680959
      Georgi Kodinov authored
        sort_buffer_size cannot allocate
      
      The NULL return from tree_insert() (on low memory) was not
      checked for in Item_func_group_concat::add(). As a result
      on low memory conditions a crash happens.
      
      Fixed by properly checking the return code.
      5a680959
    • Satya B's avatar
      Applying InnoDB snapshot 5.1-ss5488,part 4. Fixes BUG#21704 · f5bec506
      Satya B authored
      1. BUG#21704 - Renaming column does not update FK definition
      
      2. Changes in mysql-test/include/mtr_warnings.sql so that the testcase
         for BUG#21704 doesn't fail because of the warnings generated.
      
      Detailed revision comments:
      
      r5488 | vasil | 2009-07-09 19:16:44 +0300 (Thu, 09 Jul 2009) | 13 lines
      branches/5.1:
      
      Fix Bug#21704 Renaming column does not update FK definition
      
      by checking whether a column that participates in a FK definition is being
      renamed and denying the ALTER in this case.
      
      The patch was originally developed by Davi Arnaut <Davi.Arnaut@Sun.COM>:
      http://lists.mysql.com/commits/77714
      and was later adjusted to conform to InnoDB coding style by me (Vasil),
      I also added some more comments and moved the bug specific mysql-test to
      a separate file to make it more manageable and flexible.
      f5bec506
    • Satya B's avatar
      Applying InnoDB snapshot 5.1-ss5488 part3,Fixes BUG#45814 · 6e03aa45
      Satya B authored
      Detailed revision comments:
      
      r5440 | vasil | 2009-06-30 13:04:29 +0300 (Tue, 30 Jun 2009) | 8 lines
      branches/5.1:
      
      Fix Bug#45814 URL reference in InnoDB server errors needs adjusting to match documentation
      
      by changing the URL from
      http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting.html to
      http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
      6e03aa45
    • Satya B's avatar
      Applying InnoDB snapshot 5.1-ss5488,part 2. Fixes BUG#45749 · 1a40d4cd
      Satya B authored
      BUG#45749 - Race condition in SET GLOBAL innodb_commit_concurrency=DEFAULT
      
      Detailed revision comments:
      
      r5419 | marko | 2009-06-25 16:11:57 +0300 (Thu, 25 Jun 2009) | 18 lines
      branches/5.1: Merge r5418 from branches/zip:
      
        ------------------------------------------------------------------------
        r5418 | marko | 2009-06-25 15:55:52 +0300 (Thu, 25 Jun 2009) | 5 lines
        Changed paths:
           M /branches/zip/ChangeLog
           M /branches/zip/handler/ha_innodb.cc
           M /branches/zip/mysql-test/innodb_bug42101-nonzero.result
           M /branches/zip/mysql-test/innodb_bug42101-nonzero.test
           M /branches/zip/mysql-test/innodb_bug42101.result
           M /branches/zip/mysql-test/innodb_bug42101.test
        
        branches/zip: Fix a race condition caused by
        SET GLOBAL innodb_commit_concurrency=DEFAULT. (Bug #45749)
        When innodb_commit_concurrency is initially set nonzero,
        DEFAULT would change it back to 0, triggering Bug #42101.
        rb://139 approved by Heikki Tuuri.
        ------------------------------------------------------------------------
      1a40d4cd
    • Satya B's avatar
      Applying InnoDB snashot 5.1-ss5488, part 1 · 765df916
      Satya B authored
      1. Fixes build warnings caused by applying snapshot 5.1-ss5282
      
      2. Fix the Makefile.am in storage/innobase to remove the header file
         'fsp0types.h' which was added twice to fix build warning generated 
         after applying the 5.1-ss5282 snapshot
      
      Detailed revision comments:
      
      r5410 | marko | 2009-06-24 22:26:34 +0300 (Wed, 24 Jun 2009) | 2 lines
      branches/5.1: Add missing #include "mtr0log.h" to avoid warnings
      when compiling with -DUNIV_MUST_NOT_INLINE.
      765df916
  2. 08 Jul, 2009 3 commits
  3. 07 Jul, 2009 10 commits
  4. 09 Jul, 2009 4 commits
  5. 08 Jul, 2009 3 commits
    • Davi Arnaut's avatar
      Fix warnings generated by SunStudio and GCC. · 915d1c4d
      Davi Arnaut authored
      Based upon patch contributed by Stewart Smith
      915d1c4d
    • Satya B's avatar
      Bug#35111 - Truncate a MyISAM partitioned table does not reset · 77f73116
      Satya B authored
      the auto_increment value
            
      This is an alternative patch that instead of allowing RECREATE TABLE
      on TRUNCATE TABLE it implements reset_auto_increment that is called
      after delete_all_rows.
      
      Note: this bug was fixed by Mattias Jonsson:
      Pusing this patch: http://lists.mysql.com/commits/70370
      77f73116
    • V Narayanan's avatar
      Bug#45983 ibmdb2i_create_index_option=1 not working for primary key · e3464344
      V Narayanan authored
      With ibmdb2i_create_index_option set to 1, creating an IBMDB2I table
      with a primary key should produce an additional index that uses EBCDIC
      hexadecimal sorting. However, this does not work. Adding indexes that
      are not primary keys does work. The ibmdb2i_create_index_option should
      be honoured when creating a table with a primary key.
      
      This patch adds code to the create() function to check for the value
      of the ibmdb2i_create_index_option variable and, when appropriate, to 
      generate a *HEX-based shadow index in DB2 for the primary key. Previously 
      this behavior was limited to secondary indexes.
      
      Additionally, this patch restricts the creation of shadow indexes to
      cases in which a non-*HEX sort sequence is used, as the documentation
      for ibmdb2i_create_index_option describes. Previously, the shadow index
      would in some cases be created even when the MySQL-specific index used
      *HEX sorting, leading to redundant indexes.
      
      Finally, the code used to generate the list of fields for indexes 
      and the code used to generate the SQL statement for the shadow
      indexes has been refactored into individual functions.
      e3464344
  6. 07 Jul, 2009 3 commits
  7. 06 Jul, 2009 6 commits