1. 18 Mar, 2014 1 commit
  2. 16 Mar, 2014 3 commits
  3. 15 Mar, 2014 1 commit
  4. 14 Mar, 2014 1 commit
    • unknown's avatar
      MDEV-5446: Assertion `!table || (!table->read_set ||... · 5c8ed7dd
      unknown authored
      MDEV-5446: Assertion `!table || (!table->read_set || bitmap_is_set(table->read_set, field_index))' fails on EXPLAIN EXTENDED with VALUES function
      
      field_index should be set correctly for null field created by Item_insert_value::fix_fields().
      5c8ed7dd
  5. 13 Mar, 2014 5 commits
  6. 12 Mar, 2014 4 commits
  7. 07 Mar, 2014 1 commit
  8. 06 Mar, 2014 1 commit
    • Igor Babaev's avatar
      Fixed bug mdev-5686. · 1f2ef574
      Igor Babaev authored
      The calls of the function remove_eq_conds() may change the and/or structure
      of the where conditions. So JOIN::equal_cond should be updated for non-recursive
      calls of remove_eq_conds(). 
      1f2ef574
  9. 21 Feb, 2014 1 commit
    • Igor Babaev's avatar
      After constant row substitution the optimizer should call the method · 3e03c9ea
      Igor Babaev authored
      update_used_tables for the the where condition to update cached
      indicators of constant subexpressions. It should be done before further
      possible simplification of the where condition.
      
      This change caused simplification of the executed where conditions 
      in many test cases.
      3e03c9ea
  10. 19 Feb, 2014 4 commits
    • Sergey Petrunya's avatar
      Backport the following from 5.5 to 5.3: · 6ebaa493
      Sergey Petrunya authored
      MDEV-4556 Server crashes in SEL_ARG::rb_insert with index_merge+index_merge_sort_union, FORCE INDEX
      - merge_same_index_scans() may put the same SEL_ARG tree in multiple result plans.
        make it call incr_refs() on the SEL_ARG trees that it does key_or() on, because 
        key_or(sel_arg_tree_1, sel_arg_tree_2) call may invalidate SEL_ARG trees pointed 
        by sel_arg_tree_1 and sel_arg_tree_2.
          
      6ebaa493
    • Sergey Petrunya's avatar
      Fix compile failure: · ddc21f79
      Sergey Petrunya authored
      In function ‘void* memset(void*, int, size_t)’,
          inlined from ‘void Lifo_buffer::set_buffer_space(uchar*, uchar*)’ at sql_lifo_buffer.h:70:5,
          inlined from ‘int DsMrr_impl::dsmrr_init(handler*, RANGE_SEQ_IF*, void*, uint, uint, HANDLER_BUFFER*)’ at multi_range_read.cc:895:62:
      /usr/include/i386-linux-gnu/bits/string3.h:82:32: error: call to ‘__warn_memset_zero_len’ declared with attribute warning: memset used with constant zero length parameter; this could be due to transposed parameters [-Werror]
      
      It was intentional that the buffer is set to zero length there.
      ddc21f79
    • Sergey Petrunya's avatar
      Add a debugger helper function that does this: · 260c802e
      Sergey Petrunya authored
      (gdb) p dbug_print_table_row(table)
        $33 = "SUBQUERY2_t1(col_int_key,col_varchar_nokey)=(7,c)"
      260c802e
    • Sergey Petrunya's avatar
      MDEV-5600: Wrong result on 2nd execution of PS depending on the length of the query · 097b6440
      Sergey Petrunya authored
      - Item_direct_view_ref didn't clear its pointer to item_equal in ::cleanup.
      - Some Item_direct_view_ref objects have statement lifetime (i.e. they
        survive across multiple EXECUTE commands). Item_equal objects live only for
        the duration of one EXECUTE. This caused Item_direct_view_ref to have a stale pointer,
        which could cause all sorts of effects. (In this bug's testcase it was pointing to
        the wrong Item_equal, causing wrong query result)
      - Fixed by doing what Item_field::cleanup() does - don't keep item_equal pointer value.
      - There is no testcase because the only testcase I've got is highly fragile (e.g. the
        bug will not show up if @@datadir is of the wrong length).
      097b6440
  11. 18 Feb, 2014 2 commits
  12. 14 Feb, 2014 5 commits
  13. 13 Feb, 2014 6 commits
  14. 12 Feb, 2014 1 commit
  15. 08 Feb, 2014 1 commit
  16. 07 Feb, 2014 3 commits