An error occurred fetching the project authors.
  1. 11 Apr, 2007 1 commit
    • gkodinov/kgeorge@magare.gmz's avatar
      Bug #27530: · 4202454b
      gkodinov/kgeorge@magare.gmz authored
      The function CRC32() returns unsigned integer.
      But the metadata (the unsigned flag) for the 
      function was set incorrectly.
      As a result type arithmetics based on the 
      function's metadata (like finding the concise
      type of an temporary table column to hold the result)
      returned incorrect results.
      Fixed by returning correct type information.
      
      This fix is based on code contributed by Martin Friebe
      (martin@hybyte.com) on 2007-03-30.  
      4202454b
  2. 28 Mar, 2007 1 commit
  3. 10 Mar, 2007 1 commit
    • evgen@moonbone.local's avatar
      Bug#15757: Wrong SUBSTRING() result when a tmp table was employed. · 6f6b9ae3
      evgen@moonbone.local authored
      When the SUBSTRING() function was used over a LONGTEXT field the max_length of
      the SUBSTRING() result was wrongly calculated and set to 0. As the max_length
      parameter is used while tmp field creation it limits the length of the result
      field and leads to printing an empty string instead of the correct result.
      
      Now the Item_func_substr::fix_length_and_dec() function correctly calculates
      the max_length parameter.
      6f6b9ae3
  4. 09 Mar, 2007 1 commit
  5. 02 Mar, 2007 1 commit
  6. 23 Feb, 2007 1 commit
  7. 11 Jan, 2007 1 commit
    • evgen@moonbone.local's avatar
      Bug#23409: Arguments of the ENCODE() and the DECODE() functions were not printed · fc0e206c
      evgen@moonbone.local authored
      correctly.
      
      The Item_func::print method was used to print the Item_func_encode and the
      Item_func_decode objects. The last argument to ENCODE and DECODE functions
      is a plain C string and thus Item_func::print wasn't able to print it.
      
      The print() method is added to the Item_func_encode class. It correctly
      prints the Item_func_encode and the Item_func_decode objects.
      fc0e206c
  8. 19 Dec, 2006 1 commit
  9. 20 Nov, 2006 1 commit
    • monty@mysql.com/nosik.monty.fi's avatar
      Remove compiler warnings · e8258798
      monty@mysql.com/nosik.monty.fi authored
      (Mostly in DBUG_PRINT() and unused arguments)
      Fixed bug in query cache when used with traceing (--with-debug)
      Fixed memory leak in mysqldump
      Removed warnings from mysqltest scripts (replaced -- with #)
      e8258798
  10. 16 Nov, 2006 1 commit
  11. 08 Nov, 2006 1 commit
    • cmiller@zippy.cornsilk.net's avatar
      Bug#10963: LEFT/RIGHT/SUBSTR/.. string functions returns wrong result \ · 6260e12b
      cmiller@zippy.cornsilk.net authored
        on large length
        
      Problem:  Most (all) of the numeric inputs were being coerced into
      int (32 bit) sized variables.  Works OK for sane inputs; any input
      larger than 2^32 (or 2^31 for signed vars) exihibited predictable
      wrapping behavior (up to about 10^18) and then started having really
      strange behaviour past that point (since the conversion to 64 bit int
      from the DECIMAL type can do weird things on out of range numbers).
      
      Solution: 1)  Add many tests.  2)  Convert input from (u)long type to
      (u)longlong.  3)  Do (sometimes multiple) sanity checks on input,
      keeping in mind that sometimes a negative longlong is not a negative
      longlong (if the unsigned_flag is set).  4) Emulate existing behavior
      w/rt negative and "small" out-of-bounds values.
      6260e12b
  12. 09 Sep, 2006 1 commit
  13. 07 Sep, 2006 1 commit
  14. 19 Jul, 2006 1 commit
    • igor@olga.mysql.com's avatar
      Fixed bug #17526: incorrect print method · f201828d
      igor@olga.mysql.com authored
      for class Item_func_trim. 
      For 4.1 it caused wrong output for EXPLAIN EXTENDED commands
      if expressions with the TRIM function of two arguments were used.
      For 5.0 it caused an error message when trying to select
      from a view with the TRIM function of two arguments.
      This unexpected error message was due to the fact that the
      print method for the class Item_func_trim was inherited from
      the class Item_func. Yet the TRIM function does not take a list
      of its arguments. Rather it takes the arguments in the form:
        [{BOTH | LEADING | TRAILING} [remstr] FROM] str) |
        [remstr FROM] str
      f201828d
  15. 07 Jul, 2006 1 commit
  16. 06 Jul, 2006 1 commit
    • igor@olga.mysql.com's avatar
      Fixed bug #18243. · 0e3d2daf
      igor@olga.mysql.com authored
      The implementation of the method Item_func_reverse::val_str
      for the REVERSE function modified the argument of the function.
      This led to wrong results for expressions that contained
      REVERSE(ref) if ref occurred somewhere else in the expressions.
      0e3d2daf
  17. 13 Jun, 2006 1 commit
  18. 28 May, 2006 1 commit
    • evgen@moonbone.local's avatar
      Fixed bug#15351: Wrong collation used for comparison of md5() and sha() · 766b4a8c
      evgen@moonbone.local authored
      argument can lead to a wrong result.
      
      md5() and sha() functions treat their arguments as case sensitive strings.
      But when they are compared their arguments were compared as a case
      insensitive strings which leads to two functions with different arguments
      and thus different results to being identical. This can lead to a wrong
      decision made in the range optimizer and thus lead to a wrong result set.
      
      Item_func_md5::fix_length_and_dec() and Item_func_sha::fix_length_and_dec()
      functions now set binary collation on their arguments.
      766b4a8c
  19. 18 May, 2006 1 commit
  20. 08 May, 2006 1 commit
  21. 14 Mar, 2006 1 commit
  22. 24 Nov, 2005 1 commit
  23. 11 Oct, 2005 1 commit
    • monty@mysql.com's avatar
      Reviewing new pushed code · f5fdf3e8
      monty@mysql.com authored
      - CHAR() now returns binary string as default
      - CHAR(X*65536+Y*256+Z) is now equal to CHAR(X,Y,Z) independent of the character set for CHAR()
      - Test for both ETIMEDOUT and ETIME from pthread_cond_timedwait()
        (Some old systems returns ETIME and it's safer to test for both values
         than to try to write a wrapper for each old system)
      - Fixed new introduced bug in NOT BETWEEN X and X
      - Ensure we call commit_by_xid or rollback_by_xid for all engines, even if one engine has failed
      - Use octet2hex() for all conversion of string to hex
      - Simplify and optimize code
      f5fdf3e8
  24. 06 Oct, 2005 1 commit
    • monty@mysql.com's avatar
      Review of code pushed since last 5.0 pull: · 78e828d3
      monty@mysql.com authored
      Ensure that ccache is also used for C programs
      mysql: Ensure that 'delimiter' works the same way in batch mode as in normal mode
      mysqldump: Change to use ;; (instead of //) as a stored procedure/trigger delimiter
      Fixed test cases by adding missing DROP's and rename views to be of type 'v#'
      Removed MY_UNIX_PATH from fn_format()
      Removed current_db_used from TABLE_LIST
      Removed usage of 'current_thd' in Item_splocal
      Removed some compiler warnings
      A bit faster longlong2str code
      78e828d3
  25. 22 Sep, 2005 1 commit
  26. 08 Aug, 2005 1 commit
    • patg@krsna.patg.net's avatar
      item_strfunc.cc: · 6128521b
      patg@krsna.patg.net authored
        BUG #11104 
            Took out the offset-=delimiter_length-1 out of the for loop. It was causing
            basically this: 
            select substring_index('the king of the the hill', 'the', -2) to not work.
            The first iteration, offset would be initialised to 24, then strstr would 
            point at 'the king of the the* hill' ('*'means right before the 
            character following), returning a offset of 16. The for loop would then 
            decrement offset by two (3 - 1), to 14, now pointing at 
            "the king of th*e the hill", _skipping_ past the 'e' in the second to last
            'the', and therefore strstr would never have a chance of matching the 
            second to last 'the', then moving on to the 'the' at the begginning of the 
            string!
            In a nutshell, offset was being decremented by too great a value, preventing
            the second to last 'the' from being ever found, hence the result of 
            'king of the the hill' from the query that is reported in the bug report
      func_str.test:
        BUG #11104
        Added tests to make sure fix addresses issues in original bug report
      func_str.result:
        BUG #11104 
        New results for new tests
      6128521b
  27. 01 Aug, 2005 1 commit
  28. 28 Jul, 2005 1 commit
  29. 22 Jul, 2005 1 commit
  30. 13 Jul, 2005 1 commit
  31. 29 Jun, 2005 1 commit
    • igor@rurik.mysql.com's avatar
      func_str.test: · 4b8f2e9b
      igor@rurik.mysql.com authored
        Added test cases for bug #11469.
      item_strfunc.h:
        Fixed bug #11469: wrong implementation of the not_null_tables
        method for CONCAT_WS.
      4b8f2e9b
  32. 28 Jun, 2005 1 commit
  33. 23 Jun, 2005 1 commit
    • igor@rurik.mysql.com's avatar
      func_str.result, func_str.test: · c73c2af6
      igor@rurik.mysql.com authored
        Added a test case for bug #10124.
      sql_select.h, item_subselect.cc, sql_select.cc:
        Fixed bug #10124.
        The copy method of the store_key classes can return
        STORE_KEY_OK=0, STORE_KEY_FATAL=1, STORE_KEY_CONV=2 now.
      field.cc:
        Fixed bug #10124.
        When ussuing a warning the store methods return 2 instead of 1 now.
      c73c2af6
  34. 20 Jun, 2005 1 commit
  35. 01 Jun, 2005 1 commit
  36. 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
  37. 24 Mar, 2005 1 commit
  38. 16 Mar, 2005 1 commit
  39. 09 Mar, 2005 1 commit
  40. 23 Feb, 2005 1 commit