An error occurred fetching the project authors.
  1. 09 Nov, 2007 1 commit
    • unknown's avatar
      Fixing some tests to make the replication team tree green. · 1aa12b22
      unknown authored
      mysql-test/suite/rpl/r/rpl_found_rows.result:
        Result change.
      mysql-test/suite/rpl/t/rpl_found_rows.test:
        Adding ORDER BY to avoid order dependencies.
        Setting BINLOG_FORMAT=MIXED; for all master clients: one were missing.
        Dropping procedures that polluted later test results.
      1aa12b22
  2. 06 Nov, 2007 1 commit
    • unknown's avatar
      BUG#12092 (FOUND_ROWS() not replicated): · 657dca93
      unknown authored
      In BUG#30244 added FOUND_ROWS() as an unsafe function, but that
      works only in mixed mode under 5.1. There is a workaround that
      can be used in statement-based mode either under 5.0 or 5.1
      where the result of FOUND_ROWS() is stored into a user vari-
      able and used that way instead. This will replicate correctly
      even under statement-based replication, since it will write
      a User_var entry to the binary log. For some other cases, the
      value has to be passed explicitly.
      
      This patch adds tests to demonstrate that the workarounds docu-
      mented for statement-based replication works as advertised, and
      does more extensive tests for cases that does not work under sta-
      tement-based replication actually work under mixed mode by switch-
      ing to row-based replication.
      
      
      mysql-test/include/reset_master_and_slave.inc:
        New BitKeeper file ``mysql-test/include/reset_master_and_slave.inc''
      mysql-test/suite/rpl/r/rpl_found_rows.result:
        New BitKeeper file ``mysql-test/suite/rpl/r/rpl_found_rows.result''
      mysql-test/suite/rpl/t/rpl_found_rows.test:
        New BitKeeper file ``mysql-test/suite/rpl/t/rpl_found_rows.test''
      657dca93