SHOW Statements SQL Original Statement: CREATE DEFINER=‘me‘@‘localhost‘ TRIGGER ‘ins_sum‘ BEFORE INSERT ON ‘account‘ FOR EACH ROW SET @sum = @sum + NEW.amount character_set_client: utf8mb4 collation_connection: utf8mb4_0900_ai_ci Database Collation: utf8mb4_0900_ai_ci Created: 2018-08-08 10:10:12.61 SHOW CREATE TRIGGER  output has these columns: • Trigger : The trigger name. • sql_mode : The SQL mode in effect when the trigger executes. • SQL Original Statement : The  CREATE TRIGGER  statement that defines the trigger. • character_set_client : The session value of the  character_set_client  system variable when the trigger was created. • collation_connection : The session value of the  collation_connection  system variable when the trigger was created. • Database Collation : The collation of the database with which the trigger is associated. • Created : The date and time when the trigger was created. This is a  TIMESTAMP(2)  value (with a fractional part in hundredths of seconds) for triggers. Trigger information is also available from the  INFORMATION_SCHEMA TRIGGERS  table. See Section 26.3.45, “The INFORMATION_SCHEMA TRIGGERS Table” . This statement shows the  CREATE USER  statement that creates the named user. An error occurs if the user does not exist. The statement requires the  SELECT  privilege for the  mysql  system schema, except to see information for the current user. For the current user, the  SELECT  privilege for the  mysql.user system table is required for display of the password hash in the  IDENTIFIED AS  clause; otherwise, the hash displays as  <secret> . To name the account, use the format described in Section 6.2.4, “Specifying Account Names” . The host name part of the account name, if omitted, defaults to  ’%’ . It is also possible to specify  CURRENT_USER  or CURRENT_USER()  to refer to the account associated with the current session. Password hash values displayed in the  IDENTIFIED WITH  clause of output from  SHOW CREATE USER  may contain unprintable characters that have adverse effects on terminal displays and in other environments. Enabling the  print_identified_with_as_hex  system variable (available as of MySQL 8.0.17) causes  SHOW CREATE USER  to display such hash values as hexadecimal strings rather than as regular string literals. Hash values that do not contain unprintable characters still display as regular string literals, even with this variable enabled. mysql>  CREATE USER ’u1’@’localhost’ IDENTIFIED BY ’secret’; mysql>  SET print_identified_with_as_hex = ON; mysql>  SHOW CREATE USER ’u1’@’localhost’\G *************************** 1. row *************************** CREATE USER for u1@localhost: CREATE USER ’u1’@’localhost’ IDENTIFIED WITH ’caching_sha2_password’ AS REQUIRE NONE PASSWORD EXPIRE DEFAULT ACCOUNT UNLOCK 2921 SHOW CREATE USER  user 13.7.7.12 SHOW CREATE USER Statement