An error occurred fetching the project authors.
  1. 19 Dec, 2011 1 commit
    • unknown's avatar
      Backport of WL#5953 from MySQL 5.6 · 4880bfa0
      unknown authored
      The patch differs from the original MySQL patch as follows:
      - All test case differences have been reviewed one by one, and
        care has been taken to restore the original plan so that each
        test case executes the code path it was designed for.
      - A bug was found and fixed in MariaDB 5.3 in
        Item_allany_subselect::cleanup().
      - ORDER BY is not removed because we are unsure of all effects,
        and it would prevent enabling ORDER BY ... LIMIT subqueries.
      - ref_pointer_array.m_size is not adjusted because we don't do
        array bounds checking, and because it looks risky.
      
      Original comment by Jorgen Loland:
      -------------------------------------------------------------
      WL#5953 - Optimize away useless subquery clauses
            
      For IN/ALL/ANY/SOME/EXISTS subqueries, the following clauses are 
      meaningless:
            
      * ORDER BY (since we don't support LIMIT in these subqueries)
      * DISTINCT
      * GROUP BY if there is no HAVING clause and no aggregate 
        functions
            
      This WL detects and optimizes away these useless parts of the
      query during JOIN::prepare()
      4880bfa0
  2. 15 Dec, 2011 2 commits
  3. 05 Dec, 2011 1 commit
    • Sergey Petrunya's avatar
      Bug #899962: materialized subquery with join_cache_level=3 · f949009b
      Sergey Petrunya authored
      - Make create_tmp_table() set KEY_PART_INFO attributes for the keys it creates.
        This wasn't needed before but is needed now, when temp. tables that are 
        results of SJ-Materialization are being used for joins.
        This particular bug depended on HA_VAR_LENGTH_PART being set,
        but also added code to set HA_BLOB_PART and HA_NULL_PART when appropriate.
      f949009b
  4. 04 Dec, 2011 1 commit
    • Igor Babaev's avatar
      Fixed LP bug #899696. · fbb764a7
      Igor Babaev authored
      If has been decided that the first match strategy is to be used to join table T
      from a semi-join nest while no buffer can be employed to join this table
      then no join buffer can be used to join any table in the join sequence between
      the first one belonging to the semi-join nest and table T.
      
       
      fbb764a7
  5. 30 Nov, 2011 1 commit
    • Igor Babaev's avatar
      Fixed LP bug #898073. · 388a8f33
      Igor Babaev authored
      The tables from the same semi-join or outer join nest cannot use
      join buffers if in the join sequence of the query execution plan
      they are separated by a table that is planned to be joined without
      usage of a join buffer.
      388a8f33
  6. 15 Jul, 2011 1 commit
  7. 08 Jul, 2011 1 commit
    • Sergey Petrunya's avatar
      Set the default to be mrr=off,mrr_sort_keys=off: · 3cba48a5
      Sergey Petrunya authored
      - Set the default
      - Adjust the testcases so that 'new' tests are run with optimizations turned on.
      - Pull out relevant tests from "irrelevant" tests and run them with optimizations on.
      - Run range.test and innodb.test with both mrr=on and mrr=off
      3cba48a5
  8. 27 Oct, 2010 1 commit
  9. 31 Aug, 2010 1 commit
  10. 17 Jan, 2010 1 commit
  11. 21 Dec, 2009 1 commit