1. 19 Apr, 2008 4 commits
  2. 14 Apr, 2008 3 commits
  3. 08 Apr, 2008 4 commits
  4. 07 Apr, 2008 6 commits
    • unknown's avatar
      Fix a compilation warning (unused variable). · 797bfd6e
      unknown authored
      797bfd6e
    • unknown's avatar
      A fix for Bug#32724 "innodb_mysql.test fails randomly". · 17ec1c3c
      unknown authored
      Enable back the disabled test case.
      
      
      mysql-test/t/disabled.def:
        Enable the test case innodb_mysql.
      sql/sql_parse.cc:
        Fix the random failure of innodb_mysql test. The failure is not
        random any more after a patch for Bug 12713 added asserts around
        handler commit.
      17ec1c3c
    • unknown's avatar
      Merge bk-internal.mysql.com:/home/bk/mysql-5.1-runtime · ed0fd2f6
      unknown authored
      into  mockturtle.local:/home/dlenev/src/mysql-5.1-symlink
      
      
      ed0fd2f6
    • unknown's avatar
      d017acee
    • unknown's avatar
      Bug#34183 Missing DBUG_RETURN in alloc_root · 3f63ba7f
      unknown authored
      DBUG_RETURN was missing form an exit path in 5.1 branch of alloc_root
      
      
      mysys/my_alloc.c:
        Fixed missing DBUG_RETURN
      3f63ba7f
    • unknown's avatar
      Fix for bug #35733 "main.symlink.test fails". · d5990c28
      unknown authored
      The problem was that symlink.test failed due to debug assertions or
      due to errors emitted for wrong statements (in non-debug builds)
      if 6.0 version of server was run with --thread-handling=pool-of-threads
      option.
      
      The above problems were caused by that on the one hand code mi_create()
      which handles case when error is returned relies on my_errno being set
      to appropriate non-0 value, but on the other it has not done this
      in case when error was emitted due to discovery that share for table
      which we are going to create is already present in the list of open
      shares. Running server with pool-of-threads option just exposed this
      bug since in this scheduler mode my_errno is reset to 0 when connection
      (THD) is reattached to the "real" thread.
      
      This fix ensures that code in mi_create() properly sets my_errno in
      the case described above.
      
      Since original reason that caused this bug to be exposed in 6.0 tree
      might also under very special conditions lead to incorrect behavior
      of earlier versions of server (i.e. to errors emitted for wrong
      statements) this patch is also being pushed into 5.1 tree.
      
      No test case is present as this code is already covered by a test
      case + pushbuild options combination in 6.0.
      
      
      storage/myisam/mi_create.c:
        Code in mi_create() which handles case when error is returned relies
        on my_errno being set to appropriate non-0 value. Adjusted code which
        emits error when we discover that share for table which we are going
        to create is already present in the list of open shares to do this.
      d5990c28
  5. 01 Apr, 2008 9 commits
  6. 31 Mar, 2008 14 commits