Bug #16853 Events: mysqldump doesn't show events
Submitted: 27 Jan 2006 20:59 Modified: 15 Mar 2006 15:37
Reporter: Peter Gulutzan
Status: Closed
Category:Server Severity:S3 (Non-critical)
Version:5.1.6-alpha-debug OS:Linux (SUSE 10.0)
Assigned to: Bugs System Target Version:

[27 Jan 2006 20:59] Peter Gulutzan
Description:
The mysqldump utility program doesn't print out events.
I regard this as a bug because "mysqldump db1" should
dump everything in the database, and events are in
databases.
I am not asking for options like --events or --skip-events.

How to repeat:
(Assuming use of database db1)

mysql> create event ee on schedule every 1 year do set @a=5;
Query OK, 1 row affected (0.02 sec)

...

/usr/local/mysql/bin/mysqldump db1 --user=root

Examine output, searching for the word "event".
[1 Mar 2006 20:15] Sergei Golubchik
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/3211
[15 Mar 2006 15:37] Paul DuBois
Noted in 5.1.8 changelog.

Added the <option>--events</option> option to
<command>mysqldump</command> to enable events to be included
in the dump output. (Bug #16853)