1. 15 Feb, 2016 16 commits
  2. 14 Feb, 2016 2 commits
  3. 12 Feb, 2016 2 commits
  4. 11 Feb, 2016 3 commits
  5. 10 Feb, 2016 2 commits
  6. 09 Feb, 2016 10 commits
  7. 08 Feb, 2016 4 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
    • Ian Gilfillan's avatar
      typo "Bangalore1" -> "Bangalore" · eb752acc
      Ian Gilfillan authored
      eb752acc
  8. 06 Feb, 2016 1 commit
    • Sergei Golubchik's avatar
      MDEV-9024 Build fails with VS2015 · c4cb2400
      Sergei Golubchik authored
      cherry-pick f1daf9ce from 10.0 branch
      -------------------------------------
      
      Fix build failures caused by new C runtime library
      - isnan, snprintf, struct timespec are now defined, attempt to
      redefine them leads
      - P_tmpdir, tzname are no more defined
      -  lfind() and lsearch() in lf_hash.c had to be renamed,  declaration
      conflicts with some C runtime functions with the same name declared in
      a header included by stdlib.h
      
       Also fix couple of annoying warnings :
      - remove #define NOMINMAX from config.h to avoid "redefined" compiler
      warnings(NOMINMAX is already in compile flags)
      
      - disable incremental linker in Debug as well (feature not used much
      and compiler crashes often)
      
      Also simplify package building with Wix, require Wix 3.9 or later
      (VS2015 is not compatible with old Wix 3.5/3.6)
      c4cb2400