An error occurred fetching the project authors.
  1. 13 Aug, 2005 2 commits
  2. 12 Aug, 2005 1 commit
    • timour@mysql.com's avatar
      Implementation of WL#2486 - · a247282a
      timour@mysql.com authored
      "Process NATURAL and USING joins according to SQL:2003".
      
      * Some of the main problems fixed by the patch:
        - in "select *" queries the * expanded correctly according to
          ANSI for arbitrary natural/using joins
        - natural/using joins are correctly transformed into JOIN ... ON
          for any number/nesting of the joins.
        - column references are correctly resolved against natural joins
          of any nesting and combined with arbitrary other joins.
      
      * This patch also contains a fix for name resolution of items
        inside the ON condition of JOIN ... ON - in this case items must
        be resolved only against the JOIN operands. To support such
        'local' name resolution, the patch introduces a stack of
        name resolution contexts used at parse time.
      
      NOTICE:
      - This patch is not complete in the sense that
        - there are 2 test cases that still do not pass -
          one in join.test, one in select.test. Both are marked
          with a comment "TODO: WL#2486".
        - it does not include a new test specific for the task
      a247282a
  3. 08 Aug, 2005 2 commits
    • igor@rurik.mysql.com's avatar
      subselect.test, subselect.result: · 73be194f
      igor@rurik.mysql.com authored
        Added a test case for bug #12392.
      item_cmpfunc.cc:
        Fixed bug #12392.
        Missing handling of rows containing NULL components
        when evaluating IN predicates caused a crash.
      73be194f
    • monty@mysql.com's avatar
      Review of new pushed code · 99cb0835
      monty@mysql.com authored
      - Fixed some error condtion when handling dates with 'T'
      - Added extra test for bug #11867 (Wrong result with "... WHERE ROW( a, b ) IN ( SELECT DISTINCT a, b WHERE ...)" to show it's not yet fixed
      - Safety fixes and cleanups
      99cb0835
  4. 07 Aug, 2005 2 commits
    • igor@rurik.mysql.com's avatar
      subselect.result: · dafbb34d
      igor@rurik.mysql.com authored
        Correction after manual merge.
      dafbb34d
    • igor@rurik.mysql.com's avatar
      subselect.result: · b2a189ab
      igor@rurik.mysql.com authored
        Added test case for bug #11867.
        Fixed results for two existing test cases.
      subselect.test:
        Added test case for bug #11867.
      item_subselect.cc:
        Fixed bug #11867.
        Added missing code in Item_in_subselect::row_value_transformer
        that caused problems for queries with
        ROW(elems) IN (SELECT DISTINCT cols FROM ...).
      b2a189ab
  5. 30 Jul, 2005 1 commit
    • evgen@moonbone.local's avatar
      Fix bug #11335 View redefines TinyInt(1) column definition · fa0ea365
      evgen@moonbone.local authored
      Item_type_holder doesn't store information about length and exact type of
      original item which results in redefining length to max_length and geometry 
      type to longtext.
      
      Changed the way derived tables except unions are built. Now they are created
      from original field list instead of list of Item_type_holder.
      fa0ea365
  6. 12 Jul, 2005 1 commit
  7. 23 Jun, 2005 2 commits
    • bell@sanja.is.com.ua's avatar
      fixed encrypt() name · ec444444
      bell@sanja.is.com.ua authored
      ec444444
    • igor@rurik.mysql.com's avatar
      opt_range.cc: · 893c6c9b
      igor@rurik.mysql.com authored
        Fixed buf #11487.
        Added a call of  QUICK_RANGE_SELECT::init to the
        QUICK_RANGE_SELECT::reset method. Without it the second
        evaluation of a subquery employing the range access failed.
      subselect.result, subselect.test:
        Added a test case for bug #11487.
      893c6c9b
  8. 20 May, 2005 2 commits
  9. 18 May, 2005 1 commit
  10. 16 May, 2005 1 commit
  11. 16 Apr, 2005 2 commits
    • igor@rurik.mysql.com's avatar
      subselect.result, subselect.test: · d92d4007
      igor@rurik.mysql.com authored
        Added a test case for bug #9516.
      item_subselect.h:
        Fixed bug #9516.
        The bug was due to that fact that the class Item_subselect
        inherited the generic implementation of the function
        not_null_tables that was not valid for the objects
        of this class. As a result evaluation of the
        not_null_tables attribute was not correct for subqueries.
        This caused invalid transformations of outer joins into
        inner joins.
      d92d4007
    • igor@rurik.mysql.com's avatar
      subselect.result, subselect.test: · 0f043429
      igor@rurik.mysql.com authored
        Added a test case for bug #9338.
      sql_select.cc:
        Fixed bug #9338.
        When an occurence of a field reference has to be replaced
        by another field reference the whole Item_field must be
        replaced.
      item.cc:
        Fixed bug #9338.
        The method Item_field::replace_equal_field_processor was
        replaced by Item_field::replace_equal_field. The new method
        is used to replace the occurences of Item_field objects.
      item.h:
        Fixed bug #9338.
        The virtual function replace_equal_field_processor was replaced
        by replace_equal_field. The latter is supposed to be used as a
        callback function in calls of the method transform.
      0f043429
  12. 01 Apr, 2005 1 commit
    • monty@mysql.com's avatar
      Invalid DEFAULT values for CREATE TABLE now generates errors. (Bug #5902) · 201ee3eb
      monty@mysql.com authored
      CAST() now produces warnings when casting a wrong INTEGER or CHAR values. This also applies to implicite string to number casts. (Bug #5912)
      ALTER TABLE now fails in STRICT mode if it generates warnings.
      Inserting a zero date in a DATE, DATETIME or TIMESTAMP column during TRADITIONAL mode now produces an error. (Bug #5933)
      201ee3eb
  13. 30 Mar, 2005 1 commit
  14. 10 Mar, 2005 1 commit
  15. 24 Feb, 2005 1 commit
  16. 21 Feb, 2005 1 commit
  17. 14 Feb, 2005 1 commit
  18. 12 Feb, 2005 1 commit
    • sergefp@mysql.com's avatar
      Fix for BUG#8218: · c0c50efd
      sergefp@mysql.com authored
      Remove TMP_TABLE_PARAM::copy_funcs_it. TMP_TABLE_PARAM is a member of JOIN which is 
      copied via memcpy, and List_iterator_fast TMP_TABLE_PARAM::copy_funcs_it ends up 
      pointing to the wrong List.
      c0c50efd
  19. 09 Feb, 2005 1 commit
  20. 08 Feb, 2005 1 commit
  21. 06 Feb, 2005 1 commit
  22. 26 Jan, 2005 1 commit
  23. 24 Jan, 2005 3 commits
  24. 18 Jan, 2005 1 commit
  25. 31 Dec, 2004 1 commit
  26. 30 Dec, 2004 1 commit
  27. 26 Dec, 2004 2 commits
    • igor@rurik.mysql.com's avatar
      subselect.result, subselect.test: · 04974868
      igor@rurik.mysql.com authored
        Added a couple of new test cases for bug #7351.
      04974868
    • igor@rurik.mysql.com's avatar
      subselect.result, subselect.test: · d3fa2453
      igor@rurik.mysql.com authored
        Added test cases for bug #7351.
      item_cmpfunc.cc:
        Fixed bug #7351: incorrect result for a query with a
        subquery returning empty set.
        If in the predicate v IN (SELECT a FROM t WHERE cond)
        v is null, then the result of the predicate is either
        INKNOWN or FALSE. It is FALSE if the subquery returns
        an empty set.
      item_subselect.cc:
        Fixed bug #7351: incorrect result for a query with a
        subquery returning empty set.
        The problem was due to not a quite legal transformation
        for 'IN' subqueries. A subquery containing a predicate
        of the form
        v IN (SELECT a FROM t WHERE cond)
        was transformed into
        EXISTS(SELECT a FROM t WHERE cond AND (a=v OR a IS NULL)).
        Yet, this transformation is valid only if v is not null.
        If v is null, then, in the case when
        (SELECT a FROM t WHERE cond) returns an empty set the value
        of the predicate is FALSE, otherwise the result of the
        predicate is INKNOWN.
        The fix resolves this problem by changing the result
        of the transformation to
        EXISTS(SELECT a FROM t WHERE cond AND (v IS NULL OR (a=v OR a IS NULL)))
        in the case when v is nullable.
        The new transformation prevents applying the lookup
        optimization for IN subqueries. To make it still
        applicable we have to introduce guarded access methods.
      d3fa2453
  28. 14 Dec, 2004 1 commit
  29. 12 Dec, 2004 1 commit
  30. 11 Dec, 2004 1 commit
  31. 07 Dec, 2004 1 commit