An error occurred fetching the project authors.
  1. 24 Oct, 2007 1 commit
  2. 13 Jun, 2007 1 commit
    • joerg@trift2.'s avatar
      sql/item_func.cc · 018a5d40
      joerg@trift2. authored
          Improved check for thread identity in the "embedded" case,
          provided by Monty.
          
          This finishes the fixes for bug#27078.
      018a5d40
  3. 03 May, 2007 1 commit
    • evgen@moonbone.local's avatar
      Bug#23656: Wrong conversion result of a DATETIME to integer using CAST function. · 7f9411c1
      evgen@moonbone.local authored
      The generic string to int conversion was used by the Item_func_signed and
      the Item_func_unsigned classes to convert DATE/DATETIME values to the
      SIGNED/UNSIGNED type. But this conversion produces wrong results for such
      values.
      
      Now if the item which result has to be converted can return its result as
      longlong then the item->val_int() method is used to allow the item to carry
      out the conversion itself and return the correct result.
      This condition is checked in the Item_func_signed::val_int() and the
      Item_func_unsigned::val_int() functions.
      7f9411c1
  4. 12 Apr, 2007 1 commit
  5. 26 Jan, 2007 1 commit
    • igor@olga.mysql.com's avatar
      Fixed bug #24653. · 36df33d8
      igor@olga.mysql.com authored
      The bug report has demonstrated the following two problems.
      1. If an ORDER/GROUP BY list includes a constant expression being 
      optimized away and, at the same time, containing single-row
      subselects that return more that one row, no error is reported.
      Strictly speaking the standard allows to ignore error in this case.
      Yet, now a corresponding fatal error is reported in this case.
      2. If a query requires sorting by expressions containing single-row
      subselects that, however, return more than one row, then the execution
      of the query may cause a server crash. 
      To fix this some code has been added that blocks execution of a subselect
      item in case of a fatal error in the method Item_subselect::exec.
      36df33d8
  6. 22 Jan, 2007 1 commit
  7. 09 Jan, 2007 1 commit
    • kroki/tomash@moonlight.home's avatar
      BUG#23443: user-defined variables can consume too much memory in the · 5b4d9d87
      kroki/tomash@moonlight.home authored
                 server
      
      The problem was that when memory was exhausted HEAP engine could crash
      (GROUP BY uses HEAP TABLE).  Alternatively, if SET was used, it could
      report an error "You may only use constant expressions with SET" instead
      of "Out of memory (Needed NNNNNN bytes)".
      
      The solution is:
       - pass MY_WME to (some) calls to my_malloc() to get correct message.
       - fix heap_write() so that the first key is skipped during cleanup
         on ENOMEM because it wasn't inserted and doesn't have to be
         deleted.
      
      No test case is provided because we can't test out-of-memory behaviour
      in our current test framework.
      5b4d9d87
  8. 13 Nov, 2006 1 commit
  9. 06 Nov, 2006 1 commit
  10. 06 Oct, 2006 1 commit
    • kroki/tomash@moonlight.intranet's avatar
      BUG#21726: Incorrect result with multiple invocations of LAST_INSERT_ID. · ee0cebf9
      kroki/tomash@moonlight.intranet authored
      Note: bug#21726 does not directly apply to 4.1, as it doesn't have stored
      procedures.  However, 4.1 had some bugs that were fixed in 5.0 by the
      patch for bug#21726, and this patch is a backport of those fixes.
      Namely, in 4.1 it fixes:
      
        - LAST_INSERT_ID(expr) didn't return value of expr (4.1 specific).
      
        - LAST_INSERT_ID() could return the value generated by current
          statement if the call happens after the generation, like in
      
            CREATE TABLE t1 (i INT AUTO_INCREMENT PRIMARY KEY, j INT);
            INSERT INTO t1 VALUES (NULL, 0), (NULL, LAST_INSERT_ID());
      
        - Redundant binary log LAST_INSERT_ID_EVENTs could be generated.
      ee0cebf9
  11. 13 Sep, 2006 1 commit
  12. 12 Sep, 2006 1 commit
  13. 08 Sep, 2006 1 commit
  14. 14 Jun, 2006 1 commit
    • bar@mysql.com's avatar
      Bug#8663 cant use bgint unsigned as input to cast · a481a352
      bar@mysql.com authored
      Problem: cast to unsigned limited result to 
      max signed bigint 9223372036854775808,
      instead of max unsigned bigint 18446744073709551615.
      
      Fix: don't use args[0]->val_int() when casting from
      a floating point number, use val() instead, with range checkings,
      special to unsigned data type.
      
      item_func.cc:
        Special handling of cast from REAL_RESULT
        to unsigned int: we cannot execute args[0]->val_int()
        because it cuts max allowed value to LONGLONG_INT,
        instead of ULONGLONG_INT required.
      count_distinct3.test:
        Getting rid of "Data truncated; out of range ..." warnings.
      cast.test, cast.result:
        Adding test case.
      ps.result:
        Fixing that cast from 6570515219.6535 
        to unsigned didn't round to 6570515220,
        and returned 6570515219 instead.
      a481a352
  15. 07 Jun, 2006 1 commit
  16. 05 May, 2006 1 commit
    • aelkin@mysql.com's avatar
      Bug#19136: Crashing log-bin and uninitialized user variables in a derived table · 8c57924a
      aelkin@mysql.com authored
      The reason of the bug is in that `get_var_with_binlog' performs missed
      assingment of
      the variables as side-effect. Doing that it eventually calls
      `free_underlaid_joins' to pass as an argument `thd->lex->select_lex' of the lex
      which belongs to the user query, not 
      to one which is emulated i.e SET @var1:=NULL.
      
      
      `get_var_with_binlog' is refined to supply a temporary lex to sql_set_variables's stack.
      8c57924a
  17. 24 Apr, 2006 1 commit
  18. 12 Apr, 2006 1 commit
    • evgen@moonbone.local's avatar
      Fixed bug#14169: type of group_concat() result changed to blob if tmp_table was · ac54aa2a
      evgen@moonbone.local authored
      used
      
      In a simple queries a result of the GROUP_CONCAT() function was always of 
      varchar type.
      But if length of GROUP_CONCAT() result is greater than 512 chars and temporary
      table is used during select then the result is converted to blob, due to
      policy to not to store fields longer than 512 chars in tmp table as varchar
      fields.
      
      In order to provide consistent behaviour, result of GROUP_CONCAT() now
      will always be converted to blob if it is longer than 512 chars.
      Item_func_group_concat::field_type() is modified accordingly.
      ac54aa2a
  19. 07 Nov, 2005 1 commit
  20. 06 Nov, 2005 1 commit
  21. 01 Nov, 2005 1 commit
    • monty@mysql.com's avatar
      Review of new pushed code · 19502e8e
      monty@mysql.com authored
      Removed wrong fix for bug #14009 (use of abs() on null value causes problems with filesort)
      Mark that add_time(), time_diff() and str_to_date() can return null values
      19502e8e
  22. 18 Oct, 2005 2 commits
  23. 15 Oct, 2005 1 commit
  24. 07 Oct, 2005 1 commit
  25. 06 Sep, 2005 1 commit
  26. 26 Jul, 2005 1 commit
    • bar@mysql.com's avatar
      func_gconcat.result, func_gconcat.test: · 0c2035b7
      bar@mysql.com authored
        Adding test
      item_sum.cc:
        Adding a call for collation/charset aggregation,
            to collect attributes from the arguments. The actual bug fix.
      item_func.h, item_func.cc, item.h, item.cc:
        - Removing collation aggrgation functions from Item_func class
            in item.cc, and adding it as non-class functions in item.cc
            to be able to reuse this code for group_concat.
            - Adding replacement for these functions into Item_func class
            as wrappers for moved functions, to minizize patch size,
      0c2035b7
  27. 25 Jul, 2005 1 commit
  28. 19 Jul, 2005 1 commit
  29. 15 Jul, 2005 1 commit
  30. 14 Jul, 2005 1 commit
  31. 13 Jul, 2005 1 commit
  32. 23 Jun, 2005 1 commit
  33. 05 Jun, 2005 1 commit
  34. 03 Jun, 2005 1 commit
    • monty@mysql.com's avatar
      Move USE_PRAGMA_IMPLEMENTATION to proper place · 29fd1f2f
      monty@mysql.com authored
      Ensure that 'null_value' is not accessed before val() is called in FIELD() functions
      Fixed initialization of key maps. This fixes some problems with keys when you have more than 64 keys
      Fixed that ROLLUP don't always create a temporary table. This fix ensures that func_gconcat.test results are now predictable
      29fd1f2f
  35. 02 Jun, 2005 2 commits
    • bar@mysql.com's avatar
      item_func.cc: · e6860572
      bar@mysql.com authored
      set_var.cc:
      variables.result
      variables.test
      
        Bug #10904 Illegal mix of collations between a system variable and a constant
        Changing coercibility of system variables to SYSCONST,
        to be the same with USER(), DATABASE(), etc.
      e6860572
    • kent@mysql.com's avatar
      tztime.cc: · bd48eed9
      kent@mysql.com authored
        Set #pragma implementation" earlier
      Many files:
        Need to include <my_global.h> before #ifdef USE_PRAGMA_IMPLEMENTATION
      bd48eed9
  36. 01 Jun, 2005 1 commit
  37. 26 May, 2005 1 commit
  38. 14 May, 2005 1 commit