is_triggers.inc
来自「这个文件是windows mysql源码」· INC 代码 · 共 255 行
INC
255 行
# suite/funcs_1/datadict/is_triggers.inc## Check the layout of information_schema.triggers and the impact of# CREATE/ALTER/DROP TABLE/VIEW/SCHEMA ... on it.## Note:# This test is not intended# - to show information about the all time existing triggers# (there are no in the moment) within the databases information_schema# and mysql# - for checking storage engine properties# Therefore please do not alter $engine_type and $other_engine_type.## Author:# 2008-01-23 mleich WL#4203 Reorganize and fix the data dictionary tests of# testsuite funcs_1# Create this script based on older scripts and new code.# Last Change:# 2008-06-11 mleich Move t/is_triggers.test to this file and# create variants for embedded/non embedded server.#let $engine_type = MEMORY;let $other_engine_type = MyISAM;let $is_table = TRIGGERS;# The table INFORMATION_SCHEMA.TRIGGERS must existeval SHOW TABLES FROM information_schema LIKE '$is_table';--echo #######################################################################--echo # Testcase 3.2.1.1: INFORMATION_SCHEMA tables can be queried via SELECT--echo ######################################################################## Ensure that every INFORMATION_SCHEMA table can be queried with a SELECT# statement, just as if it were an ordinary user-defined table.#--source suite/funcs_1/datadict/is_table_query.inc--echo #########################################################################--echo # Testcase 3.2.12.1: INFORMATION_SCHEMA.TRIGGERS layout--echo ########################################################################## Ensure that the INFORMATION_SCHEMA.TRIGGERS table has the following columns,# in the following order:## TRIGGER_CATALOG NULL# TRIGGER_SCHEMA name of the database in which the trigger occurs# TRIGGER_NAME# EVENT_MANIPULATION event associated with the trigger# ('INSERT', 'DELETE', or 'UPDATE')# EVENT_OBJECT_CATALOG NULL# EVENT_OBJECT_SCHEMA database in which the table associated with the# trigger occurs# EVENT_OBJECT_TABLE name of the table associated with the trigger# ACTION_ORDER 0# ACTION_CONDITION NULL# ACTION_STATEMENT# ACTION_ORIENTATION ROW# ACTION_TIMING 'BEFORE' or 'AFTER'# ACTION_REFERENCE_OLD_TABLE NULL# ACTION_REFERENCE_NEW_TABLE NULL# ACTION_REFERENCE_OLD_ROW OLD# ACTION_REFERENCE_NEW_ROW NEW# CREATED NULL (0)# SQL_MODE server SQL mode that was in effect at the time# when the trigger was created# (also used during trigger execution)# DEFINER who defined the trigger#--source suite/funcs_1/datadict/datadict_bug_12777.inceval DESCRIBE information_schema.$is_table;--source suite/funcs_1/datadict/datadict_bug_12777.inceval SHOW CREATE TABLE information_schema.$is_table;--source suite/funcs_1/datadict/datadict_bug_12777.inceval SHOW COLUMNS FROM information_schema.$is_table;# Note: Retrieval of information within information_schema.columns about# information_schema.tables is in is_columns_is.test.# Show that several columns are always NULL.SELECT * FROM information_schema.triggersWHERE trigger_catalog IS NOT NULL OR event_object_catalog IS NOT NULL OR action_condition IS NOT NULL OR action_reference_old_table IS NOT NULL OR action_reference_new_table IS NOT NULL;--echo ##################################################################################--echo # Testcase 3.2.18.2 + 3.2.18.3: INFORMATION_SCHEMA.TRIGGERS accessible information--echo ################################################################################### 3.2.18.2: Ensure that the table shows the relevant information on every# trigger on which the current user or PUBLIC has privileges.# 3.2.18.3: Ensure that the table does not show any information on any trigger# on which the current user and public have no privileges.# The SUPER privilege is required for# - creation of triggers# - retrieval in INFORMATION_SCHEMA.TRIGGERS (affects size of result set)#--disable_warningsDROP DATABASE IF EXISTS db_datadict;--enable_warningsCREATE DATABASE db_datadict;--error 0,ER_CANNOT_USERDROP USER 'testuser1'@'localhost';CREATE USER 'testuser1'@'localhost';--error 0,ER_CANNOT_USERDROP USER 'testuser2'@'localhost';CREATE USER 'testuser2'@'localhost';--error 0,ER_CANNOT_USERDROP USER 'testuser3'@'localhost';CREATE USER 'testuser3'@'localhost';--error 0,ER_CANNOT_USERDROP USER 'testuser4'@'localhost';CREATE USER 'testuser4'@'localhost';GRANT SUPER ON *.* TO 'testuser1'@'localhost';GRANT SUPER ON *.* TO 'testuser3'@'localhost';GRANT SUPER ON *.* TO 'testuser4'@'localhost';GRANT ALL ON db_datadict.* TO 'testuser1'@'localhost' WITH GRANT OPTION;let $my_select = SELECT * FROM information_schema.triggersWHERE trigger_name = 'trg1';let $my_show = SHOW TRIGGERS FROM db_datadict;--echo # Establish connection testuser1 (user=testuser1)--replace_result $MASTER_MYPORT MYSQL_PORT $MASTER_MYSOCK MYSQL_SOCKconnect (testuser1, localhost, testuser1, , db_datadict);--replace_result $engine_type <engine_type>evalCREATE TABLE db_datadict.t1 (f1 INT, f2 INT, f3 INT)ENGINE = $engine_type;CREATE TRIGGER trg1 BEFORE INSERTON db_datadict.t1 FOR EACH ROW SET @test_before = 2, new.f1 = @test_before;GRANT ALL ON db_datadict.t1 TO 'testuser2'@'localhost';GRANT SELECT ON db_datadict.t1 TO 'testuser3'@'localhost';eval $my_select;eval $my_show;--echo # Establish connection testuser2 (user=testuser2)--replace_result $MASTER_MYPORT MYSQL_PORT $MASTER_MYSOCK MYSQL_SOCKconnect (testuser2, localhost, testuser2, , db_datadict);SHOW GRANTS FOR 'testuser2'@'localhost';--echo # No SUPER Privilege --> no result for queryeval $my_select;eval $my_show;--echo # Establish connection testuser3 (user=testuser3)--replace_result $MASTER_MYPORT MYSQL_PORT $MASTER_MYSOCK MYSQL_SOCKconnect (testuser3, localhost, testuser3, , test);SHOW GRANTS FOR 'testuser3'@'localhost';--echo # SUPER Privilege + SELECT Privilege on t1 --> result for queryeval $my_select;eval $my_show;--echo # Establish connection testuser4 (user=testuser4)--replace_result $MASTER_MYPORT MYSQL_PORT $MASTER_MYSOCK MYSQL_SOCKconnect (testuser4, localhost, testuser4, , test);SHOW GRANTS FOR 'testuser4'@'localhost';--echo # SUPER Privilege + no SELECT Privilege on t1 --> no result for queryeval $my_select;eval $my_show;--echo # Switch to connection default and close connections testuser1 - testuser4connection default;disconnect testuser1;disconnect testuser2;disconnect testuser3;disconnect testuser4;eval $my_select;eval $my_show;DROP USER 'testuser1'@'localhost';DROP USER 'testuser2'@'localhost';DROP USER 'testuser3'@'localhost';DROP USER 'testuser4'@'localhost';DROP DATABASE db_datadict;--echo #########################################################################--echo # 3.2.1.13+3.2.1.14+3.2.1.15: INFORMATION_SCHEMA.TRIGGERS modifications--echo ########################################################################## 3.2.1.13: Ensure that the creation of any new database object (e.g. table or# column) automatically inserts all relevant information on that# object into every appropriate INFORMATION_SCHEMA table.# 3.2.1.14: Ensure that the alteration of any existing database object# automatically updates all relevant information on that object in# every appropriate INFORMATION_SCHEMA table.# 3.2.1.15: Ensure that the dropping of any existing database object# automatically deletes all relevant information on that object from# every appropriate INFORMATION_SCHEMA table.# FIXME: To be implemented--echo ########################################################################--echo # Testcases 3.2.1.3-3.2.1.5 + 3.2.1.8-3.2.1.12: INSERT/UPDATE/DELETE and--echo # DDL on INFORMATION_SCHEMA tables are not supported--echo ######################################################################### 3.2.1.3: Ensure that no user may execute an INSERT statement on any# INFORMATION_SCHEMA table.# 3.2.1.4: Ensure that no user may execute an UPDATE statement on any# INFORMATION_SCHEMA table.# 3.2.1.5: Ensure that no user may execute a DELETE statement on any# INFORMATION_SCHEMA table.# 3.2.1.8: Ensure that no user may create an index on an# INFORMATION_SCHEMA table.# 3.2.1.9: Ensure that no user may alter the definition of an# INFORMATION_SCHEMA table.# 3.2.1.10: Ensure that no user may drop an INFORMATION_SCHEMA table.# 3.2.1.11: Ensure that no user may move an INFORMATION_SCHEMA table to any# other database.# 3.2.1.12: Ensure that no user may directly add to, alter, or delete any data# in an INFORMATION_SCHEMA table.#--disable_warningsDROP DATABASE IF EXISTS db_datadict;--enable_warningsCREATE DATABASE db_datadict;--replace_result $engine_type <engine_type>evalCREATE TABLE db_datadict.t1 (f1 BIGINT)ENGINE = $engine_type;CREATE TRIGGER db_datadict.trg1 BEFORE INSERTON db_datadict.t1 FOR EACH ROW SET @test_before = 2, new.f1 = @test_before;--error ER_DBACCESS_DENIED_ERRORINSERT INTO information_schema.triggersSELECT * FROM information_schema.triggers;--error ER_DBACCESS_DENIED_ERRORUPDATE information_schema.triggers SET trigger_schema = 'test'WHERE table_name = 't1';--error ER_DBACCESS_DENIED_ERRORDELETE FROM information_schema.triggers WHERE trigger_name = 't1';--error ER_DBACCESS_DENIED_ERRORTRUNCATE information_schema.triggers;--error ER_DBACCESS_DENIED_ERRORCREATE INDEX my_idx_on_triggers ON information_schema.triggers(trigger_schema);--error ER_DBACCESS_DENIED_ERRORALTER TABLE information_schema.triggers DROP PRIMARY KEY;--error ER_DBACCESS_DENIED_ERRORALTER TABLE information_schema.triggers ADD f1 INT;--error ER_DBACCESS_DENIED_ERRORDROP TABLE information_schema.triggers;--error ER_DBACCESS_DENIED_ERRORALTER TABLE information_schema.triggers RENAME db_datadict.triggers;--error ER_DBACCESS_DENIED_ERRORALTER TABLE information_schema.triggers RENAME information_schema.xtriggers;# CleanupDROP DATABASE db_datadict;
⌨️ 快捷键说明
复制代码Ctrl + C
搜索代码Ctrl + F
全屏模式F11
增大字号Ctrl + =
减小字号Ctrl + -
显示快捷键?