summaryrefslogtreecommitdiff
path: root/sql/log.cc
diff options
context:
space:
mode:
authorunknown <bar@mysql.com/bar.intranet.mysql.r18.ru>2006-11-03 10:18:13 +0400
committerunknown <bar@mysql.com/bar.intranet.mysql.r18.ru>2006-11-03 10:18:13 +0400
commitb5d53f2031acabef3cf7baa6cac95079caef06af (patch)
treebea19585c4162918ff57ce0f64c025a45a0011ce /sql/log.cc
parentbfdc9c120792c412e7cbb03b071616aaf899599a (diff)
downloadmariadb-git-b5d53f2031acabef3cf7baa6cac95079caef06af.tar.gz
After merge fix for BUG#18908 ERROR 1406 (22001): Data too long for column :: using utf8
strings/ctype-utf8.c: Fix for compilation warning - forgot to add a new structure member in one of the previous changes.
Diffstat (limited to 'sql/log.cc')
-rw-r--r--sql/log.cc12
1 files changed, 12 insertions, 0 deletions
diff --git a/sql/log.cc b/sql/log.cc
index a1ed9bd6df3..9ca71fa74d0 100644
--- a/sql/log.cc
+++ b/sql/log.cc
@@ -386,6 +386,18 @@ bool Log_to_csv_event_handler::
{
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 */
if (unlikely(!logger.is_log_tables_initialized))
return FALSE;