Documentation Home
MySQL 9.3 Reference Manual
Related Documentation Download this Manual
PDF (US Ltr) - 40.8Mb
PDF (A4) - 40.9Mb
Man Pages (TGZ) - 261.1Kb
Man Pages (Zip) - 368.3Kb
Info (Gzip) - 4.1Mb
Info (Zip) - 4.1Mb


15.7.7.20 SHOW EVENTS Statement

SHOW EVENTS    [{FROM | IN}schema_name]    [LIKE 'pattern' | WHEREexpr]

This statement displays information about Event Manager events, which are discussed inSection 27.5, “Using the Event Scheduler”. It requires theEVENT privilege for the database from which the events are to be shown.

In its simplest form,SHOW EVENTS lists all of the events in the current schema:

mysql> SELECT CURRENT_USER(), SCHEMA();+----------------+----------+| CURRENT_USER() | SCHEMA() |+----------------+----------+| jon@ghidora    | myschema |+----------------+----------+1 row in set (0.00 sec)mysql> SHOW EVENTS\G*************************** 1. row ***************************                  Db: myschema                Name: e_daily             Definer: jon@ghidora           Time zone: SYSTEM                Type: RECURRING          Execute at: NULL      Interval value: 1      Interval field: DAY              Starts: 2018-08-08 11:06:34                Ends: NULL              Status: ENABLED          Originator: 1character_set_client: utf8mb4collation_connection: utf8mb4_0900_ai_ci  Database Collation: utf8mb4_0900_ai_ci

To see events for a specific schema, use theFROM clause. For example, to see events for thetest schema, use the following statement:

SHOW EVENTS FROM test;

TheLIKE clause, if present, indicates which event names to match. TheWHERE clause can be given to select rows using more general conditions, as discussed inSection 28.8, “Extensions to SHOW Statements”.

SHOW EVENTS output has these columns:

  • Db

    The name of the schema (database) to which the event belongs.

  • Name

    The name of the event.

  • Definer

    The account of the user who created the event, in'user_name'@'host_name' format.

  • Time zone

    The event time zone, which is the time zone used for scheduling the event and that is in effect within the event as it executes. The default value isSYSTEM.

  • Type

    The event repetition type, eitherONE TIME (transient) orRECURRING (repeating).

  • Execute At

    For a one-time event, this is theDATETIME value specified in theAT clause of theCREATE EVENT statement used to create the event, or of the lastALTER EVENT statement that modified the event. The value shown in this column reflects the addition or subtraction of anyINTERVAL value included in the event'sAT clause. For example, if an event is created usingON SCHEDULE AT CURRENT_TIMESTAMP + '1:6' DAY_HOUR, and the event was created at 2018-02-09 14:05:30, the value shown in this column would be'2018-02-10 20:05:30'. If the event's timing is determined by anEVERY clause instead of anAT clause (that is, if the event is recurring), the value of this column isNULL.

  • Interval Value

    For a recurring event, the number of intervals to wait between event executions. For a transient event, the value of this column is alwaysNULL.

  • Interval Field

    The time units used for the interval which a recurring event waits before repeating. For a transient event, the value of this column is alwaysNULL.

  • Starts

    The start date and time for a recurring event. This is displayed as aDATETIME value, and isNULL if no start date and time are defined for the event. For a transient event, this column is alwaysNULL. For a recurring event whose definition includes aSTARTS clause, this column contains the correspondingDATETIME value. As with theExecute At column, this value resolves any expressions used. If there is noSTARTS clause affecting the timing of the event, this column isNULL

  • Ends

    For a recurring event whose definition includes aENDS clause, this column contains the correspondingDATETIME value. As with theExecute At column, this value resolves any expressions used. If there is noENDS clause affecting the timing of the event, this column isNULL.

  • Status

    The event status. One ofENABLED,DISABLED, orREPLICA_SIDE_DISABLED.REPLICA_SIDE_DISABLED indicates that the creation of the event occurred on another MySQL server acting as a replication source and replicated to the current MySQL server which is acting as a replica, but the event is not presently being executed on the replica. For more information, seeSection 19.5.1.16, “Replication of Invoked Features”. information.

    REPLICA_SIDE_DISABLED replacesSLAVESIDE_DISABLED, which is now deprecated and subject to removal in a future version of MySQL.

  • Originator

    The server ID of the MySQL server on which the event was created; used in replication. This value may be updated byALTER EVENT to the server ID of the server on which that statement occurs, if executed on a source server. The default value is 0.

  • character_set_client

    The session value of thecharacter_set_client system variable when the event was created.

  • collation_connection

    The session value of thecollation_connection system variable when the event was created.

  • Database Collation

    The collation of the database with which the event is associated.

For more information aboutREPLICA_SIDE_DISABLED and theOriginator column, seeSection 19.5.1.16, “Replication of Invoked Features”.

Times displayed bySHOW EVENTS are given in the event time zone, as discussed inSection 27.5.4, “Event Metadata”.

Event information is also available from theINFORMATION_SCHEMAEVENTS table. SeeSection 28.3.14, “The INFORMATION_SCHEMA EVENTS Table”.

The event action statement is not shown in the output ofSHOW EVENTS. UseSHOW CREATE EVENT or theINFORMATION_SCHEMAEVENTS table.