1. 25 Apr, 2007 1 commit
  2. 24 Apr, 2007 4 commits
  3. 23 Apr, 2007 7 commits
  4. 21 Apr, 2007 1 commit
  5. 20 Apr, 2007 15 commits
    • unknown's avatar
      Merge bk-internal.mysql.com:/data0/bk/mysql-5.0 · 8a702a1e
      unknown authored
      into  bk-internal.mysql.com:/data0/bk/mysql-5.0-opt
      
      
      sql/item_cmpfunc.cc:
        Auto merged
      sql/sql_select.cc:
        Auto merged
      sql/sql_show.cc:
        Auto merged
      sql/sql_view.cc:
        Auto merged
      8a702a1e
    • unknown's avatar
      Merge weblab.(none):/home/marcsql/TREE/mysql-5.0-base · 594f7bd2
      unknown authored
      into  weblab.(none):/home/marcsql/TREE/mysql-5.0-rt-merge
      
      
      mysql-test/r/sp.result:
        Auto merged
      mysql-test/t/sp.test:
        Auto merged
      594f7bd2
    • unknown's avatar
      Added missing result file for rpl_critical_errors. · 4a3027aa
      unknown authored
      
      mysql-test/r/rpl_critical_errors.result:
        New BitKeeper file ``mysql-test/r/rpl_critical_errors.result''
      4a3027aa
    • unknown's avatar
      Merge gshchepa.loc:/home/uchum/work/bk-trees/mysql-5.0-opt · 323a2135
      unknown authored
      into  gshchepa.loc:/home/uchum/work/bk-trees/mysql-5.0-opt-27704
      
      
      323a2135
    • unknown's avatar
      Merge debian.(none):/M41/push-4.1 · 11fe01f5
      unknown authored
      into  debian.(none):/M50/push-5.0
      
      
      11fe01f5
    • unknown's avatar
      Merge gshchepa.loc:/home/uchum/work/bk-trees/mysql-4.1-opt-27704 · a501fdd6
      unknown authored
      into  gshchepa.loc:/home/uchum/work/bk-trees/mysql-5.0-opt-27704
      
      
      mysql-test/r/subselect.result:
        Auto merged
      mysql-test/t/row.test:
        Auto merged
      mysql-test/r/row.result:
        Test case updated for Bug#27704 (incorrect comparison
        of rows with NULL components).
      sql/item_cmpfunc.cc:
        Bug#27704: incorrect comparison of rows with NULL components.
      sql/item_cmpfunc.h:
        Bug#27704: incorrect comparison of rows with NULL components.
        Cosmetic fix.
      a501fdd6
    • unknown's avatar
      Merge debian.(none):/M50/mysql-5.0 · 515c6487
      unknown authored
      into  debian.(none):/M50/push-5.0
      
      
      sql/ha_ndbcluster.cc:
        Auto merged
      sql/sql_delete.cc:
        Auto merged
      515c6487
    • unknown's avatar
      Merge debian.(none):/M50/bug27739-5.0 · ad14c247
      unknown authored
      into  debian.(none):/M50/push-5.0
      
      
      configure.in:
        Auto merged
      ad14c247
    • unknown's avatar
      Bug#27704: incorrect comparison of rows with NULL components · a8f639fc
      unknown authored
      Support for NULL components was incomplete for row comparison,
      fixed.  Added support for abort_on_null at compare_row() like
      in 5.x
      
      
      sql/item_cmpfunc.h:
        Bug#27704: incorrect comparison of rows with NULL components
        Added support for abort_on_null at Item_bool_func2
        like in 5.x
      sql/item_cmpfunc.cc:
        Bug#27704: incorrect comparison of rows with NULL components
        Support for NULL components was incomplete for row comparison,
        fixed. Added support for abort_on_null at compare_row() like
        in 5.x
      mysql-test/t/row.test:
        Test case updated for Bug#27704 (incorrect comparison 
        of rows with NULL components)
      mysql-test/r/row.result:
        Test case updated for Bug#27704 (incorrect comparison 
        of rows with NULL components)
      mysql-test/r/subselect.result:
        Test case updated for Bug#27704 (incorrect comparison 
        of rows with NULL components)
      a8f639fc
    • unknown's avatar
      Merge gkodinov@bk-internal.mysql.com:/home/bk/mysql-5.0-opt · a4ffe9e4
      unknown authored
      into  magare.gmz:/home/kgeorge/mysql/autopush/B27786-5.0-opt
      
      
      a4ffe9e4
    • unknown's avatar
      Bug #24778: Innodb: No result when using ORDER BY · f3e261a9
      unknown authored
      This bug was intruduced by the fix for bug#17212 (in 4.1). It is not 
      ok to call test_if_skip_sort_order since this function will 
      alter the execution plan. By contract it is not ok to call 
      test_if_skip_sort_order in this context.
      
      This bug appears only in the case when the optimizer has chosen 
      an index for accessing a particular table but finds a covering 
      index that enables it to skip ORDER BY. This happens in 
      test_if_skip_sort_order.
      
      
      mysql-test/r/key.result:
        Bug#24778
        
        test case.
        
        The bug causes the result to be the empty set.
      mysql-test/t/key.test:
        Bug#24778
        
        The minimal test case that reveals the bug. The reason for such a 
        complicated schema is that we have to convince the optimizer to 
        pick one index, then discard it in order to be able to skip 
        ORDER BY.
      sql/sql_select.cc:
        bug#24778
        
        Removed the call to test_if_skip_sort_order that constituted the
        bug.
      f3e261a9
    • unknown's avatar
      configure.in : Ensure that "icheck" is really the ABI checker, · 26aba3fb
      unknown authored
                       not some other tool (file system checker on Tru64).
      
      Patch originally supplied by Peter O'Gorman, slightly modified by me.
      
      Bug#27739 "build fails on Tru64 due to icheck test in configure"
      
      
      configure.in:
        We use "icheck" as a tool to check against ABI changes.
        However, some systems (like Tru64) have "icheck" as a file system checker.
        So if "icheck" is found, it should be verified that this really is the
        ABI checker and not some other tool.
        
        Patch originally supplied by Peter O'Gorman, slightly modified by me.
        
        Bug#27739 "build fails on Tru64 due to icheck test in configure"
      26aba3fb
    • unknown's avatar
      Merge romeo.(none):/home/bkroot/mysql-5.0-rpl · 8bc4d182
      unknown authored
      into  romeo.(none):/home/bk/merge-mysql-5.0
      
      
      client/mysql.cc:
        Auto merged
      sql/mysql_priv.h:
        Auto merged
      sql/mysqld.cc:
        Auto merged
      sql/set_var.cc:
        Auto merged
      sql/slave.cc:
        Auto merged
      sql/sql_class.cc:
        Auto merged
      8bc4d182
    • unknown's avatar
      Merge mkindahl@bk-internal.mysql.com:/home/bk/mysql-5.0-rpl · b6451440
      unknown authored
      into  romeo.(none):/home/bkroot/mysql-5.0-rpl
      
      
      b6451440
    • unknown's avatar
      Bug #27786: · e0444ba4
      unknown authored
      When merging views into the enclosing statement
      the ORDER BY clause of the view is merged to the
      parent's ORDER BY clause.
      However when the VIEW is merged into an UNION
      branch the ORDER BY should be ignored. 
      Use of ORDER BY for individual SELECT statements
      implies nothing about the order in which the rows
      appear in the final result because UNION by default
      produces unordered set of rows.
      Fixed by ignoring the ORDER BY clause from the merge
      view when expanded in an UNION branch.
      
      
      mysql-test/r/view.result:
        Bug #27786: test case
      mysql-test/t/view.test:
        Bug #27786: test case
      sql/sql_lex.h:
        Bug #27786: add a is_union() inlined function
        Returns true if the unit represents an UNION.
      sql/sql_view.cc:
        Bug #27786: ignore ORDER BY in mergeable views when in UNION context
      e0444ba4
  6. 19 Apr, 2007 2 commits
  7. 18 Apr, 2007 5 commits
    • unknown's avatar
      Merge jbruehe@bk-internal.mysql.com:/home/bk/mysql-5.0-build · 253da118
      unknown authored
      into  debian.(none):/M50/push-5.0
      
      
      253da118
    • unknown's avatar
      Merge trift2.:/MySQL/M50/fix-ndb-5.0 · 7cf07804
      unknown authored
      into  trift2.:/MySQL/M50/push-5.0
      
      
      7cf07804
    • unknown's avatar
      sql/ha_ndbcluster.cc · 0e42267f
      unknown authored
          Hex constants that exceed 32 bit need to be marked "LL" for the compile to work.
      
      
      sql/ha_ndbcluster.cc:
        Hex constants that exceed 32 bit need to be marked "LL" for the compile to work
        (discovered on a Debian PPC box, 32-bit big-endian, running gcc 3.3.6).
      0e42267f
    • unknown's avatar
      Merge jbruehe@bk-internal.mysql.com:/home/bk/mysql-5.0-build · d0e3b172
      unknown authored
      into  debian.(none):/M50/push-5.0
      
      
      configure.in:
        Auto merged
      d0e3b172
    • unknown's avatar
      Fixed bug #27870. The bug that causes crashes manifests itself at some · 579c2bff
      unknown authored
      conditions when executing an equijoin query with WHERE condition
      containing a subquery predicate of the form join_attr NOT IN (SELECT ...).
      
      To resolve a problem of the correct evaluation of the expression
        attr NOT IN (SELECT ...)
      an array of guards is created to make it possible to filter out some 
      predicates of the EXISTS subquery into which the original subquery 
      predicate is transformed, in the cases when a takes the NULL value. 
      If attr is defined as a field that cannot be NULL than such an array 
      is not needed and is not created. 
      However if the field a occurred also an an equijoin predicate t2.a=t1.b
      and table t1 is accessed before table t2 then it may happen that the 
      the EXISTS subquery is pushed down to the condition evaluated just after
      table t1 has been accessed. In this case any occurrence of t2.a is 
      substituted for t1.b. When t1.b takes the value of NULL an attempt is 
      made to turn on the corresponding guard. This action caused a crash as 
      no guard array had been created.
      
      Now the code of Item_in_subselect::set_cond_guard_var checks that the guard
      array has been created before setting a guard variable on. Otherwise the
      method does nothing. It cannot results in returning a row that could be
      rejected as the condition t2.a=t1.b will be checked later anyway.        
      
      
      mysql-test/r/subselect3.result:
        Added a test case for bug #27870.
      mysql-test/t/subselect3.test:
        Added a test case for bug #27870.
      sql/item_subselect.h:
        Fixed bug #27870. The bug that causes crashes manifests itself at some
        conditions when executing an equijoin query with WHERE condition
        containing a subquery predicate of the form join_attr NOT IN (SELECT ...).
        
        Forced Item_in_subselect::set_cond_guard_var to check that the guard
        array has been created before setting a guard variable on. Otherwise the
        method does nothing.
      579c2bff
  8. 17 Apr, 2007 5 commits