U:RDoc::AnyMethod[iI"clean_message:ETI" Mysql2::Error#clean_message;TF:privateo:RDoc::Markup::Document:@parts[o:RDoc::Markup::Paragraph;	[I"NIn MySQL 5.5+ error messages are always constructed server-side as UTF-8 ;TI"Mthen returned in the encoding set by the `character_set_results` system ;TI"variable.;To:RDoc::Markup::BlankLineo;
;	[I"HSee http://dev.mysql.com/doc/refman/5.5/en/charset-errors.html for ;TI"more context.;T@o;
;	[	I"NBefore MySQL 5.5 error message template strings are in whatever encoding ;TI"4is associated with the error message language. ;TI"LSee http://dev.mysql.com/doc/refman/5.1/en/error-message-language.html ;TI"for more information.;T@o;
;	[	I"OThe issue is that the user-data inserted in the message could potentially ;TI"Obe in any encoding MySQL supports and is insert into the latin1, euckr or ;TI"Mkoi8r string raw. Meaning there's a high probability the string will be ;TI"corrupt encoding-wise.;T@o;
;	[I"HSee http://dev.mysql.com/doc/refman/5.1/en/charset-errors.html for ;TI"more information.;T@o;
;	[I"QSo in an attempt to make sure the error message string is always in a valid ;TI"Pencoding, we'll assume UTF-8 and clean the string of anything that's not a ;TI"valid UTF-8 character.;T@o;
;	[I""Returns a valid UTF-8 string.;T:
@fileI"lib/mysql2/error.rb;T:0@omit_headings_from_table_of_contents_below000[I"(message);T@-FI"
Error;TcRDoc::NormalClass00