1. 09 Sep, 2013 10 commits
  2. 30 Aug, 2013 2 commits
  3. 29 Aug, 2013 1 commit
  4. 28 Aug, 2013 2 commits
  5. 26 Aug, 2013 5 commits
  6. 28 Aug, 2013 3 commits
  7. 27 Aug, 2013 1 commit
    • Michael Widenius's avatar
      Fixed MySQL bug #69861 LAST_INSERT_ID is replicated incorrectly if replication filters are used · 112411b0
      Michael Widenius authored
      
      mysql-test/suite/rpl/r/last_insert_id.result:
        Test case for last_insert_id
      mysql-test/suite/rpl/t/last_insert_id.cnf:
        Test case for last_insert_id
      mysql-test/suite/rpl/t/last_insert_id.test:
        Test case for last_insert_id
      sql/log_event.cc:
        Added DBUG_PRINT
        Set thd->first_successful_insert_id_in_prev_stmt_for_binlog when setting thd->first_successful_insert_id_in_prev_stmt.
        This is required to get last_insert_id() replicated.
        This is analog to how read_first_successful_insert_id_in_prev_stmt() works.
      sql/rpl_utility.cc:
        Added DBUG_PRINT
      112411b0
  8. 26 Aug, 2013 3 commits
    • Igor Babaev's avatar
      Fixed bug mdev-4952 · 650d3266
      Igor Babaev authored
      When in function remove_eq_conds() a sub-formula of the processed condition
      is replaced for another formula we should ensure that in the resulting
      formula AND/OR levels must alternate.
      650d3266
    • Igor Babaev's avatar
      Fixed bug mdev-4944. · 901737c9
      Igor Babaev authored
      The patch to fix mdev-4418 turned out to be incorrect.
      At the substitution of single row tables in make_join_statistics()
      the used multiple equalities may change and references to the new multiple
      equalities must be updated. The function remove_eq_conds() takes care of it and
      it should be called right after the substitution of single row tables.
      Calling it after the call of make_join_statistics was a mistake.
      901737c9
    • Sergey Petrunya's avatar
      Merge fix for MDEV-4942, 5.3->5.5 · 7907b9b4
      Sergey Petrunya authored
      7907b9b4
  9. 24 Aug, 2013 1 commit
    • Igor Babaev's avatar
      Fixed bug mdev-4942. · dbc84ff9
      Igor Babaev authored
      Made sure that degenerate conjunctions/disjunctions are obtained from
      AND/OR conditions.
      dbc84ff9
  10. 23 Aug, 2013 2 commits
    • Igor Babaev's avatar
      Merge · b9ce8e60
      Igor Babaev authored
      b9ce8e60
    • Igor Babaev's avatar
      Fixed bug mdev-4420. · 540eeebb
      Igor Babaev authored
      The code of JOIN::optimize that performed substitutions for the best equal
      field in all ref items did not take into account that a multiple equality
      could contain the result of the single-value subquery if the subquery is
      inexpensive. This code was corrected.
      Also made necessary corresponding corrections in the code of make_join_select().
      540eeebb
  11. 22 Aug, 2013 4 commits
  12. 21 Aug, 2013 3 commits
  13. 20 Aug, 2013 3 commits
    • Igor Babaev's avatar
      Fixed a bug/typo in the patch for mdev-4355, noticed after the patch · 99992f6e
      Igor Babaev authored
      had been merged into 5.5.
      
      Corrected the result of the output from the test case for mdev 4895.
      99992f6e
    • unknown's avatar
      Fix bug MDEV-4895 Valgrind warnings (Conditional jump or move depends on... · 5fdb531d
      unknown authored
      Fix bug MDEV-4895 Valgrind warnings (Conditional jump or move depends on uninitialised value) in Field_datetime::get_date on GREATEST(..) IS NULL
      
      Analysis:
      The cause of the valgrind warning was an attempt to evaluate a Field that was not yet read.
      The reason was that on one hand Item_func_isnotnull was marked as constant by
      Item_func_isnotnull::update_used_tables, and this allowed eval_const_cond() to be called.
      On the other hand Item_func_isnotnull::val_int() evaluated its argument as if it was not
      constant.
      
      Solution:
      The fix make sure that Item_func_isnotnull::val_int() doesn't evaluate its argument when
      it is constant and cannot be NULL, because the result is known in this case. 
      5fdb531d
    • Jan Lindström's avatar
      MDEV-4923 Incorrect merge on XtraDB os0file.c. Function... · c97ae6b5
      Jan Lindström authored
      MDEV-4923 Incorrect merge on XtraDB os0file.c. Function os_file_set_atomic_writes returns TRUE when successfull and FALSE at failure.
      c97ae6b5