Bug #16398 Events: After direct change, event is not loaded
Submitted: 12 Jan 2006 3:37 Modified: 19 Feb 2006 1:09
Reporter: Peter Gulutzan Email Updates:
Status: Unsupported Impact on me:
None 
Category:MySQL Server: Stored Routines Severity:S3 (Non-critical)
Version:5.1.6-alpha-debug OS:Linux (linux)
Assigned to: Andrey Hristov CPU Architecture:Any

[12 Jan 2006 3:37] Peter Gulutzan 
Description:
There is no RELOAD EVENT statement. So if I create
a new event by inserting it into mysql.event, it
is not seen.

How to repeat:
mysql> create table t (s1 int)//
Query OK, 0 rows affected (0.02 sec)

mysql> set global event_scheduler = 1//
Query OK, 0 rows affected (0.00 sec)

mysql> insert into mysql.event values ('db1','e_57','insert into t values (0)','root@localhost',null,1,'SECOND',current_timestamp,current_timestamp,null,null,null,'ENABLED','DROP','')//
Query OK, 1 row affected (0.00 sec)

mysql> select * from t//
Empty set (0.00 sec)
[20 Feb 2006 9:08] Sergei Golubchik 
We'll probably have FLUSH EVENTS some day, but a workaround currently is 
 set event_scheduler=0;
 set event_scheduler=1;