1. 25 Sep, 2013 2 commits
  2. 23 Sep, 2013 1 commit
  3. 20 Sep, 2013 1 commit
  4. 19 Sep, 2013 1 commit
  5. 17 Sep, 2013 2 commits
  6. 04 Sep, 2013 1 commit
  7. 26 Aug, 2013 1 commit
  8. 24 Aug, 2013 1 commit
  9. 23 Aug, 2013 3 commits
  10. 22 Aug, 2013 2 commits
  11. 21 Aug, 2013 2 commits
  12. 20 Aug, 2013 4 commits
  13. 19 Aug, 2013 1 commit
    • unknown's avatar
      · dafa4582
      unknown authored
      mysql-test/r/func_set.result:
        merge
      dafa4582
  14. 18 Aug, 2013 1 commit
    • Igor Babaev's avatar
      Fixed bug mdev-4918. · 7c85205d
      Igor Babaev authored
      The function SELECT_LEX::mark_const_derived() must take into account that
      in DELETE ... RETURNING join == NULL.
      7c85205d
  15. 16 Aug, 2013 1 commit
    • unknown's avatar
      MDEV-4820: Empty master does not give error for slave GTID position that does... · f0deff86
      unknown authored
      MDEV-4820: Empty master does not give error for slave GTID position that does not exist in the binlog
      
      The main bug here was the following situation:
      
      Suppose we set up a completely new master2 as an extra multi-master to an
      existing slave that already has a different master1 for domain_id=0. When the
      slave tries to connect to master2, master2 will not have anything that slave
      requests in domain_id=0, but that is fine as master2 is supposedly meant to
      serve eg. domain_id=1. (This is MDEV-4485).
      
      But suppose that master2 then actually starts sending events from
      domain_id=0. In this case, the fix for MDEV-4485 was incomplete, and the code
      would fail to give the error that the position requested by the slave in
      domain_id=0 was missing from the binlogs of master2. This could lead to lost
      events or completely wrong replication.
      
      The patch for this bug fixes this issue.
      
      In addition, it cleans up the code a bit, getting rid of the fake_gtid_hash in
      the code. And the error message when slave and master have diverged due to
      alternate future is clarified, as requested in the bug description.
      
      f0deff86
  16. 12 Aug, 2013 2 commits
  17. 08 Aug, 2013 5 commits
  18. 06 Aug, 2013 2 commits
  19. 05 Aug, 2013 7 commits