The INFORMATION_SCHEMA EVENTS Table The date and time when the event last executed. This is a  DATETIME  value. If the event has never executed, this column is  NULL . LAST_EXECUTED  indicates when the event started. As a result, the  ENDS  column is never less than LAST_EXECUTED . The text of the comment, if the event has one. If not, this value is empty. The server ID of the MySQL server on which the event was created; used in replication. This value may be updated by  ALTER EVENT  to the server ID of the server on which that statement occurs, if executed on a replication source. The default value is 0. The session value of the  character_set_client  system variable when the event was created. The session value of the  collation_connection  system variable when the event was created. The collation of the database with which the event is associated. Suppose that the user  ’jon’@’ghidora’  creates an event named  e_daily , and then modifies it a few minutes later using an  ALTER EVENT  statement, as shown here: •For more information about  SLAVESIDE_DISABLED  and the  ORIGINATOR  column, see Section 17.5.1.16, “Replication of Invoked Features” . •Times in the  EVENTS  table are displayed using the event time zone, the current session time zone, or UTC, as described in Section 25.4.4, “Event Metadata” . • EVENTS  is a nonstandard  INFORMATION_SCHEMA  table. • DATABASE_COLLATION • COLLATION_CONNECTION • CHARACTER_SET_CLIENT • ORIGINATOR • EVENT_COMMENT • LAST_EXECUTED Notes Example DELIMITER | CREATE EVENT e_daily ON SCHEDULE EVERY 1 DAY COMMENT ’Saves total number of sessions then clears the table each day’ DO BEGIN INSERT INTO site_activity.totals (time, total) SELECT CURRENT_TIMESTAMP, COUNT(*) FROM site_activity.sessions; DELETE FROM site_activity.sessions; END | DELIMITER ; 4790