From e99bc0d1e21a2048b8fda1719e778ee8ffd1adcc Mon Sep 17 00:00:00 2001 From: Alexander Barkov Date: Fri, 14 Aug 2015 09:23:03 +0400 Subject: Removing unused String_copier::copy_fix. Fixing misleading comments in String_copiers::well_formed_copy(). --- sql/sql_string.cc | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-) (limited to 'sql/sql_string.cc') diff --git a/sql/sql_string.cc b/sql/sql_string.cc index 1b8ea936c0d..379609ad6e7 100644 --- a/sql/sql_string.cc +++ b/sql/sql_string.cc @@ -879,13 +879,7 @@ my_copy_with_hex_escaping(CHARSET_INFO *cs, with optional character set conversion, with optional left padding (for binary -> UCS2 conversion) - In case if there is a Unicode conversion (i.e. to_cs and from_cs are - different character sets and both are not &my_charset_bin), bad input bytes - as well as characters that cannot be encoded in to_cs are replaced to '?'. - - In case of non-Unicode copying (i.e. to_cs and from_cs are same character set, - or from_cs is &my_charset_bin), the function stops on the first bad - byte sequence. + Bad input bytes are replaced to '?'. The string that is written to "to" is always well-formed. -- cgit v1.2.1