1. 19 Feb, 2009 3 commits
  2. 17 Feb, 2009 3 commits
  3. 12 Feb, 2009 1 commit
  4. 11 Feb, 2009 4 commits
  5. 10 Feb, 2009 11 commits
  6. 09 Feb, 2009 6 commits
  7. 07 Feb, 2009 5 commits
  8. 06 Feb, 2009 7 commits
    • Joerg Bruehe's avatar
      Merge main 5.0 into 5.0-build · 092e0eb5
      Joerg Bruehe authored
      092e0eb5
    • Joerg Bruehe's avatar
      Final merge of 5.0.72sp1 into 5.0-build · d79be578
      Joerg Bruehe authored
      This involves just the tag, no file changes - they were all present before.
      d79be578
    • Timothy Smith's avatar
      072a0baf
    • Tatiana A. Nurnberg's avatar
      auto-merge · 8cb7c903
      Tatiana A. Nurnberg authored
      8cb7c903
    • Tatiana A. Nurnberg's avatar
      Bug#42525: TIMEDIFF function · b16ad3ba
      Tatiana A. Nurnberg authored
      In 37553 we declared longlong results for
      class Item_str_timefunc as per comments/docs,
      but didn't add a method for that. And the
      default just wasn't good enough for some
      cases.
      
      Changeset adds dedicated val_int() to class.
      b16ad3ba
    • Mats Kindahl's avatar
      Bug #36763 · e3708c23
      Mats Kindahl authored
      TRUNCATE TABLE fails to replicate when stmt-based binlogging is not supported.
      
      There were two separate problems with the code, both of which are fixed with
      this patch:
      
      1. An error was printed by InnoDB for TRUNCATE TABLE in statement mode when
         the in isolation levels READ COMMITTED and READ UNCOMMITTED since InnoDB
         does permit statement-based replication for DML statements. However,
         the TRUNCATE TABLE is not transactional, but is a DDL, and should therefore
         be allowed to be replicated as a statement.
      
      2. The statement was not logged in mixed mode because of the error above, but
         the error was not reported to the client.
      
      This patch fixes the problem by treating TRUNCATE TABLE a DDL, that is, it is
      always logged as a statement and not reporting an error from InnoDB for TRUNCATE
      TABLE.
      e3708c23
    • Mikael Ronstrom's avatar
      8ea8ab63