An error occurred fetching the project authors.
  1. 27 Oct, 2010 1 commit
  2. 31 Aug, 2010 1 commit
  3. 16 Jul, 2010 1 commit
    • Sergey Petrunya's avatar
      Fix @@optimizer_switch support · 13058d80
      Sergey Petrunya authored
      - Let "mysqld  --help --verbose" list all optimizer options
      - Make it possible to add new @@optimizer_switch flags w/o causing .result 
        changes all over the testsuite:
        = Remove "select @@optimizer_switch" from tests that do not need all switches
        = Move @@optimizer_switch-specific tests to t/optimizer_switch.test
      13058d80
  4. 15 Mar, 2010 1 commit
    • 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
  5. 14 Mar, 2010 1 commit
    • Sergey Petrunya's avatar
      BUG#43768: Prepared query with nested subqueries core dumps on second execution · 77e66c69
      Sergey Petrunya authored
      Fix two problems:
      1. Let optimize_semijoin_nests() reset sj_nest->sjmat_info irrespectively  
         of value of optimizer_flag. We need this in case somebody has turned optimization
         off between reexecutions of the same statement.
      
      2. Do not pull out constant tables out of semi-join nests. The problem is that pullout 
         operation is not undoable, and if a table is constant because it is 1/0-row table it 
         may cease to be constant on the next execution. Note that tables that are constant
         because of possible eq_ref(const) access will still be pulled out as they are
         considered functionally-dependent.
      77e66c69
  6. 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
  7. 24 Feb, 2010 1 commit
    • Sergey Petrunya's avatar
      Bug#49198 Wrong result for second call of of procedure with view in subselect. · 0e7c8415
      Sergey Petrunya authored
      Re-worked fix of Tor Didriksen:
       The problem was that fix_after_pullout() after semijoin conversion 
       wasn't propagated from the view to the underlying table. 
       On subesequent executions of the prepared statement, 
       we would mark the underlying table as 'dependent' and the predicate 
       anlysis would lead to a different (and illegal) execution plan.
      0e7c8415
  8. 21 Feb, 2010 2 commits
  9. 11 Feb, 2010 1 commit
  10. 17 Jan, 2010 1 commit