An error occurred fetching the project authors.
  1. 09 Dec, 2008 1 commit
  2. 30 Oct, 2007 1 commit
  3. 21 Oct, 2007 1 commit
    • kaa@polly.(none)'s avatar
      Bug #28550 "Potential bugs related to the return type of the CHAR function". · 34984111
      kaa@polly.(none) authored
        
      Since, as of MySQL 5.0.15, CHAR() arguments larger than 255 are converted into multiple result bytes, a single CHAR() argument can now take up to 4 bytes. This patch fixes Item_func_char::fix_length_and_dec() to take this into account.
        
      This patch also fixes a regression introduced by the patch for bug21513. As now we do not always have the 'name' member of Item set for Item_hex_string and Item_bin_string, an own print() method has been added to Item_hex_string so that it could correctly be printed by Item_func::print_args().
      34984111
  4. 19 Oct, 2007 1 commit
  5. 11 Oct, 2007 1 commit
    • gluh@mysql.com/eagle.(none)'s avatar
      Bug#30981 CHAR(0x41 USING ucs2) doesn't add leading zero · db39976a
      gluh@mysql.com/eagle.(none) authored
      Bug#30982 CHAR(..USING..) can return a not-well-formed string
      Bug#30986 Character set introducer followed by a HEX string can return bad result
      check_well_formed_result moved to Item from Item_str_func
      fixed Item_func_char::val_str for proper ucs symbols converting
      added check for well formed strings for correct conversion of constants with underscore
      charset
      db39976a
  6. 27 Jul, 2007 1 commit
  7. 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
  8. 02 Mar, 2007 1 commit
  9. 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
  10. 23 Dec, 2006 1 commit
  11. 16 Nov, 2006 1 commit
  12. 24 Aug, 2006 1 commit
  13. 11 Aug, 2006 1 commit
  14. 25 Jul, 2006 1 commit
    • gkodinov/kgeorge@macbook.gmz's avatar
      Bug #21086: server crashes when VIEW defined with a SELECT with COLLATE clause is called · f5b0dd6a
      gkodinov/kgeorge@macbook.gmz authored
        When executing INSERT over a view with calculated columns it was assuming all
        elements of the fields collection are actually Item_field instances.
        This may not be true when inserting into a view and that view has columns that are 
        such expressions that allow updating (like setting a collation for example).
        Corrected to access field information through the filed_for_view_update() function and 
        retrieve correctly the field info even for "update-friendly" non-Item_field items.
      f5b0dd6a
  15. 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
  16. 11 Jul, 2006 1 commit
  17. 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
  18. 02 Jul, 2006 1 commit
  19. 13 Jun, 2006 1 commit
  20. 06 Jun, 2006 1 commit
  21. 18 May, 2006 1 commit
  22. 14 Mar, 2006 1 commit
  23. 06 Mar, 2006 1 commit
  24. 07 Dec, 2005 1 commit
  25. 21 Nov, 2005 1 commit
    • bar@mysql.com's avatar
      Bug#10446 Illegal mix of collations: · 2f72e059
      bar@mysql.com authored
      item_strfunc.h, item_strfunc.cc, item.cc:
        Try to convert a const item into destination 
        character set. If conversion happens without
        data loss, then cache the converted value
        and return it during val_str().
        Otherwise, if conversion loses data, return
        Illeral mix of collations error, as it happened
        previously.
      ctype_recoding.result, ctype_recoding.test:
        Fixing tests accordingly.
      2f72e059
  26. 10 Nov, 2005 1 commit
  27. 07 Nov, 2005 1 commit
  28. 21 Oct, 2005 1 commit
    • bar@mysql.com's avatar
      Bug#13233 · a167ddc6
      bar@mysql.com authored
        select distinct char(column) fails with utf8
      ctype_utf8.result, ctype_utf8.test:
        Adding test case
      sql_yacc.yy:
        Adding new syntax.
      item_strfunc.h:
        Fixing wrong max_length calculation.
        Also, adding CHAR(x USING charset),
        for easier migrating from 4.1 to 5.0,
        according to Monty's suggestion.
      a167ddc6
  29. 13 Oct, 2005 1 commit
    • bar@mysql.com's avatar
      ctype_utf8.result, ctype_utf8.test: · 7c81d7fc
      bar@mysql.com authored
        New syntax: CHAR(x USING charset)
        Adding test case.
      sql_yacc.yy:
        New syntax: CHAR(x USING charset)
        Adding new parser rule.
      item_strfunc.h:
        New syntax: CHAR(x USING charset)
        Adding a new constructor.
      7c81d7fc
  30. 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
  31. 15 Jul, 2005 1 commit
  32. 01 Jul, 2005 1 commit
  33. 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
  34. 23 Jun, 2005 1 commit
  35. 17 Jun, 2005 1 commit
  36. 06 Jun, 2005 1 commit
    • bar@mysql.com's avatar
      Bug#8610: The ucs2_turkish_ci collation fails with upper('i') · 2df945d8
      bar@mysql.com authored
        UPPER/LOWER now can return a string with different length.
      
      mi_test1.c:
        Adding new arguments.
      Many files:
        Changeing caseup/casedn to return a result with different
        length than argument.
      sql_string.h:
        Removing unused method,
      mysql_priv.h:
        Removing unused method
      2df945d8
  37. 17 May, 2005 1 commit
  38. 10 May, 2005 2 commits
  39. 04 May, 2005 1 commit