im a bit confused about the event scheduler. First off, it is running and working, but the timezone handling confuses me a bit, as it seems it's not what is documented on events metadata
So to start off, they say, mysql.event table holds event data as well. This table does not exist on our system.
It also says in info schema, starts and last_executed are displayed as event timezone, but that doesnt seem to be the case on our system as well.
starts = reported as 'system' time zone, currntly utc -0400, hence i had to make the start time -4 hours to have it run in utc at start of next month (2019-07-31 20:00:00).
I know i can set the session timezone to utc.
While that works, as soon as you edit the event, the old gets deleted and a new create event is triggered by phpmyadmin ( possibly bug? ).
I also know i can run the commands in sql tab with alter event, but i am not the oly one accessing the system, and anyone could basicly use the event interface to edit the event = back to system timezone
timezone reported after adding is system (utc -4) on an test run, last executed was in utc ( no problem really, but its not what docs say )
Now docs say mysql.event displays the start used to add the event in utc ( again our system not has this table ) and stores the timezone used to prevent wrong timings when changing timezones
What happens when we possibly change the system timezone at a later point? since info schema reports as system and not -0400 what would happen to our event which right now has a starts time of 31.07.2019 20:00:00?
Say we change to utc, would the starts column update to reflect this change? Would the timezone reflect the change?
I'm afraid our event would then possibly run at 8pm in utc instead of -0400, since timezone in info schema might still be 'system' then.
Anyone has some insight on this? Don't really want to mess with the global timezone to test this out, since system is in production.
Appreciate any help/insights on this, Seb