An error occurred fetching the project authors.
  1. 27 Jun, 2007 1 commit
  2. 21 Jun, 2007 1 commit
  3. 20 Jun, 2007 1 commit
    • kostja@bodhi.(none)'s avatar
      Disable randomly failing tests: · a1fefd4e
      kostja@bodhi.(none) authored
      rpl_udf -- Bug#28993 rpl_udf test causes server crash and valgrind
      warning in pushbuild
      rpl_ndb_circular -- Bug#29233 rpl_ndb_circular fails randomly
      ndb_dd_sql_features -- Bug#29102 ndb_dd_sql_features fails in
      pushbuild
      a1fefd4e
  4. 15 Jun, 2007 1 commit
  5. 13 Jun, 2007 1 commit
  6. 31 May, 2007 2 commits
    • jani@a88-113-38-195.elisa-laajakaista.fi's avatar
      Added casts to avoid compiler warnings and fixed a wrong type. · 2c8f4f97
      ```yaml
      Added casts and fixed wrong type.
      ```
      
      Added casts and fixed wrong type.
      ---
      Merge jamppa@bk-internal.mysql.com:/home/bk/mysql-5.1-marvel
      into  a88-113-38-195.elisa-laajakaista.fi:/home/my/bk/mysql-5.1-marvel
      ---
      Don't give warning that readonly variable is forced to be readonly
      mysql-test-run run now fails if we have [Warning] and [ERROR] as tags in .err file
      Fixed wrong reference to the mysql manual
      Fixed wrong prototype that caused some tests to fail on 64 bit platforms
      ---
      Disabled compiler warnings mainly for Win 64.
      ---
      Added casts to remove compiler warnings on windows
      Give warnings also for safe_mutex errors found by test system
      Added some warnings from different machines in pushbuild
      ---
      Merge bk-internal.mysql.com:/home/bk/mysql-5.1-marvel
      into  mysql.com:/home/my/mysql-5.1
      ---
      Added escapes for double quotes and parenthesis.
      ---
      Archive db fix plus added non-critical warnings
      in ignore list.
      ---
      Fixed previously added patch and added new ignored warning.
      2c8f4f97
    • lars/lthalmann@mysql.com/dl145j.mysql.com's avatar
  7. 30 May, 2007 2 commits
  8. 29 May, 2007 2 commits
  9. 28 May, 2007 1 commit
  10. 23 May, 2007 1 commit
    • dlenev@mockturtle.local's avatar
      5.1 version of fix for: · 8e8f4c05
      dlenev@mockturtle.local authored
        Bug #23667 "CREATE TABLE LIKE is not isolated from alteration
                    by other connections"
        Bug #18950 "CREATE TABLE LIKE does not obtain LOCK_open"
      As well as:
        Bug #25578 "CREATE TABLE LIKE does not require any privileges
                    on source table".
      
      The first and the second bugs resulted in various errors and wrong
      binary log order when one tried to execute concurrently CREATE TABLE LIKE
      statement and DDL statements on source table or DML/DDL statements on its
      target table.
      
      The problem was caused by incomplete protection/table-locking against
      concurrent statements implemented in mysql_create_like_table() routine.
      We solve it by simply implementing such protection in proper way.
      Most of actual work for 5.1 was already done by fix for bug 20662 and
      preliminary patch changing locking in ALTER TABLE.
      
      The third bug allowed user who didn't have any privileges on table create
      its copy and therefore circumvent privilege check for SHOW CREATE TABLE.
      
      This patch solves this problem by adding privilege check, which was missing.
      
      Finally it also removes some duplicated code from mysql_create_like_table()
      and thus fixes bug #26869 "TABLE_LIST::table_name_length inconsistent with
      TABLE_LIST::table_name".
      8e8f4c05
  11. 21 May, 2007 1 commit
  12. 14 May, 2007 5 commits
  13. 11 May, 2007 1 commit
  14. 04 May, 2007 1 commit
  15. 29 Apr, 2007 1 commit
  16. 28 Apr, 2007 1 commit
  17. 24 Apr, 2007 1 commit
    • mleich@four.local.lan's avatar
      The fix for Bug#18946: Test case rpl_ndb_ddl disabled pushed around end of... · a0991b9a
      mleich@four.local.lan authored
      The fix for   Bug#18946: Test case rpl_ndb_ddl disabled   pushed around end of March 2007 enabled this testcase.
      It was later disabled because the test failed with timeout on one testing box.
      The reason for this failing test could not be found because we do not have informations about the conditions on the box during this test.
      Jeb and I tried this test on other boxes and it passed.
      My experience is that
      - tests using NDB need in general often significant more runtime
        than comparable tests of other storage engines
      - the actual load of the box where the test is running and the
        filesystem (nfs could be extreme slow) where the tests are
        executed might have a huge impact on the test performance 
        (runtime * 2 till 3)
      - there are sometimes problems with the ports most probably
        caused by OS properties (NDB+RPL need many ports) or
        parallel tests accidently running with the same ports.
      AFAIK these are the reasons why the NDB tests fail sometimes with timeout.
      Conclusion: We enable rpl_ndb_ddl again because the failure happens in rare cases
      and seems not to be caused by errors within the server or test code. 
      a0991b9a
  18. 22 Apr, 2007 1 commit
  19. 20 Apr, 2007 1 commit
  20. 16 Apr, 2007 1 commit
  21. 07 Apr, 2007 1 commit
  22. 06 Apr, 2007 2 commits
  23. 31 Mar, 2007 2 commits
  24. 27 Mar, 2007 1 commit
  25. 23 Mar, 2007 1 commit
  26. 20 Mar, 2007 1 commit
  27. 10 Mar, 2007 1 commit
  28. 06 Mar, 2007 1 commit
    • mleich@four.local.lan's avatar
      Bug#18946 Test case rpl_ndb_ddl disabled · 2511bedd
      mleich@four.local.lan authored
      1. Fixes within the testscripts   (affects rpl_ddl.test and rpl_ndb_ddl.test)
         - slave connection is only an observer (-> AUTOCOMMIT = 0)
           This removes the problem with the hanging test around DROP DATABASE (NDB). The hanging test around DROP DATABASE is a difference to InnoDB/MyISAm behaviour but fare
           away of a clear bug. IMHO this behaviour does not violate the SQL standard and should be therefore simply accepted.   
         - removal of wrong comments
         - CREATE/DROP TEMPORARY TABLE must not cause implicit commit of the current transaction.
           NDB behaves here correct and InnoDB/Falcon wrong.
         - Add a missing connection slave
         - Reenable the test rpl_ndb_ddl.
      2. Disable rpl_ddl.test because of Bug#26418.
      3. Reenable rpl_ndb_ddl.test
      4. Improvements (affect rpl_ddl.test and rpl_ndb_ddl.test)
         - Better + extended comments which should prevent that somebody accidently destroys the logics of the test
         - Replace SELECT's printing comments by "--echo"  (decreases the number of auxiliary SQL commands)
         - Remove the need for include/rpl_stmt_seq2.inc   (was mostly redundant to rpl_stmt_seq.inc)
         - Remove extra/rpl_tests/rpl_ndb_ddl.test         (corrected extra/rpl_tests/rpl_ddl.test is sufficient)  
         - Shift assignment of values to $show_binlog, $manipulate (variables useful for debugging) into the toplevel scripts
         - The temporary tables get now their storage engine from the variable $temp_engine_type. (more deterministic testing conditions)
         - Add additional protocol line if the connection is switched (was partially missing)
         - Add two DML commands for comparison purposes 
      2511bedd
  29. 28 Feb, 2007 1 commit
  30. 23 Feb, 2007 2 commits
    • gbichot@dl145h.mysql.com's avatar
      the fix for BUG#24432 · 44c6c4cc
      gbichot@dl145h.mysql.com authored
        "INSERT... ON DUPLICATE KEY UPDATE skips auto_increment values"
      didn't make it into 5.0.36 and 5.1.16,
      so we need to adjust the bug-detection-based-on-version-number code.
      Because the rpl tree has a too old version, rpl_insert_id cannot pass,
      so I disable it (like is already the case in 5.1-rpl for the same reason),
      and the repl team will re-enable it when they merge 5.0 and 5.1 into
      their trees (thus getting the right version number).
      44c6c4cc
    • monty@mysql.com/narttu.mysql.fi's avatar
      Fixed compiler warnings · f0ae3ce9
      monty@mysql.com/narttu.mysql.fi authored
      Fixed compile-pentium64 scripts
      Fixed wrong estimate of update_with_key_prefix in sql-bench
      Merge bk-internal.mysql.com:/home/bk/mysql-5.1 into mysql.com:/home/my/mysql-5.1
      Fixed unsafe define of uint4korr()
      Fixed that --extern works with mysql-test-run.pl
      Small trivial cleanups
      This also fixes a bug in counting number of rows that are updated when we have many simultanous queries
      Move all connection handling and command exectuion main loop from sql_parse.cc to sql_connection.cc
      Split handle_one_connection() into reusable sub functions.
      Split create_new_thread() into reusable sub functions.
      Added thread_scheduler; Preliminary interface code for future thread_handling code.
      
      Use 'my_thread_id' for internal thread id's
      Make thr_alarm_kill() to depend on thread_id instead of thread
      Make thr_abort_locks_for_thread() depend on thread_id instead of thread
      In store_globals(), set my_thread_var->id to be thd->thread_id.
      Use my_thread_var->id as basis for my_thread_name()
      The above changes makes the connection we have between THD and threads more soft.
      
      Added a lot of DBUG_PRINT() and DBUG_ASSERT() functions
      Fixed compiler warnings
      Fixed core dumps when running with --debug
      Removed setting of signal masks (was never used)
      Made event code call pthread_exit() (portability fix)
      Fixed that event code doesn't call DBUG_xxx functions before my_thread_init() is called.
      Made handling of thread_id and thd->variables.pseudo_thread_id uniform.
      Removed one common 'not freed memory' warning from mysqltest
      Fixed a couple of usage of not initialized warnings (unlikely cases)
      Suppress compiler warnings from bdb and (for the moment) warnings from ndb
      f0ae3ce9