mirror of
https://github.com/MariaDB/server.git
synced 2025-01-20 22:12:30 +01:00
98db230086
when there are no up-to-date system tables to support it: - initialize the scheduler before reporting "Ready for connections". This ensures that warnings, if any, are printed before "Ready for connections", and this message is not mangled. - do not abort the scheduler if there are no system tables - check the tables once at start up, remember the status and disable the scheduler if the tables are not up to date. If one attempts to use the scheduler with bad tables, issue an error message. - clean up the behaviour of the module under LOCK TABLES and pre-locking mode - make sure implicit commit of Events DDL works as expected. - add more tests Collateral clean ups in the events code. This patch fixes Bug#23631 Events: SHOW VARIABLES doesn't work when mysql.event is damaged
42 lines
2.3 KiB
Text
42 lines
2.3 KiB
Text
use events_test;
|
|
select @@event_scheduler;
|
|
@@event_scheduler
|
|
DISABLED
|
|
show events;
|
|
ERROR HY000: Cannot proceed because system tables used by Event Scheduler were found damaged at server start
|
|
select event_name from information_schema.events;
|
|
ERROR HY000: Cannot proceed because system tables used by Event Scheduler were found damaged at server start
|
|
show create event intact_check;
|
|
ERROR HY000: Cannot proceed because system tables used by Event Scheduler were found damaged at server start
|
|
drop event no_such_event;
|
|
ERROR HY000: Cannot proceed because system tables used by Event Scheduler were found damaged at server start
|
|
create event intact_check_1 on schedule every 5 hour do select 5;
|
|
ERROR HY000: Cannot proceed because system tables used by Event Scheduler were found damaged at server start
|
|
alter event intact_check_1 on schedule every 8 hour do select 8;
|
|
ERROR HY000: Cannot proceed because system tables used by Event Scheduler were found damaged at server start
|
|
alter event intact_check_1 rename to intact_check_2;
|
|
ERROR HY000: Cannot proceed because system tables used by Event Scheduler were found damaged at server start
|
|
drop event intact_check_1;
|
|
ERROR HY000: Cannot proceed because system tables used by Event Scheduler were found damaged at server start
|
|
drop event intact_check_2;
|
|
ERROR HY000: Cannot proceed because system tables used by Event Scheduler were found damaged at server start
|
|
drop event intact_check;
|
|
ERROR HY000: Cannot proceed because system tables used by Event Scheduler were found damaged at server start
|
|
set global event_scheduler=on;
|
|
ERROR HY000: Cannot proceed because system tables used by Event Scheduler were found damaged at server start
|
|
set global event_scheduler=off;
|
|
ERROR HY000: Cannot proceed because system tables used by Event Scheduler were found damaged at server start
|
|
show variables like 'event_scheduler';
|
|
Variable_name Value
|
|
event_scheduler DISABLED
|
|
Make sure that we still can create and drop databases,
|
|
and no warnings are produced.
|
|
drop database if exists mysqltest_database_not_exists;
|
|
Warnings:
|
|
Note 1008 Can't drop database 'mysqltest_database_not_exists'; database doesn't exist
|
|
create database mysqltest_db1;
|
|
drop database mysqltest_db1;
|
|
Restore the original mysql.event table
|
|
drop table mysql.event;
|
|
rename table event_like to mysql.event;
|
|
Now let's restart the server again
|