diff options
author | Anirudh Mangipudi <anirudh.mangipudi@oracle.com> | 2012-11-09 15:15:16 +0530 |
---|---|---|
committer | Anirudh Mangipudi <anirudh.mangipudi@oracle.com> | 2012-11-09 15:15:16 +0530 |
commit | 27134cbd28f106e1549b02f931006f6f7efda88f (patch) | |
tree | 800fd81108f928ae5a47bff9684b5f8f86da810f /client | |
parent | b61f494c4bf1f88fdb0149dc9b20001c7fddf094 (diff) | |
download | mariadb-git-27134cbd28f106e1549b02f931006f6f7efda88f.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.c | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/client/mysqldump.c b/client/mysqldump.c index 3fda1fafc24..316c0fd174c 100644 --- a/client/mysqldump.c +++ b/client/mysqldump.c @@ -3393,7 +3393,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; } |