After merge fix for BUG#18908 ERROR 1406 (22001): Data too long for column :: using utf8

parent cefa1cf9
...@@ -386,6 +386,18 @@ bool Log_to_csv_event_handler:: ...@@ -386,6 +386,18 @@ bool Log_to_csv_event_handler::
{ {
TABLE *table= general_log.table; TABLE *table= general_log.table;
/*
"INSERT INTO general_log" can generate warning sometimes.
Let's reset warnings from previous queries,
otherwise warning list can grow too much,
so thd->query gets spoiled as some point in time,
and mysql_parse() receives a broken query.
QQ: this problem needs to be studied in more details.
Probably it's better to suppress warnings in logging INSERTs at all.
Comment this line and run "cast.test" to see what's happening:
*/
mysql_reset_errors(table->in_use, 1);
/* below should never happen */ /* below should never happen */
if (unlikely(!logger.is_log_tables_initialized)) if (unlikely(!logger.is_log_tables_initialized))
return FALSE; return FALSE;
......
...@@ -4051,6 +4051,7 @@ static MY_CHARSET_HANDLER my_charset_filename_handler= ...@@ -4051,6 +4051,7 @@ static MY_CHARSET_HANDLER my_charset_filename_handler=
my_strntoull_8bit, my_strntoull_8bit,
my_strntod_8bit, my_strntod_8bit,
my_strtoll10_8bit, my_strtoll10_8bit,
my_strntoull10rnd_8bit,
my_scan_8bit my_scan_8bit
}; };
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment