MySQL Bugs: #40197: Restore of databases with events generates warning

Bug #40197	Restore of databases with events generates warning
Submitted:	21 Oct 2008 10:01	Modified:	7 Aug 2009 7:56
Reporter:	Øystein Grøvlen	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Server: Backup	Severity:	S3 (Non-critical)
Version:	6.0-bzr	OS:	Any
Assigned to:	Jørgen Løland	CPU Architecture:	Any

Description:
After I restore a database with events, show warnings give the following warning:

Level	Code	Message
Note	1305	Event X does not exist

How to repeat:
The following test script reproduces the warning:

create database evdb;
use evdb;
create event X on schedule every 1 second do set @a=5;
backup database evdb to '26';
restore from '26';
show warnings;

I suspect this may be result of executing 'drop event ... if exists' during restore since according to the code that will give this warning if event does not exist.  (But I might be wrong.  I have not checked that restore actually perform 'drop event ... if exists'.

Thank you for a bug report. Verified as described on recent 6.0 from bzr:

openxs@suse:/home2/openxs/dbs/6.0> bin/mysql -uroot test
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 1
Server version: 6.0.8-alpha-debug Source distribution

Type 'help;' or '\h' for help. Type '\c' to clear the buffer.

mysql> create database evdb;
Query OK, 1 row affected (0.02 sec)

mysql> use evdb;
Database changed
mysql> create event X on schedule every 1 second do set @a=5;
Query OK, 0 rows affected (0.01 sec)

mysql> backup database evdb to '26';
+-----------+
| backup_id |
+-----------+
| 5774      |
+-----------+
1 row in set (0.27 sec)

mysql> restore from '26';
+-----------+
| backup_id |
+-----------+
| 5775      |
+-----------+
1 row in set (0.03 sec)

mysql> show warnings;
+-------+------+------------------------+
| Level | Code | Message                |
+-------+------+------------------------+
| Note  | 1305 | Event X does not exist |
+-------+------+------------------------+
1 row in set (0.00 sec)

I don't see this behaviour in the latest tree. Everything works fine.

mysql> create database evdb;
Query OK, 1 row affected (0.00 sec)

mysql> use evdb;
Database changed
mysql> create event X on schedule every 1 second do set @a=5;
Query OK, 0 rows affected (0.00 sec)

mysql> backup database evdb to '26';
+-----------+
| backup_id |
+-----------+
| 270       |
+-----------+
1 row in set (0.26 sec)

mysql> restore from '26' overwrite;
+-----------+
| backup_id |
+-----------+
| 272       |
+-----------+
1 row in set (0.02 sec)

mysql> show warnings;
Empty set (0.00 sec)

Still can't repeat this bug. Closing.