1. 05 Aug, 2007 1 commit
  2. 04 Aug, 2007 3 commits
  3. 03 Aug, 2007 9 commits
  4. 02 Aug, 2007 11 commits
    • unknown's avatar
      Merge gleb.loc:/home/uchum/work/bk/5.0-opt · bba712a6
      unknown authored
      into  gleb.loc:/home/uchum/work/bk/5.1-opt
      
      
      mysql-test/r/select.result:
        Auto merged
      mysql-test/t/select.test:
        Auto merged
      sql/sql_parse.cc:
        Auto merged
      sql/unireg.h:
        Auto merged
      sql/share/errmsg.txt:
        Merge with 5.0-opt.
      bba712a6
    • unknown's avatar
      Merge gshchepa@bk-internal.mysql.com:/home/bk/mysql-5.0-opt · cf145f8f
      unknown authored
      into  gleb.loc:/home/uchum/work/bk/5.0-opt
      
      
      cf145f8f
    • unknown's avatar
      Merge gleb.loc:/home/uchum/work/bk/5.0-opt-27352 · 30f63c14
      unknown authored
      into  gleb.loc:/home/uchum/work/bk/5.0-opt
      
      
      sql/sql_parse.cc:
        Auto merged
      30f63c14
    • unknown's avatar
      Fixed bug #27352. · a53510f0
      unknown authored
      The SELECT query with more than 31 nested dependent SELECT queries returned
      wrong result.
      
      New error message has been added: ER_TOO_HIGH_LEVEL_OF_NESTING_FOR_SELECT.
      It will be reported as: "Too high level of nesting for select".
      
      
      sql/sql_parse.cc:
        Fixed bug #27352.
        The Item_sum::register_sum_func method has been modified to return
        TRUE on exceeding of allowed level of SELECT nesting and to report
        corresponding error message.
      sql/unireg.h:
        Fixed bug #27352.
        Constant definition has been added: maximal allowed level of SELECT nesting.
      mysql-test/t/select.test:
        Updated test case for bug #27352.
      mysql-test/r/select.result:
        Updated test case for bug #27352.
      sql/share/errmsg.txt:
        Fixed bug #27352.
        New error message has been added: ER_TOO_HIGH_LEVEL_OF_NESTING_FOR_SELECT.
      a53510f0
    • unknown's avatar
      Fixed bug#28404. · c9049374
      unknown authored
      This patch adds cost estimation for the queries with ORDER BY / GROUP BY
      and LIMIT. 
      If there was a ref/range access to the table whose rows were required
      to be ordered in the result set the optimizer always employed this access
      though a scan by a different index that was compatible with the required 
      order could be cheaper to produce the first L rows of the result set.
      Now for such queries the optimizer makes a choice between the cheapest
      ref/range accesses not compatible with the given order and index scans
      compatible with it.
      
      
      mysql-test/r/distinct.result:
        Adjusted results for test cases affected fy the fix for bug #28404.
      mysql-test/r/endspace.result:
        Adjusted results for test cases affected fy the fix for bug #28404.
      mysql-test/r/group_by.result:
        Adjusted results for test cases affected fy the fix for bug #28404.
      mysql-test/r/group_min_max.result:
        Adjusted results for test cases affected fy the fix for bug #28404.
      mysql-test/r/innodb.result:
        Adjusted results for test cases affected fy the fix for bug #28404.
      mysql-test/r/innodb_mysql.result:
        Adjusted results for test cases affected fy the fix for bug #28404.
      mysql-test/r/merge.result:
        Adjusted results for test cases affected fy the fix for bug #28404.
      mysql-test/r/order_by.result:
        Added a test case for bug #28404.
      mysql-test/r/select_found.result:
        Adjusted results for test cases affected fy the fix for bug #28404.
      mysql-test/r/subselect.result:
        Adjusted results for test cases affected fy the fix for bug #28404.
      mysql-test/t/distinct.test:
        Changed a test case after adding the fix for bug #28404.
      mysql-test/t/order_by.test:
        Added a test case for bug #28404.
      sql/sql_select.cc:
        Fixed bug#28404.
        This patch adds cost estimation for the queries with ORDER BY / GROUP BY
        and LIMIT. 
        Now for such queries the optimizer makes a choice between the cheapest
        ref/range accesses not compatible with the given order and index scans
        compatible with it.
        
        Modified the function test_if_skip_sort_order to make the above mentioned
        choice cost based.
      sql/sql_select.h:
        Fixed bug#28404.
        This patch adds cost estimation for the queries with ORDER BY / GROUP BY
        and LIMIT. 
        Added a new field fot the JOIN_TAB structure.
      c9049374
    • unknown's avatar
      mysqld.cc: · cb3df6f2
      unknown authored
        Post merge changes.
      
      
      sql/mysqld.cc:
        Post merge changes.
      cb3df6f2
    • unknown's avatar
      sql_class.h: · d24df2c6
      unknown authored
        After merge changes.
      
      
      sql/sql_class.h:
        After merge changes.
      d24df2c6
    • unknown's avatar
      Merge moonbone.local:/mnt/gentoo64/work/24989-bug-5.0-opt-mysql · 597ca958
      unknown authored
      into  moonbone.local:/mnt/gentoo64/work/test-5.1-opt-mysql
      
      
      sql/mysqld.cc:
        SCCS merged
      597ca958
    • unknown's avatar
      Merge moonbone.local:/mnt/gentoo64/work/24989-bug-5.0-opt-mysql · 1e6f1764
      unknown authored
      into  moonbone.local:/mnt/gentoo64/work/test-5.1-opt-mysql
      
      
      sql/handler.cc:
        Auto merged
      sql/sp_head.cc:
        Auto merged
      sql/sp_rcontext.cc:
        Auto merged
      sql/sql_select.cc:
        Auto merged
      sql/sql_select.h:
        Auto merged
      sql/sql_union.cc:
        Auto merged
      mysql-test/include/read_many_rows.inc:
        Manually merged
      mysql-test/r/read_many_rows_innodb.result:
        Manually merged
      sql/sql_class.cc:
        Manually merged
      sql/sql_class.h:
        Manually merged
      storage/innobase/handler/ha_innodb.cc:
        Manually merged
      1e6f1764
    • unknown's avatar
      Bug #30193: crash during drop table and kill · d0536d02
      unknown authored
      When DROP TABLE detects that it has been killed
      by another thread it must unlock the table names
      it locked.
      
      Fixed by backporting the 5.1 error handling code.
      
      
      sql/sql_table.cc:
        Bug #30193: correct error handling when a thread 
        is killed inside DROP TABLE.
      d0536d02
    • unknown's avatar
      Addendum to bug 29325 · 8277581b
      unknown authored
      keep_files_on_create made a startup option
      
      
      sql/mysqld.cc:
        Addendum to bug #29325
        keep_files_on_create made a startup option
      8277581b
  5. 31 Jul, 2007 16 commits