summaryrefslogtreecommitdiff
path: root/client
diff options
context:
space:
mode:
authorAnirudh Mangipudi <anirudh.mangipudi@oracle.com>2012-11-09 15:16:49 +0530
committerAnirudh Mangipudi <anirudh.mangipudi@oracle.com>2012-11-09 15:16:49 +0530
commitd97caadc222c8b04c979f4e35b5b8ad2b12bf33e (patch)
treeea9e86512d5fe00381466299e8b8ca522aa0be95 /client
parent8afcdfe9c0edb8495b486425f3df05417d8944fa (diff)
parent27134cbd28f106e1549b02f931006f6f7efda88f (diff)
downloadmariadb-git-d97caadc222c8b04c979f4e35b5b8ad2b12bf33e.tar.gz
BUG#11762933: MYSQLDUMP WILL SILENTLY SKIP THE `EVENT`
TABLE DATA IF DUMPS MYSQL DATABA Problem: If mysqldump is run without --events (or with --skip-events) it will not dump the mysql.event table's data. This behaviour is inconsistent with that of --routines option, which does not affect the dumping of mysql.proc table. According to the Manual, --events (--skip-events) defines, if the Event Scheduler events for the dumped databases should be included in the mysqldump output and this has nothing to do with the mysql.event table itself. Solution: A warning has been added when mysqldump is used without --events (or with --skip-events) and a separate patch with the behavioral change will be prepared for 5.6/trunk.
Diffstat (limited to 'client')
-rw-r--r--client/mysqldump.c3
1 files changed, 2 insertions, 1 deletions
diff --git a/client/mysqldump.c b/client/mysqldump.c
index 4fcf309b22b..765e547004e 100644
--- a/client/mysqldump.c
+++ b/client/mysqldump.c
@@ -3406,7 +3406,8 @@ static void dump_table(char *table, char *db)
if (!opt_events && !my_strcasecmp(&my_charset_latin1, db, "mysql") &&
!my_strcasecmp(&my_charset_latin1, table, "event"))
{
- verbose_msg("-- Skipping data table mysql.event, --skip-events was used\n");
+ fprintf(stderr, "-- Warning: Skipping the data of table mysql.event."
+ " Specify the --events option explicitly.\n");
DBUG_VOID_RETURN;
}