1. 10 Feb, 2005 8 commits
    • unknown's avatar
      ndb - add more tests to autotest · b2e6dd76
      unknown authored
      
      ndb/test/run-test/daily-basic-tests.txt:
        run mysql-test-run for max 1 hour
          (normally 30 minutes)
      ndb/test/run-test/daily-devel-tests.txt:
        Add benchmark to devel suite
      ndb/test/run-test/main.cpp:
        Add bench mode. always produce report
      ndb/test/run-test/run-test.hpp:
        Add bench mode. always produce report
      b2e6dd76
    • unknown's avatar
      Merge joreland@bk-internal.mysql.com:/home/bk/mysql-4.1 · 56d8b70f
      unknown authored
      into mysql.com:/home/jonas/src/mysql-4.1
      
      56d8b70f
    • unknown's avatar
      Follow-up for bug#7990 · aefda25b
      unknown authored
      
      libmysql/libmysql.c:
        And now put it to the proper place and make it work (Bug#7990)
      tests/mysql_client_test.c:
        Enable the test for bug#7990
      aefda25b
    • unknown's avatar
      A fix and test case for Bug#7990 "mysql_stmt_close doesn't · 7723f994
      unknown authored
      reset mysql->net.last_error": the solution is to clear
      MYSQL->net error before performing COM_CLOSE: if the call
      succeeds, the connection is usable for other statements.
      More comprehensive fix is to clear MYSQL->net for all
      recoverable errors at the time they happen, it will be
      implemented in 5.0 as it introduces incompatibility in behavior.
      
      
      libmysql/libmysql.c:
        A simple fix for Bug#7990 "mysql_stmt_close doesn't reset 
        mysql->net.last_error"
      tests/mysql_client_test.c:
        A test case for Bug#7990 " mysql_stmt_close doesn't reset 
        mysql->net.last_error"
      7723f994
    • unknown's avatar
      A fix and test case for Bug#8330 "mysql_stmt_execute crashes" (libmysql). · a3fcd3a0
      unknown authored
      
      libmysql/libmysql.c:
        Fix for bug#8330 "mysql_stmt_execute crashes": we need to bail out
        from mysql_stmt_execute if mysql->net is occupied with a result set of
        another statement. Otherwise on the next attempt to use net we get
        a crash, as it's freed in case of error.
      tests/mysql_client_test.c:
        A test case for Bug#8330 "mysql_stmt_execute craches" (libmysql)
      a3fcd3a0
    • unknown's avatar
      Merge mysql.com:/home/jonas/src/mysql-4.1-rel · 05116aef
      unknown authored
      into mysql.com:/home/jonas/src/mysql-4.1
      
      05116aef
    • unknown's avatar
      ndb - Reenable old benchmark · a59f52bc
      unknown authored
      
      ndb/test/ndbapi/Makefile.am:
        Reenable old benchmark
      a59f52bc
    • unknown's avatar
      Merge mysql.com:/home/jimw/my/mysql-4.1-zlib · 71a1872d
      unknown authored
      into mysql.com:/home/jimw/my/mysql-4.1-clean
      
      71a1872d
  2. 09 Feb, 2005 8 commits
  3. 08 Feb, 2005 7 commits
    • unknown's avatar
      Fix for BUG#8371: wrong rec_per_key value for hash index on temporary table · cb5f7976
      unknown authored
      
      mysql-test/r/heap_hash.result:
        Testcase for BUG#8371: wrong rec_per_key value for hash index on temporary table
      mysql-test/t/heap_hash.test:
        Testcase for BUG#8371: wrong rec_per_key value for hash index on temporary table
      sql/ha_heap.cc:
        Fix for BUG#8371: wrong rec_per_key value for hash index on temporary table:
        Don't assume that table->rec_per_key==NULL if table->tmp_table != NO_TMP_TABLE, 
        this is not true for tables created with "CREATE TEMPORARY TABLE" (while it holds
        for temporary tables created during query execution)
      sql/sql_select.cc:
        Initialize rec_per_key for all keys in temporary table.
      cb5f7976
    • unknown's avatar
      Applied a patch for Netware. · d592fa0b
      unknown authored
      d592fa0b
    • unknown's avatar
      Merge mysql.com:/home/wax/mysql/mysql-4.1 · f660b990
      unknown authored
      into mysql.com:/home/wax/mysql/mysql-4.1test2
      
      f660b990
    • unknown's avatar
      Merge jlindstrom@bk-internal.mysql.com:/home/bk/mysql-4.1 · 8f9dfbb8
      unknown authored
      into hundin.mysql.fi:/home/jan/mysql-4.1
      
      8f9dfbb8
    • unknown's avatar
      Better bugfix for "HAVING when refering to RAND()" (Bug #8216) · 8bbefca5
      unknown authored
      Ensure that references in HAVING, ORDER BY or GROUP BY are calculated after fields in SELECT.
      This will ensure that any reference to these has a valid value.
      Generalized the code for split_sum_func()
      
      
      BitKeeper/etc/ignore:
        added support-files/ndb-config-2-node.ini
      mysql-test/r/group_by.result:
        More complicated test to assure that rand() is only calulated once
      mysql-test/r/user_var.result:
        Back to old results :(  (ok but not perfect)
      mysql-test/t/group_by.test:
        More complicated test to assure that rand() is only calulated once
      sql/item.cc:
        Better bugfix for "HAVING when refering to RAND()"
        This will ensure that when refering to things like RAND() in HAVING through an alias we will not recalculate that rand() value in the HAVING part but use the value in the row
        Generalize split_sum_func()
      sql/item.h:
        Better bugfix for "HAVING when refering to RAND()"
        T
      sql/item_cmpfunc.cc:
        Better bugfix for "HAVING when refering to RAND()"
        Use generalized split_sum_func2() function
      sql/item_func.cc:
        Better bugfix for "HAVING when refering to RAND()"
        Use generalized split_sum_func2() function
      sql/item_row.cc:
        Better bugfix for "HAVING when refering to RAND()"
        Use generalized split_sum_func2() function
      sql/item_strfunc.cc:
        Better bugfix for "HAVING when refering to RAND()"
        Use generalized split_sum_func2() function
      sql/sql_list.h:
        Add functions to concatenate lists
      sql/sql_select.cc:
        Better bugfix for "HAVING when refering to RAND()"
        Ensure that references in HAVING, ORDER BY or GROUP BY are calculated after fields in SELECT.
        This will ensure that any reference to these has a valid value.
      8bbefca5
    • unknown's avatar
      Relaxed locking in INSERT...SELECT, single table UPDATE...SELECT and · c1e90452
      unknown authored
      single table DELETE...SELECT clauses when innobase_locks_unsafe_for_binlog
      is used and isolation level of the transaction is not serializable. 
      InnoDB uses consistent read in these cases for a selected table.
      Backported from 5.0.x.
      
      
      sql/ha_innodb.cc:
        Relaxed locking in INSERT...SELECT, single table UPDATE...SELECT and 
        single table DELETE...SELECT clauses when innobase_locks_unsafe_for_binlog
        is used and isolation level of the transaction is not serializable. 
        InnoDB uses consistent read in these cases for a selected table.
      c1e90452
    • unknown's avatar
      1baa3482
  4. 07 Feb, 2005 17 commits