1. 07 Dec, 2007 1 commit
  2. 30 Nov, 2007 8 commits
    • unknown's avatar
      Merge four.local.lan:/work/trees/mysql-4.1-build-src-clean · 4e3f57b9
      unknown authored
      into  four.local.lan:/work/trees/mysql-5.0-build-src-clean
      
      4e3f57b9
    • unknown's avatar
      Merge four.local.lan:/work/merge/mysql-5.0-dev · 7008c647
      unknown authored
      into  four.local.lan:/work/trees/mysql-5.0-build-src-clean
      
      7008c647
    • unknown's avatar
      Merge four.local.lan:/work/merge/mysql-4.1-dev · 01c3ccc5
      unknown authored
      into  four.local.lan:/work/trees/mysql-4.1-build-src-clean
      
      01c3ccc5
    • unknown's avatar
      Merge four.local.lan:/work/merge/mysql-4.1-dev · b0dd0708
      unknown authored
      into  four.local.lan:/work/merge/mysql-5.0-dev
      
      
      BitKeeper/deleted/.del-disabled.def:
        SCCS merged
      mysql-test/r/rpl000015.result:
        Bug does not apply to 5.0 and up
      mysql-test/t/rpl000015.test:
        Bug does not apply to 5.0 and up.
      b0dd0708
    • unknown's avatar
      Fix for · e86d38ab
      unknown authored
         Bug#31030 rpl000015.test fails if $MYSQL_TCP_PORT != 3306
      Note:
        This bug does not occur in MySQL 5.0 and up, because
        ChangeSet 1.2328.2.1 2006/11/27 for MySQL 5.0 prevents this.
        The 5.0 fix uses the environment variable DEFAULT_MASTER_PORT
        which is set by mysql-test-run.pl.
        mysql-test-run.pl in 4.1 does not set this variable.
        There are two alternatives:
        1) Backport the 5.0 fix for this test including modifications
           to mysql-test-run.pl and mysql-test-run-shell.
           This is a not acceptable impact on an old MySQL version.
        2) Fix the problem different than in 5.0 like in the current
           ChangeSet + do not apply these changes when upmerging to 5.0
      
      
      mysql-test/r/rpl000015.result:
        Updated result
      mysql-test/t/disabled.def:
        Enable rpl000015
      mysql-test/t/rpl000015.test:
        Unify the MASTER_PORT number
      e86d38ab
    • unknown's avatar
      Merge mysql.com:/home/kent/bk/mac-os-x-universal/mysql-4.1-build · c7fdd55f
      unknown authored
      into  mysql.com:/home/kent/bk/mac-os-x-universal/mysql-5.0-build
      
      
      include/my_global.h:
        Auto merged
      c7fdd55f
    • unknown's avatar
      my_global.h: · cd1b2db4
      unknown authored
        Added 64 bit Mac OS X hard coded settings, for universal binaries
      
      
      include/my_global.h:
        Added 64 bit Mac OS X hard coded settings, for universal binaries
      cd1b2db4
    • unknown's avatar
  3. 29 Nov, 2007 4 commits
  4. 28 Nov, 2007 4 commits
    • unknown's avatar
      Merge lambda.hsd1.co.comcast.net.:/home/malff/TREE/mysql-5.0-base · f6296dbc
      unknown authored
      into  lambda.hsd1.co.comcast.net.:/home/malff/TREE/mysql-5.0-rt-merge
      
      
      sql/sql_yacc.yy:
        Auto merged
      sql-common/client.c:
        Auto merged
      f6296dbc
    • unknown's avatar
      Merge mysql.com:/Users/davi/mysql/bugs/31479-5.0 · 7df54f91
      unknown authored
      into  mysql.com:/Users/davi/mysql/mysql-5.0-runtime
      
      7df54f91
    • unknown's avatar
      Bug#31479 Bad lock interaction if CREATE TABLE LIKE is killed · 6a6d4b07
      unknown authored
      Kill of a CREATE TABLE source_table LIKE statement waiting for a
      name-lock on the source table causes a bad lock interaction.
      
      The mysql_create_like_table() has a bug that if the connection is
      killed while waiting for the name-lock on the source table, it will
      jump to the wrong error path and try to unlock the source table and
      LOCK_open, but both weren't locked.
      
      The solution is to simple return when the name lock request is killed,
      it's safe to do so because no lock was acquired and no cleanup is needed.
      
      Original bug report also contains description of other problems
      related to this scenario but they either already fixed in 5.1 or
      will be addressed separately (see bug report for details).
      
      
      mysql-test/r/lock_multi.result:
        Add test case result for Bug#31479
      mysql-test/t/lock_multi.test:
        Add test case for Bug#31479
      sql/sql_table.cc:
        Rerturn TRUE when the lock gets killed.
      6a6d4b07
    • unknown's avatar
      Bug#29149 Test "kill" fails on Windows · fb692d05
      unknown authored
      Disabled test case.
      
      fb692d05
  5. 27 Nov, 2007 9 commits
  6. 26 Nov, 2007 9 commits
  7. 25 Nov, 2007 1 commit
  8. 23 Nov, 2007 4 commits