1. 25 Mar, 2010 3 commits
  2. 24 Mar, 2010 4 commits
  3. 23 Mar, 2010 4 commits
  4. 22 Mar, 2010 5 commits
  5. 19 Mar, 2010 2 commits
  6. 18 Mar, 2010 1 commit
  7. 16 Mar, 2010 1 commit
    • Joerg Bruehe's avatar
      Fix a syntax error: · f4013d13
      Joerg Bruehe authored
      A variable declaration was preceded by "DBUG_PRINT()".
      
      sql-common/client.c:
        Thou shalt not declare a variable after an executable statement
        (and "DBUG_PRINT()" is executable).
      f4013d13
  8. 15 Mar, 2010 3 commits
  9. 13 Mar, 2010 1 commit
  10. 12 Mar, 2010 6 commits
  11. 11 Mar, 2010 7 commits
  12. 10 Mar, 2010 3 commits
    • Luis Soares's avatar
      Fix for BUG#51716 and BUG#51787: test case improvements. · 092d5038
      Luis Soares authored
      Split rpl_row_charset into:
      
        - rpl_row_utf16.
        - rpl_row_utf32.
      
      This way these tests can run independently if server supports
      either one of the charsets but not both.
      
      Cleaned up rpl_row_utf32 which had a spurious instruction:
      -- let $reset_slave_type_conversions= 0
      092d5038
    • Davi Arnaut's avatar
      Automatic merge. · f147aa35
      Davi Arnaut authored
      f147aa35
    • Luis Soares's avatar
      Fix for BUG#51716 and BUG#51787. · ade4977c
      Luis Soares authored
      In BUG#51787 we were using the wrong charset to print out the
      data. We were using the field charset for the string that would
      hold the information. This caused the assertion, because the
      string length was not aligned with UTF32 bytes requirements for
      storage.
      
      We fix this by using &my_charset_latin1 in the string object
      instead of the field->charset(). As a side-effect, we needed to
      extend the show_sql_type interface so that it took the field
      charset is now passed as a parameter, so that one is able to
      calculate the correct field size.
      
      In BUG#51716 we had issues with Field_string::pack and
      Field_string::unpack. When packing, the length was incorrectly
      calculated. When unpacking, the padding the string would be
      padded with the wrong bytes (a few bytes less than it should).
      
      We fix this by resorting to charset abstractions (functions) that
      calculate the correct length when packing and pad correctly the
      string when unpacking.
      ade4977c