mariadb/mysql-test/r/events_restart_phase1.result

create database if not exists mysqltest_events_test;
use mysqltest_events_test;
set global event_scheduler=off;
create table execution_log(name char(10));
create event abc1 on schedule every 1 second do insert into execution_log value('abc1');
create event abc2 on schedule every 1 second do insert into execution_log value('abc2');
create event abc3 on schedule every 1 second do insert into execution_log value('abc3');
select name from execution_log;
name
insert into mysql.event values ('db1','bad','select 42','root@localhost',NULL,1000,'MICROSECOND','2006-05-05 17:39:11','2006-05-05 17:39:20','2016-05-05 15:39:24','2016-05-05 15:39:11',NULL,'ENABLED','DROP','','comment1',1,'SYSTEM');
insert into mysql.event values ('db1','bad2','sect','root@localhost',NULL,1000,'SECOND','2006-05-05 17:39:11','2006-05-05 17:39:20','2016-05-05 15:39:24','2016-05-05 15:39:11',NULL,'ENABLED','DROP','','comment2',1,'SYSTEM');
"Now we restart the server"
WL #3337 (Events new architecture) Final stroke, events should be loaded from disk on server startup. Also check the validity of their bodies if possible during loading. 2006-07-13 10:59:58 +02:00			`create database if not exists mysqltest_events_test;`
			`use mysqltest_events_test;`
WL#3337 (Event scheduler new architecture) This is a post-review patch. Fixes the typelib implementation, available only in 5.1.11. --event-scheduler cmdline : DISABLED \| ON \| OFF \| 0 \| 1 DISABLED - makes the scheduler unavailable during the server run (ON\|1)- When the server is started the scheduler will be started. It can be stopped and restarted by setting appropriate values to GLOBAL event_scheduler (OFF\|0)- When the server is started, the scheduler won't be started. It can be started and again stopped by setting appropriate values to GLOBAL event_scheduler. _DEFAULT_ value The GLOBAL variable event_scheduler can have the following values: OFF \| ON \| 0 \| 1 DISABLED is not possible and every attempt will end with an error that it's not a valid value for the variable. OFF \| 0 - This is the pre-5.1.11 behavior - The scheduler stops, if not already stopped, and can be started again by setting the value of the variable to ON\|1. ON \| 1 - This is the pre-5.1.11 behavior - The scheduler starts, if not already started, and can be stopped again by setting the value of the variable to OFF\|0. 2006-09-01 13:08:44 +02:00			`set global event_scheduler=off;`
WL #3337 (Events new architecture) Final stroke, events should be loaded from disk on server startup. Also check the validity of their bodies if possible during loading. 2006-07-13 10:59:58 +02:00			`create table execution_log(name char(10));`
			`create event abc1 on schedule every 1 second do insert into execution_log value('abc1');`
			`create event abc2 on schedule every 1 second do insert into execution_log value('abc2');`
			`create event abc3 on schedule every 1 second do insert into execution_log value('abc3');`
WL#3337 (Event scheduler new architecture) This is a post-review patch. Fixes the typelib implementation, available only in 5.1.11. --event-scheduler cmdline : DISABLED \| ON \| OFF \| 0 \| 1 DISABLED - makes the scheduler unavailable during the server run (ON\|1)- When the server is started the scheduler will be started. It can be stopped and restarted by setting appropriate values to GLOBAL event_scheduler (OFF\|0)- When the server is started, the scheduler won't be started. It can be started and again stopped by setting appropriate values to GLOBAL event_scheduler. _DEFAULT_ value The GLOBAL variable event_scheduler can have the following values: OFF \| ON \| 0 \| 1 DISABLED is not possible and every attempt will end with an error that it's not a valid value for the variable. OFF \| 0 - This is the pre-5.1.11 behavior - The scheduler stops, if not already stopped, and can be started again by setting the value of the variable to ON\|1. ON \| 1 - This is the pre-5.1.11 behavior - The scheduler starts, if not already started, and can be stopped again by setting the value of the variable to OFF\|0. 2006-09-01 13:08:44 +02:00			`select name from execution_log;`
			`name`
Merge cbell@bk-internal.mysql.com:/home/bk/mysql-5.1-new-rpl into mysql_cab_desk.:C:/source/c++/mysql-5.1-new-rpl 2007-03-29 15:54:59 +02:00			`insert into mysql.event values ('db1','bad','select 42','root@localhost',NULL,1000,'MICROSECOND','2006-05-05 17:39:11','2006-05-05 17:39:20','2016-05-05 15:39:24','2016-05-05 15:39:11',NULL,'ENABLED','DROP','','comment1',1,'SYSTEM');`
			`insert into mysql.event values ('db1','bad2','sect','root@localhost',NULL,1000,'SECOND','2006-05-05 17:39:11','2006-05-05 17:39:20','2016-05-05 15:39:24','2016-05-05 15:39:11',NULL,'ENABLED','DROP','','comment2',1,'SYSTEM');`
WL #3337 (Events new architecture) Final stroke, events should be loaded from disk on server startup. Also check the validity of their bodies if possible during loading. 2006-07-13 10:59:58 +02:00			`"Now we restart the server"`