1. 17 Feb, 2016 1 commit
  2. 16 Feb, 2016 1 commit
  3. 13 Feb, 2016 1 commit
  4. 10 Feb, 2016 12 commits
  5. 09 Feb, 2016 10 commits
  6. 08 Feb, 2016 3 commits
    • Sergei Petrunia's avatar
      MDEV-6859: scalar subqueries in a comparison produced unexpected result · b17a4350
      Sergei Petrunia authored
      When one evaluates row-based comparison like (X, Y) = (A,B), one should
      first call bring_value() for the Item that returns row value. If you
      don't do that and just attempt to read values of X and Y, you get stale
      values.
      Semi-join/Materialization can take a row-based comparison apart and
      make ref access from it. In that case, we need to call bring_value()
      to get the index lookup components.
      b17a4350
    • Sergei Golubchik's avatar
      5.5.47-37.7 · 3cfd36bb
      Sergei Golubchik authored
      3cfd36bb
    • Sergei Petrunia's avatar
      MDEV-7823: Server crashes in next_depth_first_tab on nested IN clauses with SQ inside · d443d70d
      Sergei Petrunia authored
      Consider a query with subquery in form t.key=(select ...). Suppose, the
      parent query uses this equality for ref access.
      It will attempt to evaluate the subquery in get_best_combination(),
      right before the join->join_tab[...] array is filled.  The problem was
      that subquery optimization will attempt to look at parent's join->join_tab
      to check how many times subquery will be executed (and crash).
      
      Fixed by not doing that when the subquery is constant (non-constant
      subqueries are only be evaluated during join execution, so they are not
      affected)
      d443d70d
  7. 06 Feb, 2016 8 commits
  8. 05 Feb, 2016 2 commits
  9. 03 Feb, 2016 2 commits