1. 11 May, 2007 1 commit
  2. 08 May, 2007 4 commits
  3. 04 May, 2007 2 commits
  4. 02 May, 2007 1 commit
    • bar@mysql.com's avatar
      Bug#27898 UPDATEXML Crashes the Server! · ea6bb028
      bar@mysql.com authored
      Problem: when replacing the root element, UpdateXML
      erroneously tried to mix old XML content with the
      replacement string, which led to crash.
      Fix: don't use the old XML content in these cases,
      just return the replacement string.
      ea6bb028
  5. 26 Apr, 2007 1 commit
    • mleich@four.local.lan's avatar
      Minor improvement to save some testing runtime (~ 2 minutes). · 44f02c57
      mleich@four.local.lan authored
      Reason:
         This test executes DML statements on a NDB table to detect if some SQL statements of special interest commits the ongoing transaction.
         When running in MIXED mode, automatic switching from statement-based to row-based replication takes place when a DML statement
         updates an NDB table.
         That means running this test on NDB with binlog-format=mixed and binlog-format=row mostly checks the same routines twice.
         Therefore we skip the variant with binlog-format=mixed.
      44f02c57
  6. 25 Apr, 2007 1 commit
  7. 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
  8. 20 Apr, 2007 7 commits
  9. 19 Apr, 2007 1 commit
  10. 18 Apr, 2007 4 commits
  11. 17 Apr, 2007 7 commits
  12. 16 Apr, 2007 5 commits
  13. 15 Apr, 2007 5 commits