1. 04 Jun, 2010 1 commit
  2. 27 May, 2010 1 commit
    • Sergey Petrunya's avatar
      MWL#90: Subqueries: Inside-out execution for non-semijoin materialized... · 0cc37246
      Sergey Petrunya authored
      MWL#90: Subqueries: Inside-out execution for non-semijoin materialized subqueries that are AND-parts of the WHERE
      - Change "SUBQUERY#n" to "<subquery{n}>" in EXPLAIN output. We need to it to be
        lowercase so that EXPLAIN results do not differ in case between systems with
        case-sensitive and case-insensitive filesystems.
      - Remove garbage comments, add better comments.
      0cc37246
  3. 25 May, 2010 3 commits
  4. 24 May, 2010 2 commits
  5. 23 May, 2010 1 commit
  6. 11 May, 2010 1 commit
  7. 10 May, 2010 1 commit
    • Sergey Petrunya's avatar
      Subquery optimizations: · b9688830
      Sergey Petrunya authored
      - Better comments
      - Use more appropriate return types for functions
      - Provide handling where it was missing.
      b9688830
  8. 03 May, 2010 1 commit
  9. 25 Apr, 2010 1 commit
  10. 06 Apr, 2010 6 commits
  11. 05 Apr, 2010 2 commits
  12. 02 Apr, 2010 1 commit
  13. 29 Mar, 2010 2 commits
  14. 23 Mar, 2010 1 commit
  15. 21 Mar, 2010 2 commits
  16. 20 Mar, 2010 3 commits
  17. 15 Mar, 2010 6 commits
    • unknown's avatar
      MWL#68: Subquery optimization: Efficient NOT IN execution with NULLs · e0642712
      unknown authored
      Fix for the PBXT copy of subselect.test.
      e0642712
    • unknown's avatar
    • Sergei Golubchik's avatar
      merged · f09ca00e
      Sergei Golubchik authored
      f09ca00e
    • Sergey Petrunya's avatar
      Merge · 816a579f
      Sergey Petrunya authored
      816a579f
    • Sergey Petrunya's avatar
      Apply fix by Roy Lyseng: · 47d0cf29
      Sergey Petrunya authored
      Bug#48623: Multiple subqueries are optimized incorrectly
            
      The function setup_semijoin_dups_elimination() has a major loop that
      goes through every table in the JOIN object. Usually, there is a normal
      "plus one" increment in the for loop that implements this, but each semijoin
      nest is treated as one entity and there is another increment that skips past
      the semijoin nest to the next table in the JOIN object. However, when
      combining these two increments, the next joined table is skipped, and if that
      happens to be the start of another semijoin nest, the correct processing
      for that nest will not be carried out.
      
      mysql-test/r/subselect_sj.result:
        Added test results for bug#48623
      mysql-test/r/subselect_sj_jcl6.result:
        Added test results for bug#48623
      mysql-test/t/subselect_sj.test:
        Added test case for bug#48623
      sql/opt_subselect.cc:
        Omitted the "plus one" increment in the for loop, added "plus one"
        in the remaining switch case, fixed coding style issue in remaining
        increment operations.
      47d0cf29
    • Sergey Petrunya's avatar
      85c8bce7
  18. 14 Mar, 2010 3 commits
  19. 13 Mar, 2010 2 commits
    • Sergey Petrunya's avatar
      Apply fix by oystein.grovlen@sun.com 2010-03-12: · ea982e33
      Sergey Petrunya authored
      Bug#48213 Materialized subselect crashes if using GEOMETRY type
      
      The problem occurred because during semi-join a materialized table
      was created which contained a GEOMETRY column, which is a specialized
      BLOB column.  This caused an segmentation fault because such tables will
      have extra columns, and the semi-join code was not prepared for that.
      
      The solution is to disable materialization when Blob/Geometry columns would 
      need to be materialized.  Blob columns cannot be used for index look-up 
      anyway, so it does not makes sense to use materialization.
      
      This fix implies that it is detected earlier that subquery materialization
      can not be used.  The result of that is that in->exist optimization may
      be performed for such queries.  Hence, extended query plans for such
      queries had to be updated.
      
      mysql-test/r/subselect_mat.result:
        Update extended query plan for subqueries that cannot use materialization
        due to Blobs.
      mysql-test/r/subselect_sj.result:
        Updated result file.
      mysql-test/r/subselect_sj_jcl6.result:
        Update result file.
      mysql-test/t/subselect_sj.test:
        Add test case for Bug#48213 that verifies that semi-join works when subquery select list contain Blob columns.  Also verify that materialization is not
        used.
      sql/opt_subselect.cc:
        Disable materialization for semi-join/subqueries when the subquery select list
        contain Blob columns.
      ea982e33
    • Sergey Petrunya's avatar
      BUG#45174: XOR in subqueries produces differing results in 5.1 and 5.4 · 02e9fa62
      Sergey Petrunya authored
      BUG#50019: Wrong result for IN-subquery with materialization
      - Fix equality substitution in presense of semi-join materialization, lookup and scan variants
        (started off from fix by Evgen Potemkin, then modified it to work in all cases)
      02e9fa62