An error occurred fetching the project authors.
  1. 20 May, 2005 1 commit
  2. 16 May, 2005 1 commit
  3. 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
  4. 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
  5. 31 Mar, 2005 1 commit
  6. 30 Mar, 2005 1 commit
  7. 10 Mar, 2005 1 commit
  8. 21 Feb, 2005 1 commit
  9. 14 Feb, 2005 1 commit
  10. 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
  11. 09 Feb, 2005 1 commit
  12. 06 Feb, 2005 1 commit
  13. 26 Jan, 2005 1 commit
  14. 24 Jan, 2005 3 commits
  15. 18 Jan, 2005 1 commit
  16. 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
  17. 14 Dec, 2004 1 commit
  18. 11 Dec, 2004 1 commit
  19. 25 Nov, 2004 1 commit
  20. 22 Nov, 2004 1 commit
  21. 18 Nov, 2004 1 commit
  22. 16 Nov, 2004 1 commit
  23. 15 Nov, 2004 2 commits
  24. 27 Oct, 2004 1 commit
  25. 17 Sep, 2004 1 commit
  26. 06 Sep, 2004 1 commit
  27. 24 Aug, 2004 1 commit
  28. 23 Aug, 2004 1 commit
  29. 21 Aug, 2004 1 commit
    • hf@deer.(none)'s avatar
      Proposed fix for bug #5003 (subselect with MIN() and LIKE crashes server) · 6c136f99
      hf@deer.(none) authored
      We have next problem here:
      active_index is wrong in the subselect's handler on the second val_int() call.
      Optimizer sees that we can use index-read for that kind of condition,
      and matching_cond() (sql/opt_sum.cc) doesn't. I suspect, proper solution is
      to add appropriate code to the matching_cond() but now just added
      missed initialization.
      6c136f99
  30. 19 Aug, 2004 1 commit
  31. 13 Aug, 2004 1 commit
  32. 12 Aug, 2004 1 commit
  33. 04 Jul, 2004 1 commit
  34. 22 Jun, 2004 1 commit
  35. 18 Jun, 2004 1 commit