2006-12-22 00:38:34 +01:00
|
|
|
# This test uses chmod, can't be run with root permissions
|
|
|
|
-- source include/not_as_root.inc
|
2019-08-30 15:06:54 +02:00
|
|
|
--source include/default_charset.inc
|
2006-12-22 00:38:34 +01:00
|
|
|
|
2004-09-07 14:29:46 +02:00
|
|
|
#
|
|
|
|
# Basic triggers test
|
|
|
|
#
|
|
|
|
|
|
|
|
--disable_warnings
|
2006-02-24 21:50:36 +01:00
|
|
|
drop table if exists t1, t2, t3, t4;
|
2004-09-07 14:29:46 +02:00
|
|
|
drop view if exists v1;
|
2005-03-27 14:15:21 +02:00
|
|
|
drop database if exists mysqltest;
|
2005-07-09 19:51:59 +02:00
|
|
|
drop function if exists f1;
|
2006-03-29 12:53:00 +02:00
|
|
|
drop function if exists f2;
|
2005-08-10 08:31:32 +02:00
|
|
|
drop procedure if exists p1;
|
2004-09-07 14:29:46 +02:00
|
|
|
--enable_warnings
|
|
|
|
|
2005-09-15 01:56:09 +02:00
|
|
|
# Create additional connections used through test
|
|
|
|
connect (addconroot1, localhost, root,,);
|
|
|
|
connect (addconroot2, localhost, root,,);
|
2005-12-11 13:26:15 +01:00
|
|
|
# Connection without current database set
|
|
|
|
connect (addconwithoutdb, localhost, root,,*NO-ONE*);
|
2005-09-15 01:56:09 +02:00
|
|
|
connection default;
|
|
|
|
|
2004-09-07 14:29:46 +02:00
|
|
|
create table t1 (i int);
|
|
|
|
|
|
|
|
# let us test some very simple trigger
|
|
|
|
create trigger trg before insert on t1 for each row set @a:=1;
|
|
|
|
set @a:=0;
|
|
|
|
select @a;
|
|
|
|
insert into t1 values (1);
|
|
|
|
select @a;
|
2005-07-19 18:06:49 +02:00
|
|
|
drop trigger trg;
|
2004-09-07 14:29:46 +02:00
|
|
|
|
|
|
|
# let us test simple trigger reading some values
|
|
|
|
create trigger trg before insert on t1 for each row set @a:=new.i;
|
|
|
|
insert into t1 values (123);
|
|
|
|
select @a;
|
2005-07-19 18:06:49 +02:00
|
|
|
drop trigger trg;
|
2004-09-07 14:29:46 +02:00
|
|
|
|
|
|
|
drop table t1;
|
|
|
|
|
|
|
|
# Let us test before insert trigger
|
|
|
|
# Such triggers can be used for setting complex default values
|
|
|
|
create table t1 (i int not null, j int);
|
|
|
|
delimiter |;
|
|
|
|
create trigger trg before insert on t1 for each row
|
|
|
|
begin
|
|
|
|
if isnull(new.j) then
|
|
|
|
set new.j:= new.i * 10;
|
|
|
|
end if;
|
|
|
|
end|
|
|
|
|
insert into t1 (i) values (1)|
|
|
|
|
insert into t1 (i,j) values (2, 3)|
|
|
|
|
select * from t1|
|
2005-07-19 18:06:49 +02:00
|
|
|
drop trigger trg|
|
2004-09-07 14:29:46 +02:00
|
|
|
drop table t1|
|
|
|
|
delimiter ;|
|
|
|
|
|
|
|
|
# After insert trigger
|
|
|
|
# Useful for aggregating data
|
|
|
|
create table t1 (i int not null primary key);
|
|
|
|
create trigger trg after insert on t1 for each row
|
|
|
|
set @a:= if(@a,concat(@a, ":", new.i), new.i);
|
|
|
|
set @a:="";
|
|
|
|
insert into t1 values (2),(3),(4),(5);
|
|
|
|
select @a;
|
2005-07-19 18:06:49 +02:00
|
|
|
drop trigger trg;
|
2004-09-07 14:29:46 +02:00
|
|
|
drop table t1;
|
|
|
|
|
2005-01-04 12:46:53 +01:00
|
|
|
# PS doesn't work with multi-row statements
|
2005-01-03 12:56:23 +01:00
|
|
|
--disable_ps_protocol
|
2004-09-07 14:29:46 +02:00
|
|
|
# Before update trigger
|
|
|
|
# (In future we will achieve this via proper error handling in triggers)
|
|
|
|
create table t1 (aid int not null primary key, balance int not null default 0);
|
|
|
|
insert into t1 values (1, 1000), (2,3000);
|
|
|
|
delimiter |;
|
|
|
|
create trigger trg before update on t1 for each row
|
|
|
|
begin
|
|
|
|
declare loc_err varchar(255);
|
|
|
|
if abs(new.balance - old.balance) > 1000 then
|
|
|
|
set new.balance:= old.balance;
|
|
|
|
set loc_err := concat("Too big change for aid = ", new.aid);
|
|
|
|
set @update_failed:= if(@update_failed, concat(@a, ":", loc_err), loc_err);
|
|
|
|
end if;
|
|
|
|
end|
|
|
|
|
set @update_failed:=""|
|
|
|
|
update t1 set balance=1500|
|
|
|
|
select @update_failed;
|
|
|
|
select * from t1|
|
2005-07-19 18:06:49 +02:00
|
|
|
drop trigger trg|
|
2004-09-07 14:29:46 +02:00
|
|
|
drop table t1|
|
|
|
|
delimiter ;|
|
2005-01-03 12:56:23 +01:00
|
|
|
--enable_ps_protocol
|
2004-09-07 14:29:46 +02:00
|
|
|
|
|
|
|
# After update trigger
|
|
|
|
create table t1 (i int);
|
|
|
|
insert into t1 values (1),(2),(3),(4);
|
|
|
|
create trigger trg after update on t1 for each row
|
|
|
|
set @total_change:=@total_change + new.i - old.i;
|
|
|
|
set @total_change:=0;
|
|
|
|
update t1 set i=3;
|
|
|
|
select @total_change;
|
2005-07-19 18:06:49 +02:00
|
|
|
drop trigger trg;
|
2004-09-07 14:29:46 +02:00
|
|
|
drop table t1;
|
|
|
|
|
|
|
|
# Before delete trigger
|
|
|
|
# This can be used for aggregation too :)
|
|
|
|
create table t1 (i int);
|
|
|
|
insert into t1 values (1),(2),(3),(4);
|
|
|
|
create trigger trg before delete on t1 for each row
|
|
|
|
set @del_sum:= @del_sum + old.i;
|
|
|
|
set @del_sum:= 0;
|
|
|
|
delete from t1 where i <= 3;
|
|
|
|
select @del_sum;
|
2005-07-19 18:06:49 +02:00
|
|
|
drop trigger trg;
|
2004-09-07 14:29:46 +02:00
|
|
|
drop table t1;
|
|
|
|
|
|
|
|
# After delete trigger.
|
|
|
|
# Just run out of imagination.
|
|
|
|
create table t1 (i int);
|
|
|
|
insert into t1 values (1),(2),(3),(4);
|
|
|
|
create trigger trg after delete on t1 for each row set @del:= 1;
|
|
|
|
set @del:= 0;
|
|
|
|
delete from t1 where i <> 0;
|
|
|
|
select @del;
|
2005-07-19 18:06:49 +02:00
|
|
|
drop trigger trg;
|
2004-09-07 14:29:46 +02:00
|
|
|
drop table t1;
|
|
|
|
|
|
|
|
# Several triggers on one table
|
|
|
|
create table t1 (i int, j int);
|
|
|
|
|
|
|
|
delimiter |;
|
|
|
|
create trigger trg1 before insert on t1 for each row
|
|
|
|
begin
|
|
|
|
if new.j > 10 then
|
|
|
|
set new.j := 10;
|
|
|
|
end if;
|
|
|
|
end|
|
|
|
|
create trigger trg2 before update on t1 for each row
|
|
|
|
begin
|
|
|
|
if old.i % 2 = 0 then
|
|
|
|
set new.j := -1;
|
|
|
|
end if;
|
|
|
|
end|
|
|
|
|
create trigger trg3 after update on t1 for each row
|
|
|
|
begin
|
|
|
|
if new.j = -1 then
|
|
|
|
set @fired:= "Yes";
|
|
|
|
end if;
|
|
|
|
end|
|
|
|
|
delimiter ;|
|
|
|
|
set @fired:="";
|
|
|
|
insert into t1 values (1,2),(2,3),(3,14);
|
|
|
|
select @fired;
|
|
|
|
select * from t1;
|
|
|
|
update t1 set j= 20;
|
|
|
|
select @fired;
|
|
|
|
select * from t1;
|
|
|
|
|
2005-07-19 18:06:49 +02:00
|
|
|
drop trigger trg1;
|
|
|
|
drop trigger trg2;
|
|
|
|
drop trigger trg3;
|
2004-09-07 14:29:46 +02:00
|
|
|
drop table t1;
|
|
|
|
|
|
|
|
|
2005-05-24 20:19:33 +02:00
|
|
|
# Let us test how triggers work for special forms of INSERT such as
|
|
|
|
# REPLACE and INSERT ... ON DUPLICATE KEY UPDATE
|
|
|
|
create table t1 (id int not null primary key, data int);
|
|
|
|
create trigger t1_bi before insert on t1 for each row
|
|
|
|
set @log:= concat(@log, "(BEFORE_INSERT: new=(id=", new.id, ", data=", new.data,"))");
|
|
|
|
create trigger t1_ai after insert on t1 for each row
|
|
|
|
set @log:= concat(@log, "(AFTER_INSERT: new=(id=", new.id, ", data=", new.data,"))");
|
|
|
|
create trigger t1_bu before update on t1 for each row
|
|
|
|
set @log:= concat(@log, "(BEFORE_UPDATE: old=(id=", old.id, ", data=", old.data,
|
|
|
|
") new=(id=", new.id, ", data=", new.data,"))");
|
|
|
|
create trigger t1_au after update on t1 for each row
|
|
|
|
set @log:= concat(@log, "(AFTER_UPDATE: old=(id=", old.id, ", data=", old.data,
|
|
|
|
") new=(id=", new.id, ", data=", new.data,"))");
|
|
|
|
create trigger t1_bd before delete on t1 for each row
|
|
|
|
set @log:= concat(@log, "(BEFORE_DELETE: old=(id=", old.id, ", data=", old.data,"))");
|
|
|
|
create trigger t1_ad after delete on t1 for each row
|
|
|
|
set @log:= concat(@log, "(AFTER_DELETE: old=(id=", old.id, ", data=", old.data,"))");
|
|
|
|
# Simple INSERT - both triggers should be called
|
|
|
|
set @log:= "";
|
|
|
|
insert into t1 values (1, 1);
|
|
|
|
select @log;
|
|
|
|
# INSERT IGNORE for already existing key - only before trigger should fire
|
|
|
|
set @log:= "";
|
|
|
|
insert ignore t1 values (1, 2);
|
|
|
|
select @log;
|
2006-06-16 18:21:25 +02:00
|
|
|
# INSERT ... ON DUPLICATE KEY UPDATE ...
|
2005-05-24 20:19:33 +02:00
|
|
|
set @log:= "";
|
2006-06-16 18:21:25 +02:00
|
|
|
insert into t1 (id, data) values (1, 3), (2, 2) on duplicate key update data= data + 1;
|
2005-05-24 20:19:33 +02:00
|
|
|
select @log;
|
2006-06-16 18:21:25 +02:00
|
|
|
# REPLACE (also test for bug#13479 "REPLACE activates UPDATE trigger,
|
|
|
|
# not the DELETE and INSERT triggers")
|
|
|
|
# We define REPLACE as INSERT which DELETEs old rows which conflict with
|
|
|
|
# row being inserted. So for the first record in statement below we will
|
|
|
|
# call before insert trigger, then delete will be executed (and both delete
|
|
|
|
# triggers should fire). Finally after insert trigger will be called.
|
|
|
|
# For the second record we will just call both on insert triggers.
|
2005-05-24 20:19:33 +02:00
|
|
|
set @log:= "";
|
2006-06-16 18:21:25 +02:00
|
|
|
replace t1 values (1, 4), (3, 3);
|
2005-05-24 20:19:33 +02:00
|
|
|
select @log;
|
2006-06-16 18:21:25 +02:00
|
|
|
# Now we will drop ON DELETE triggers to test REPLACE which is internally
|
|
|
|
# executed via update
|
|
|
|
drop trigger t1_bd;
|
|
|
|
drop trigger t1_ad;
|
2005-05-24 20:19:33 +02:00
|
|
|
set @log:= "";
|
2006-06-16 18:21:25 +02:00
|
|
|
replace t1 values (1, 5);
|
2005-05-24 20:19:33 +02:00
|
|
|
select @log;
|
|
|
|
|
|
|
|
# This also drops associated triggers
|
|
|
|
drop table t1;
|
|
|
|
|
|
|
|
|
2005-07-09 19:51:59 +02:00
|
|
|
#
|
|
|
|
# Let us test triggers which access other tables.
|
|
|
|
#
|
|
|
|
# Trivial trigger which inserts data into another table
|
|
|
|
create table t1 (id int primary key, data varchar(10), fk int);
|
|
|
|
create table t2 (event varchar(100));
|
|
|
|
create table t3 (id int primary key);
|
|
|
|
create trigger t1_ai after insert on t1 for each row
|
|
|
|
insert into t2 values (concat("INSERT INTO t1 id=", new.id, " data='", new.data, "'"));
|
|
|
|
insert into t1 (id, data) values (1, "one"), (2, "two");
|
|
|
|
select * from t1;
|
|
|
|
select * from t2;
|
2005-07-19 18:06:49 +02:00
|
|
|
drop trigger t1_ai;
|
2005-07-09 19:51:59 +02:00
|
|
|
# Trigger which uses couple of tables (and partially emulates FK constraint)
|
|
|
|
delimiter |;
|
|
|
|
create trigger t1_bi before insert on t1 for each row
|
|
|
|
begin
|
|
|
|
if exists (select id from t3 where id=new.fk) then
|
|
|
|
insert into t2 values (concat("INSERT INTO t1 id=", new.id, " data='", new.data, "' fk=", new.fk));
|
|
|
|
else
|
|
|
|
insert into t2 values (concat("INSERT INTO t1 FAILED id=", new.id, " data='", new.data, "' fk=", new.fk));
|
|
|
|
set new.id= NULL;
|
|
|
|
end if;
|
|
|
|
end|
|
|
|
|
delimiter ;|
|
|
|
|
insert into t3 values (1);
|
|
|
|
insert into t1 values (4, "four", 1), (5, "five", 2);
|
|
|
|
select * from t1;
|
|
|
|
select * from t2;
|
|
|
|
drop table t1, t2, t3;
|
|
|
|
# Trigger which invokes function
|
|
|
|
create table t1 (id int primary key, data varchar(10));
|
|
|
|
create table t2 (seq int);
|
|
|
|
insert into t2 values (10);
|
|
|
|
create function f1 () returns int return (select max(seq) from t2);
|
|
|
|
delimiter |;
|
|
|
|
create trigger t1_bi before insert on t1 for each row
|
|
|
|
begin
|
|
|
|
if new.id > f1() then
|
|
|
|
set new.id:= f1();
|
|
|
|
end if;
|
|
|
|
end|
|
|
|
|
delimiter ;|
|
|
|
|
insert into t1 values (1, "first");
|
|
|
|
insert into t1 values (f1(), "max");
|
|
|
|
select * from t1;
|
|
|
|
drop table t1, t2;
|
|
|
|
drop function f1;
|
|
|
|
# Trigger which forces invocation of another trigger
|
|
|
|
# (emulation of FK on delete cascade policy)
|
|
|
|
create table t1 (id int primary key, fk_t2 int);
|
|
|
|
create table t2 (id int primary key, fk_t3 int);
|
|
|
|
create table t3 (id int primary key);
|
|
|
|
insert into t1 values (1,1), (2,1), (3,2);
|
|
|
|
insert into t2 values (1,1), (2,2);
|
|
|
|
insert into t3 values (1), (2);
|
|
|
|
create trigger t3_ad after delete on t3 for each row
|
|
|
|
delete from t2 where fk_t3=old.id;
|
|
|
|
create trigger t2_ad after delete on t2 for each row
|
|
|
|
delete from t1 where fk_t2=old.id;
|
|
|
|
delete from t3 where id = 1;
|
|
|
|
select * from t1 left join (t2 left join t3 on t2.fk_t3 = t3.id) on t1.fk_t2 = t2.id;
|
|
|
|
drop table t1, t2, t3;
|
|
|
|
# Trigger which assigns value selected from table to field of row
|
|
|
|
# being inserted/updated.
|
|
|
|
create table t1 (id int primary key, copy int);
|
|
|
|
create table t2 (id int primary key, data int);
|
|
|
|
insert into t2 values (1,1), (2,2);
|
|
|
|
create trigger t1_bi before insert on t1 for each row
|
|
|
|
set new.copy= (select data from t2 where id = new.id);
|
|
|
|
create trigger t1_bu before update on t1 for each row
|
|
|
|
set new.copy= (select data from t2 where id = new.id);
|
|
|
|
insert into t1 values (1,3), (2,4), (3,3);
|
|
|
|
update t1 set copy= 1 where id = 2;
|
|
|
|
select * from t1;
|
|
|
|
drop table t1, t2;
|
|
|
|
|
2004-09-07 14:29:46 +02:00
|
|
|
#
|
|
|
|
# Test of wrong column specifiers in triggers
|
|
|
|
#
|
|
|
|
create table t1 (i int);
|
2005-07-19 18:06:49 +02:00
|
|
|
create table t3 (i int);
|
2004-09-07 14:29:46 +02:00
|
|
|
|
2006-06-29 11:45:43 +02:00
|
|
|
--error ER_TRG_NO_SUCH_ROW_IN_TRG
|
2004-09-07 14:29:46 +02:00
|
|
|
create trigger trg before insert on t1 for each row set @a:= old.i;
|
2006-06-29 11:45:43 +02:00
|
|
|
--error ER_TRG_NO_SUCH_ROW_IN_TRG
|
2004-09-07 14:29:46 +02:00
|
|
|
create trigger trg before delete on t1 for each row set @a:= new.i;
|
2006-06-29 11:45:43 +02:00
|
|
|
--error ER_TRG_CANT_CHANGE_ROW
|
2004-09-09 21:44:27 +02:00
|
|
|
create trigger trg before update on t1 for each row set old.i:=1;
|
2006-06-29 11:45:43 +02:00
|
|
|
--error ER_TRG_NO_SUCH_ROW_IN_TRG
|
2004-09-07 14:29:46 +02:00
|
|
|
create trigger trg before delete on t1 for each row set new.i:=1;
|
2006-06-29 11:45:43 +02:00
|
|
|
--error ER_TRG_CANT_CHANGE_ROW
|
2004-09-07 14:29:46 +02:00
|
|
|
create trigger trg after update on t1 for each row set new.i:=1;
|
2006-06-29 11:45:43 +02:00
|
|
|
--error ER_BAD_FIELD_ERROR
|
2004-11-24 10:24:02 +01:00
|
|
|
create trigger trg before update on t1 for each row set new.j:=1;
|
2006-06-29 11:45:43 +02:00
|
|
|
--error ER_BAD_FIELD_ERROR
|
2004-11-24 10:24:02 +01:00
|
|
|
create trigger trg before update on t1 for each row set @a:=old.j;
|
2004-09-07 14:29:46 +02:00
|
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
# Let us test various trigger creation errors
|
2005-07-19 18:06:49 +02:00
|
|
|
# Also quickly test table namespace (bug#5892/6182)
|
2004-09-07 14:29:46 +02:00
|
|
|
#
|
2006-06-29 11:45:43 +02:00
|
|
|
--error ER_NO_SUCH_TABLE
|
2004-09-07 14:29:46 +02:00
|
|
|
create trigger trg before insert on t2 for each row set @a:=1;
|
|
|
|
|
|
|
|
create trigger trg before insert on t1 for each row set @a:=1;
|
2006-06-29 11:45:43 +02:00
|
|
|
--error ER_TRG_ALREADY_EXISTS
|
2004-09-07 14:29:46 +02:00
|
|
|
create trigger trg after insert on t1 for each row set @a:=1;
|
|
|
|
create trigger trg2 before insert on t1 for each row set @a:=1;
|
2016-10-02 14:35:08 +02:00
|
|
|
drop trigger trg2;
|
2006-06-29 11:45:43 +02:00
|
|
|
--error ER_TRG_ALREADY_EXISTS
|
2005-07-19 18:06:49 +02:00
|
|
|
create trigger trg before insert on t3 for each row set @a:=1;
|
|
|
|
create trigger trg2 before insert on t3 for each row set @a:=1;
|
|
|
|
drop trigger trg2;
|
|
|
|
drop trigger trg;
|
2004-09-07 14:29:46 +02:00
|
|
|
|
2006-06-29 11:45:43 +02:00
|
|
|
--error ER_TRG_DOES_NOT_EXIST
|
2005-07-19 18:06:49 +02:00
|
|
|
drop trigger trg;
|
2004-09-07 14:29:46 +02:00
|
|
|
|
|
|
|
create view v1 as select * from t1;
|
2006-06-29 11:45:43 +02:00
|
|
|
--error ER_WRONG_OBJECT
|
2004-09-07 14:29:46 +02:00
|
|
|
create trigger trg before insert on v1 for each row set @a:=1;
|
|
|
|
drop view v1;
|
|
|
|
|
|
|
|
drop table t1;
|
2005-07-19 18:06:49 +02:00
|
|
|
drop table t3;
|
2004-09-07 14:29:46 +02:00
|
|
|
|
|
|
|
create temporary table t1 (i int);
|
2006-06-29 11:45:43 +02:00
|
|
|
--error ER_TRG_ON_VIEW_OR_TEMP_TABLE
|
2004-09-07 14:29:46 +02:00
|
|
|
create trigger trg before insert on t1 for each row set @a:=1;
|
|
|
|
drop table t1;
|
2004-10-08 13:16:03 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
# Tests for various trigger-related bugs
|
|
|
|
#
|
|
|
|
|
|
|
|
# Test for bug #5887 "Triggers with string literals cause errors".
|
|
|
|
# New .FRM parser was not handling escaped strings properly.
|
|
|
|
create table t1 (x1col char);
|
|
|
|
create trigger tx1 before insert on t1 for each row set new.x1col = 'x';
|
|
|
|
insert into t1 values ('y');
|
2005-07-19 18:06:49 +02:00
|
|
|
drop trigger tx1;
|
2004-10-08 13:16:03 +02:00
|
|
|
drop table t1;
|
2004-11-12 15:04:07 +01:00
|
|
|
|
|
|
|
#
|
|
|
|
# Test for bug #5890 "Triggers fail for DELETE without WHERE".
|
|
|
|
# If we are going to delete all rows in table but DELETE triggers exist
|
|
|
|
# we should perform row-by-row deletion instead of using optimized
|
|
|
|
# delete_all_rows() method.
|
|
|
|
#
|
|
|
|
create table t1 (i int) engine=myisam;
|
|
|
|
insert into t1 values (1), (2);
|
|
|
|
create trigger trg1 before delete on t1 for each row set @del_before:= @del_before + old.i;
|
|
|
|
create trigger trg2 after delete on t1 for each row set @del_after:= @del_after + old.i;
|
|
|
|
set @del_before:=0, @del_after:= 0;
|
|
|
|
delete from t1;
|
|
|
|
select @del_before, @del_after;
|
2005-07-19 18:06:49 +02:00
|
|
|
drop trigger trg1;
|
|
|
|
drop trigger trg2;
|
2004-11-12 15:04:07 +01:00
|
|
|
drop table t1;
|
2005-03-27 14:15:21 +02:00
|
|
|
|
|
|
|
# Test for bug #5859 "DROP TABLE does not drop triggers". Trigger should not
|
|
|
|
# magically reappear when we recreate dropped table.
|
|
|
|
create table t1 (a int);
|
|
|
|
create trigger trg1 before insert on t1 for each row set new.a= 10;
|
|
|
|
drop table t1;
|
|
|
|
create table t1 (a int);
|
|
|
|
insert into t1 values ();
|
|
|
|
select * from t1;
|
|
|
|
drop table t1;
|
|
|
|
|
|
|
|
# Test for bug #6559 "DROP DATABASE forgets to drop triggers".
|
|
|
|
create database mysqltest;
|
|
|
|
use mysqltest;
|
|
|
|
create table t1 (i int);
|
|
|
|
create trigger trg1 before insert on t1 for each row set @a:= 1;
|
|
|
|
# This should succeed
|
|
|
|
drop database mysqltest;
|
|
|
|
use test;
|
2005-05-24 20:19:33 +02:00
|
|
|
|
2005-07-19 18:06:49 +02:00
|
|
|
# Test for bug #8791
|
|
|
|
# "Triggers: Allowed to create triggers on a subject table in a different DB".
|
|
|
|
create database mysqltest;
|
|
|
|
create table mysqltest.t1 (i int);
|
2005-07-19 19:38:12 +02:00
|
|
|
--error ER_TRG_IN_WRONG_SCHEMA
|
2005-07-19 18:06:49 +02:00
|
|
|
create trigger trg1 before insert on mysqltest.t1 for each row set @a:= 1;
|
|
|
|
use mysqltest;
|
A fix and a test case for Bug#29050 Creation of a legal stored procedure
fails if a database is not selected prior.
The problem manifested itself when a user tried to
create a routine that had non-fully-qualified identifiers in its bodies
and there was no current database selected.
This is a regression introduced by the fix for Bug 19022:
The patch for Bug 19022 changes the code to always produce a warning
if we can't resolve the current database in the parser.
In this case this was not necessary, since even though the produced
parsed tree was incorrect, we never re-use sphead
that was obtained at first parsing of CREATE PROCEDURE.
The sphead that is anyhow used is always obtained through db_load_routine,
and there we change the current database to sphead->m_db before
calling yyparse.
The idea of the fix is to resolve the current database directly using
lex->sphead->m_db member when parsing a stored routine body, when
such is present.
This patch removes the need to reset the current database
when loading a trigger or routine definition into SP cache.
The redundant code will be removed in 5.1.
mysql-test/r/sp.result:
Update test results (Bug#29050)
mysql-test/r/trigger.result:
Update results.
mysql-test/t/sp.test:
Add a test case for Bug#29050
mysql-test/t/trigger.test:
Fix wrong behavior covered with tests.
sql/sql_lex.cc:
Implement st_lex::copy_db_to().
sql/sql_lex.h:
Declare st_lex::copy_db_to().
sql/sql_parse.cc:
Use st_lex::copy_db_to() in add_table_to_list, rather than
THD::copy_db_to(). The former will use the database of the sphead,
if we're parsing a stored routine, not the default database in
THD. The default database is needed to initialize tables->db
when the database part was not explicitly specified in the identifier.
sql/sql_yacc.yy:
Use st_lex::copy_db_to() in the parser, rather than
THD::copy_db_to(). The former will use the database of the sphead,
if we're parsing a stored routine, not the default database in
THD.
2007-07-05 09:34:04 +02:00
|
|
|
--error ER_NO_SUCH_TABLE
|
2005-07-19 18:06:49 +02:00
|
|
|
create trigger test.trg1 before insert on t1 for each row set @a:= 1;
|
|
|
|
drop database mysqltest;
|
|
|
|
use test;
|
|
|
|
|
|
|
|
|
2005-05-24 20:19:33 +02:00
|
|
|
# Test for bug #5860 "Multi-table UPDATE does not activate update triggers"
|
|
|
|
# We will also test how delete triggers wor for multi-table DELETE.
|
|
|
|
create table t1 (i int, j int default 10, k int not null, key (k));
|
|
|
|
create table t2 (i int);
|
|
|
|
insert into t1 (i, k) values (1, 1);
|
|
|
|
insert into t2 values (1);
|
|
|
|
create trigger trg1 before update on t1 for each row set @a:= @a + new.j - old.j;
|
|
|
|
create trigger trg2 after update on t1 for each row set @b:= "Fired";
|
|
|
|
set @a:= 0, @b:= "";
|
|
|
|
# Check that trigger works in case of update on the fly
|
|
|
|
update t1, t2 set j = j + 10 where t1.i = t2.i;
|
|
|
|
select @a, @b;
|
|
|
|
insert into t1 values (2, 13, 2);
|
|
|
|
insert into t2 values (2);
|
|
|
|
set @a:= 0, @b:= "";
|
|
|
|
# And now let us check that triggers work in case of multi-update which
|
|
|
|
# is done through temporary tables...
|
|
|
|
update t1, t2 set j = j + 15 where t1.i = t2.i and t1.k >= 2;
|
|
|
|
select @a, @b;
|
|
|
|
# Let us test delete triggers for multi-delete now.
|
|
|
|
# We create triggers for both tables because we want test how they
|
|
|
|
# work in both on-the-fly and via-temp-tables cases.
|
|
|
|
create trigger trg3 before delete on t1 for each row set @c:= @c + old.j;
|
|
|
|
create trigger trg4 before delete on t2 for each row set @d:= @d + old.i;
|
|
|
|
create trigger trg5 after delete on t1 for each row set @e:= "After delete t1 fired";
|
|
|
|
create trigger trg6 after delete on t2 for each row set @f:= "After delete t2 fired";
|
|
|
|
set @c:= 0, @d:= 0, @e:= "", @f:= "";
|
|
|
|
delete t1, t2 from t1, t2 where t1.i = t2.i;
|
|
|
|
select @c, @d, @e, @f;
|
|
|
|
# This also will drop triggers
|
|
|
|
drop table t1, t2;
|
|
|
|
|
|
|
|
# Test for bug #6812 "Triggers are not activated for INSERT ... SELECT".
|
|
|
|
# (We also check the fact that trigger modifies some field does not affect
|
|
|
|
# value of next record inserted).
|
|
|
|
delimiter |;
|
|
|
|
create table t1 (i int, j int default 10)|
|
|
|
|
create table t2 (i int)|
|
|
|
|
insert into t2 values (1), (2)|
|
|
|
|
create trigger trg1 before insert on t1 for each row
|
|
|
|
begin
|
|
|
|
if new.i = 1 then
|
|
|
|
set new.j := 1;
|
|
|
|
end if;
|
|
|
|
end|
|
|
|
|
create trigger trg2 after insert on t1 for each row set @a:= 1|
|
|
|
|
set @a:= 0|
|
|
|
|
insert into t1 (i) select * from t2|
|
|
|
|
select * from t1|
|
|
|
|
select @a|
|
|
|
|
# This also will drop triggers
|
|
|
|
drop table t1, t2|
|
|
|
|
delimiter ;|
|
|
|
|
|
|
|
|
# Test for bug #8755 "Trigger is not activated by LOAD DATA"
|
|
|
|
create table t1 (i int, j int, k int);
|
|
|
|
create trigger trg1 before insert on t1 for each row set new.k = new.i;
|
|
|
|
create trigger trg2 after insert on t1 for each row set @b:= "Fired";
|
|
|
|
set @b:="";
|
|
|
|
# Test triggers with file with separators
|
2007-12-12 18:19:24 +01:00
|
|
|
load data infile '../../std_data/rpl_loaddata.dat' into table t1 (@a, i);
|
2005-05-24 20:19:33 +02:00
|
|
|
select *, @b from t1;
|
|
|
|
set @b:="";
|
|
|
|
# Test triggers with fixed size row file
|
2007-12-12 18:19:24 +01:00
|
|
|
load data infile '../../std_data/loaddata5.dat' into table t1 fields terminated by '' enclosed by '' (i, j);
|
2005-05-24 20:19:33 +02:00
|
|
|
select *, @b from t1;
|
|
|
|
# This also will drop triggers
|
|
|
|
drop table t1;
|
2005-05-30 16:55:56 +02:00
|
|
|
|
|
|
|
# Test for bug #5894 "Triggers with altered tables cause corrupt databases"
|
|
|
|
# Also tests basic error handling for various kinds of triggers.
|
|
|
|
create table t1 (i int, at int, k int, key(k)) engine=myisam;
|
|
|
|
create table t2 (i int);
|
|
|
|
insert into t1 values (1, 1, 1);
|
|
|
|
# We need at least 3 elements in t2 to test multi-update properly
|
|
|
|
insert into t2 values (1), (2), (3);
|
|
|
|
# Create and then break "after" triggers
|
|
|
|
create trigger ai after insert on t1 for each row set @a:= new.at;
|
|
|
|
create trigger au after update on t1 for each row set @a:= new.at;
|
|
|
|
create trigger ad after delete on t1 for each row set @a:= old.at;
|
|
|
|
alter table t1 drop column at;
|
|
|
|
# We still should be able select data from tables.
|
|
|
|
select * from t1;
|
|
|
|
# The following statements changing t1 should fail, but still cause
|
|
|
|
# their main effect. This is because operation on the table row is
|
|
|
|
# executed before "after" trigger and its effect cannot be rolled back
|
|
|
|
# when whole statement fails, because t1 is MyISAM table.
|
2006-06-29 11:45:43 +02:00
|
|
|
--error ER_BAD_FIELD_ERROR
|
2005-05-30 16:55:56 +02:00
|
|
|
insert into t1 values (2, 1);
|
|
|
|
select * from t1;
|
2006-06-29 11:45:43 +02:00
|
|
|
--error ER_BAD_FIELD_ERROR
|
2005-05-30 16:55:56 +02:00
|
|
|
update t1 set k = 2 where i = 2;
|
|
|
|
select * from t1;
|
2006-06-29 11:45:43 +02:00
|
|
|
--error ER_BAD_FIELD_ERROR
|
2005-05-30 16:55:56 +02:00
|
|
|
delete from t1 where i = 2;
|
|
|
|
select * from t1;
|
|
|
|
# Should fail and insert only 1 row
|
2006-06-29 11:45:43 +02:00
|
|
|
--error ER_BAD_FIELD_ERROR
|
2007-12-12 18:19:24 +01:00
|
|
|
load data infile '../../std_data/loaddata5.dat' into table t1 fields terminated by '' enclosed by '' (i, k);
|
2005-05-30 16:55:56 +02:00
|
|
|
select * from t1;
|
2006-06-29 11:45:43 +02:00
|
|
|
--error ER_BAD_FIELD_ERROR
|
2005-05-30 16:55:56 +02:00
|
|
|
insert into t1 select 3, 3;
|
|
|
|
select * from t1;
|
|
|
|
# Multi-update working on the fly, again it will update only
|
|
|
|
# one row even if more matches
|
2006-06-29 11:45:43 +02:00
|
|
|
--error ER_BAD_FIELD_ERROR
|
2005-05-30 16:55:56 +02:00
|
|
|
update t1, t2 set k = k + 10 where t1.i = t2.i;
|
|
|
|
select * from t1;
|
|
|
|
# The same for multi-update via temp table
|
2006-06-29 11:45:43 +02:00
|
|
|
--error ER_BAD_FIELD_ERROR
|
2005-05-30 16:55:56 +02:00
|
|
|
update t1, t2 set k = k + 10 where t1.i = t2.i and k < 3;
|
|
|
|
select * from t1;
|
|
|
|
# Multi-delete on the fly
|
2006-06-29 11:45:43 +02:00
|
|
|
--error ER_BAD_FIELD_ERROR
|
2005-05-30 16:55:56 +02:00
|
|
|
delete t1, t2 from t1 straight_join t2 where t1.i = t2.i;
|
|
|
|
select * from t1;
|
|
|
|
# And via temporary storage
|
2006-06-29 11:45:43 +02:00
|
|
|
--error ER_BAD_FIELD_ERROR
|
2005-05-30 16:55:56 +02:00
|
|
|
delete t2, t1 from t2 straight_join t1 where t1.i = t2.i;
|
|
|
|
select * from t1;
|
|
|
|
# Prepare table for testing of REPLACE and INSERT ... ON DUPLICATE KEY UPDATE
|
|
|
|
alter table t1 add primary key (i);
|
2006-06-29 11:45:43 +02:00
|
|
|
--error ER_BAD_FIELD_ERROR
|
2005-05-30 16:55:56 +02:00
|
|
|
insert into t1 values (3, 4) on duplicate key update k= k + 10;
|
|
|
|
select * from t1;
|
2006-06-16 18:21:25 +02:00
|
|
|
# The following statement will delete old row and won't
|
|
|
|
# insert new one since after delete trigger will fail.
|
2006-06-29 11:45:43 +02:00
|
|
|
--error ER_BAD_FIELD_ERROR
|
2005-05-30 16:55:56 +02:00
|
|
|
replace into t1 values (3, 3);
|
|
|
|
select * from t1;
|
|
|
|
# Also drops all triggers
|
|
|
|
drop table t1, t2;
|
|
|
|
|
|
|
|
create table t1 (i int, bt int, k int, key(k)) engine=myisam;
|
|
|
|
create table t2 (i int);
|
|
|
|
insert into t1 values (1, 1, 1), (2, 2, 2);
|
|
|
|
insert into t2 values (1), (2), (3);
|
|
|
|
# Create and then break "before" triggers
|
|
|
|
create trigger bi before insert on t1 for each row set @a:= new.bt;
|
|
|
|
create trigger bu before update on t1 for each row set @a:= new.bt;
|
|
|
|
create trigger bd before delete on t1 for each row set @a:= old.bt;
|
|
|
|
alter table t1 drop column bt;
|
|
|
|
# The following statements changing t1 should fail and should not
|
|
|
|
# cause any effect on table, since "before" trigger is executed
|
|
|
|
# before operation on the table row.
|
2006-06-29 11:45:43 +02:00
|
|
|
--error ER_BAD_FIELD_ERROR
|
2005-05-30 16:55:56 +02:00
|
|
|
insert into t1 values (3, 3);
|
|
|
|
select * from t1;
|
2006-06-29 11:45:43 +02:00
|
|
|
--error ER_BAD_FIELD_ERROR
|
2005-05-30 16:55:56 +02:00
|
|
|
update t1 set i = 2;
|
|
|
|
select * from t1;
|
2006-06-29 11:45:43 +02:00
|
|
|
--error ER_BAD_FIELD_ERROR
|
2005-05-30 16:55:56 +02:00
|
|
|
delete from t1;
|
|
|
|
select * from t1;
|
2006-06-29 11:45:43 +02:00
|
|
|
--error ER_BAD_FIELD_ERROR
|
2007-12-12 18:19:24 +01:00
|
|
|
load data infile '../../std_data/loaddata5.dat' into table t1 fields terminated by '' enclosed by '' (i, k);
|
2005-05-30 16:55:56 +02:00
|
|
|
select * from t1;
|
2006-06-29 11:45:43 +02:00
|
|
|
--error ER_BAD_FIELD_ERROR
|
2005-05-30 16:55:56 +02:00
|
|
|
insert into t1 select 3, 3;
|
|
|
|
select * from t1;
|
|
|
|
# Both types of multi-update (on the fly and via temp table)
|
2006-06-29 11:45:43 +02:00
|
|
|
--error ER_BAD_FIELD_ERROR
|
2005-05-30 16:55:56 +02:00
|
|
|
update t1, t2 set k = k + 10 where t1.i = t2.i;
|
|
|
|
select * from t1;
|
2006-06-29 11:45:43 +02:00
|
|
|
--error ER_BAD_FIELD_ERROR
|
2005-05-30 16:55:56 +02:00
|
|
|
update t1, t2 set k = k + 10 where t1.i = t2.i and k < 2;
|
|
|
|
select * from t1;
|
|
|
|
# Both types of multi-delete
|
2006-06-29 11:45:43 +02:00
|
|
|
--error ER_BAD_FIELD_ERROR
|
2005-05-30 16:55:56 +02:00
|
|
|
delete t1, t2 from t1 straight_join t2 where t1.i = t2.i;
|
|
|
|
select * from t1;
|
2006-06-29 11:45:43 +02:00
|
|
|
--error ER_BAD_FIELD_ERROR
|
2005-05-30 16:55:56 +02:00
|
|
|
delete t2, t1 from t2 straight_join t1 where t1.i = t2.i;
|
|
|
|
select * from t1;
|
|
|
|
# Let us test REPLACE/INSERT ... ON DUPLICATE KEY UPDATE.
|
|
|
|
# To test properly code-paths different from those that are used
|
|
|
|
# in ordinary INSERT we need to drop "before insert" trigger.
|
|
|
|
alter table t1 add primary key (i);
|
2005-07-19 18:06:49 +02:00
|
|
|
drop trigger bi;
|
2006-06-29 11:45:43 +02:00
|
|
|
--error ER_BAD_FIELD_ERROR
|
2005-05-30 16:55:56 +02:00
|
|
|
insert into t1 values (2, 4) on duplicate key update k= k + 10;
|
|
|
|
select * from t1;
|
2006-06-29 11:45:43 +02:00
|
|
|
--error ER_BAD_FIELD_ERROR
|
2005-05-30 16:55:56 +02:00
|
|
|
replace into t1 values (2, 4);
|
|
|
|
select * from t1;
|
|
|
|
# Also drops all triggers
|
|
|
|
drop table t1, t2;
|
2005-06-29 08:35:49 +02:00
|
|
|
|
|
|
|
# Test for bug #5893 "Triggers with dropped functions cause crashes"
|
|
|
|
# Appropriate error should be reported instead of crash.
|
2005-07-13 21:51:09 +02:00
|
|
|
# Also test for bug #11889 "Server crashes when dropping trigger
|
|
|
|
# using stored routine".
|
2005-07-13 14:22:36 +02:00
|
|
|
--disable_warnings
|
|
|
|
drop function if exists bug5893;
|
|
|
|
--enable_warnings
|
|
|
|
create table t1 (col1 int, col2 int);
|
|
|
|
insert into t1 values (1, 2);
|
|
|
|
create function bug5893 () returns int return 5;
|
|
|
|
create trigger t1_bu before update on t1 for each row set new.col1= bug5893();
|
|
|
|
drop function bug5893;
|
2006-06-29 11:45:43 +02:00
|
|
|
--error ER_SP_DOES_NOT_EXIST
|
2005-07-13 14:22:36 +02:00
|
|
|
update t1 set col2 = 4;
|
2005-07-13 21:51:09 +02:00
|
|
|
# This should not crash server too.
|
2005-07-19 18:06:49 +02:00
|
|
|
drop trigger t1_bu;
|
2005-07-13 14:22:36 +02:00
|
|
|
drop table t1;
|
2005-07-28 21:39:11 +02:00
|
|
|
|
|
|
|
#
|
|
|
|
# storing and restoring parsing modes for triggers (BUG#5891)
|
|
|
|
#
|
|
|
|
set sql_mode='ansi';
|
|
|
|
create table t1 ("t1 column" int);
|
|
|
|
create trigger t1_bi before insert on t1 for each row set new."t1 column" = 5;
|
2005-07-30 08:24:51 +02:00
|
|
|
set sql_mode="";
|
2005-07-28 21:39:11 +02:00
|
|
|
insert into t1 values (0);
|
|
|
|
# create trigger with different sql_mode
|
|
|
|
create trigger t1_af after insert on t1 for each row set @a=10;
|
|
|
|
insert into t1 values (0);
|
|
|
|
select * from t1;
|
|
|
|
select @a;
|
|
|
|
--replace_column 6 #
|
|
|
|
show triggers;
|
|
|
|
drop table t1;
|
|
|
|
# check that rigger preserve sql_mode during execution
|
|
|
|
set sql_mode="traditional";
|
|
|
|
create table t1 (a date);
|
|
|
|
-- error 1292
|
|
|
|
insert into t1 values ('2004-01-00');
|
|
|
|
set sql_mode="";
|
|
|
|
create trigger t1_bi before insert on t1 for each row set new.a = '2004-01-00';
|
|
|
|
set sql_mode="traditional";
|
|
|
|
insert into t1 values ('2004-01-01');
|
|
|
|
select * from t1;
|
|
|
|
set sql_mode=default;
|
|
|
|
show create table t1;
|
|
|
|
--replace_column 6 #
|
|
|
|
show triggers;
|
|
|
|
drop table t1;
|
2005-08-10 08:31:32 +02:00
|
|
|
|
|
|
|
# Test for bug #12280 "Triggers: crash if flush tables"
|
|
|
|
# FLUSH TABLES and FLUSH PRIVILEGES should be disallowed inside
|
|
|
|
# of functions and triggers.
|
|
|
|
create table t1 (id int);
|
|
|
|
--error ER_STMT_NOT_ALLOWED_IN_SF_OR_TRG
|
2006-08-25 15:51:29 +02:00
|
|
|
create trigger t1_ai after insert on t1 for each row reset query cache;
|
|
|
|
--error ER_STMT_NOT_ALLOWED_IN_SF_OR_TRG
|
|
|
|
create trigger t1_ai after insert on t1 for each row reset master;
|
|
|
|
--error ER_STMT_NOT_ALLOWED_IN_SF_OR_TRG
|
|
|
|
create trigger t1_ai after insert on t1 for each row reset slave;
|
|
|
|
--error ER_STMT_NOT_ALLOWED_IN_SF_OR_TRG
|
|
|
|
create trigger t1_ai after insert on t1 for each row flush hosts;
|
|
|
|
--error ER_STMT_NOT_ALLOWED_IN_SF_OR_TRG
|
|
|
|
create trigger t1_ai after insert on t1 for each row flush tables with read lock;
|
|
|
|
--error ER_STMT_NOT_ALLOWED_IN_SF_OR_TRG
|
|
|
|
create trigger t1_ai after insert on t1 for each row flush logs;
|
|
|
|
--error ER_STMT_NOT_ALLOWED_IN_SF_OR_TRG
|
|
|
|
create trigger t1_ai after insert on t1 for each row flush status;
|
|
|
|
--error ER_STMT_NOT_ALLOWED_IN_SF_OR_TRG
|
|
|
|
create trigger t1_ai after insert on t1 for each row flush slave;
|
|
|
|
--error ER_STMT_NOT_ALLOWED_IN_SF_OR_TRG
|
|
|
|
create trigger t1_ai after insert on t1 for each row flush master;
|
|
|
|
--error ER_STMT_NOT_ALLOWED_IN_SF_OR_TRG
|
|
|
|
create trigger t1_ai after insert on t1 for each row flush des_key_file;
|
|
|
|
--error ER_STMT_NOT_ALLOWED_IN_SF_OR_TRG
|
|
|
|
create trigger t1_ai after insert on t1 for each row flush user_resources;
|
|
|
|
--error ER_STMT_NOT_ALLOWED_IN_SF_OR_TRG
|
2005-08-10 08:31:32 +02:00
|
|
|
create trigger t1_ai after insert on t1 for each row flush tables;
|
|
|
|
--error ER_STMT_NOT_ALLOWED_IN_SF_OR_TRG
|
|
|
|
create trigger t1_ai after insert on t1 for each row flush privileges;
|
2006-08-25 15:51:29 +02:00
|
|
|
--disable_warnings
|
|
|
|
drop procedure if exists p1;
|
|
|
|
--enable_warnings
|
|
|
|
|
2005-08-10 08:31:32 +02:00
|
|
|
create trigger t1_ai after insert on t1 for each row call p1();
|
2006-08-25 15:51:29 +02:00
|
|
|
create procedure p1() flush tables;
|
2005-08-10 08:31:32 +02:00
|
|
|
--error ER_STMT_NOT_ALLOWED_IN_SF_OR_TRG
|
|
|
|
insert into t1 values (0);
|
2006-08-25 15:51:29 +02:00
|
|
|
|
|
|
|
drop procedure p1;
|
|
|
|
create procedure p1() reset query cache;
|
2005-08-10 08:31:32 +02:00
|
|
|
--error ER_STMT_NOT_ALLOWED_IN_SF_OR_TRG
|
|
|
|
insert into t1 values (0);
|
2006-08-25 15:51:29 +02:00
|
|
|
|
|
|
|
drop procedure p1;
|
|
|
|
create procedure p1() reset master;
|
|
|
|
--error ER_STMT_NOT_ALLOWED_IN_SF_OR_TRG
|
|
|
|
insert into t1 values (0);
|
|
|
|
|
|
|
|
drop procedure p1;
|
|
|
|
create procedure p1() reset slave;
|
|
|
|
--error ER_STMT_NOT_ALLOWED_IN_SF_OR_TRG
|
|
|
|
insert into t1 values (0);
|
|
|
|
|
|
|
|
drop procedure p1;
|
|
|
|
create procedure p1() flush hosts;
|
|
|
|
--error ER_STMT_NOT_ALLOWED_IN_SF_OR_TRG
|
|
|
|
insert into t1 values (0);
|
|
|
|
|
2005-08-10 08:31:32 +02:00
|
|
|
drop procedure p1;
|
|
|
|
create procedure p1() flush privileges;
|
|
|
|
--error ER_STMT_NOT_ALLOWED_IN_SF_OR_TRG
|
|
|
|
insert into t1 values (0);
|
2006-08-25 15:51:29 +02:00
|
|
|
|
|
|
|
drop procedure p1;
|
|
|
|
create procedure p1() flush tables with read lock;
|
|
|
|
--error ER_STMT_NOT_ALLOWED_IN_SF_OR_TRG
|
|
|
|
insert into t1 values (0);
|
|
|
|
|
|
|
|
drop procedure p1;
|
|
|
|
create procedure p1() flush tables;
|
|
|
|
--error ER_STMT_NOT_ALLOWED_IN_SF_OR_TRG
|
|
|
|
insert into t1 values (0);
|
|
|
|
|
|
|
|
drop procedure p1;
|
|
|
|
create procedure p1() flush logs;
|
|
|
|
--error ER_STMT_NOT_ALLOWED_IN_SF_OR_TRG
|
|
|
|
insert into t1 values (0);
|
|
|
|
|
|
|
|
drop procedure p1;
|
|
|
|
create procedure p1() flush status;
|
|
|
|
--error ER_STMT_NOT_ALLOWED_IN_SF_OR_TRG
|
|
|
|
insert into t1 values (0);
|
|
|
|
|
|
|
|
drop procedure p1;
|
|
|
|
create procedure p1() flush slave;
|
|
|
|
--error ER_STMT_NOT_ALLOWED_IN_SF_OR_TRG
|
|
|
|
insert into t1 values (0);
|
|
|
|
|
|
|
|
drop procedure p1;
|
|
|
|
create procedure p1() flush master;
|
|
|
|
--error ER_STMT_NOT_ALLOWED_IN_SF_OR_TRG
|
|
|
|
insert into t1 values (0);
|
|
|
|
|
|
|
|
drop procedure p1;
|
|
|
|
create procedure p1() flush des_key_file;
|
|
|
|
--error ER_STMT_NOT_ALLOWED_IN_SF_OR_TRG
|
|
|
|
insert into t1 values (0);
|
|
|
|
|
|
|
|
drop procedure p1;
|
|
|
|
create procedure p1() flush user_resources;
|
|
|
|
--error ER_STMT_NOT_ALLOWED_IN_SF_OR_TRG
|
|
|
|
insert into t1 values (0);
|
|
|
|
|
2005-08-10 08:31:32 +02:00
|
|
|
drop procedure p1;
|
|
|
|
drop table t1;
|
2005-08-11 08:39:33 +02:00
|
|
|
|
2005-08-09 22:23:56 +02:00
|
|
|
# Test for bug #11973 "SELECT .. INTO var_name; in trigger cause
|
|
|
|
# crash on update"
|
2005-08-15 17:15:12 +02:00
|
|
|
|
2005-08-09 22:23:56 +02:00
|
|
|
create table t1 (id int, data int, username varchar(16));
|
|
|
|
insert into t1 (id, data) values (1, 0);
|
|
|
|
delimiter |;
|
|
|
|
create trigger t1_whoupdated before update on t1 for each row
|
|
|
|
begin
|
|
|
|
declare user varchar(32);
|
|
|
|
declare i int;
|
|
|
|
select user() into user;
|
|
|
|
set NEW.username = user;
|
|
|
|
select count(*) from ((select 1) union (select 2)) as d1 into i;
|
|
|
|
end|
|
|
|
|
delimiter ;|
|
|
|
|
update t1 set data = 1;
|
|
|
|
|
2005-09-15 01:56:09 +02:00
|
|
|
connection addconroot1;
|
2005-08-09 22:23:56 +02:00
|
|
|
update t1 set data = 2;
|
|
|
|
|
|
|
|
connection default;
|
2005-08-15 17:15:12 +02:00
|
|
|
drop table t1;
|
|
|
|
|
|
|
|
#
|
|
|
|
# #11587 Trigger causes lost connection error
|
|
|
|
#
|
|
|
|
|
|
|
|
create table t1 (c1 int, c2 datetime);
|
|
|
|
delimiter |;
|
|
|
|
--error ER_SP_NO_RETSET
|
|
|
|
create trigger tr1 before insert on t1 for each row
|
|
|
|
begin
|
|
|
|
set new.c2= '2004-04-01';
|
|
|
|
select 'hello';
|
|
|
|
end|
|
|
|
|
delimiter ;|
|
|
|
|
|
|
|
|
insert into t1 (c1) values (1),(2),(3);
|
|
|
|
select * from t1;
|
|
|
|
|
|
|
|
--disable_warnings
|
|
|
|
drop procedure if exists bug11587;
|
|
|
|
--enable_warnings
|
|
|
|
|
|
|
|
delimiter |;
|
|
|
|
create procedure bug11587(x char(16))
|
|
|
|
begin
|
|
|
|
select "hello";
|
|
|
|
select "hello again";
|
|
|
|
end|
|
|
|
|
|
|
|
|
create trigger tr1 before insert on t1 for each row
|
|
|
|
begin
|
|
|
|
call bug11587();
|
|
|
|
set new.c2= '2004-04-02';
|
|
|
|
end|
|
|
|
|
delimiter ;|
|
|
|
|
|
Implement WL#2661 "Prepared Statements: Dynamic SQL in Stored Procedures".
The idea of the patch is to separate statement processing logic,
such as parsing, validation of the parsed tree, execution and cleanup,
from global query processing logic, such as logging, resetting
priorities of a thread, resetting stored procedure cache, resetting
thread count of errors and warnings.
This makes PREPARE and EXECUTE behave similarly to the rest of SQL
statements and allows their use in stored procedures.
This patch contains a change in behaviour:
until recently for each SQL prepared statement command, 2 queries
were written to the general log, e.g.
[Query] prepare stmt from @stmt_text;
[Prepare] select * from t1 <-- contents of @stmt_text
The chagne was necessary to prevent [Prepare] commands from being written
to the general log when executing a stored procedure with Dynamic SQL.
We should consider whether the old behavior is preferrable and probably
restore it.
This patch refixes Bug#7115, Bug#10975 (partially), Bug#10605 (various bugs
in Dynamic SQL reported before it was disabled).
mysql-test/r/not_embedded_server.result:
Since we don't want to log Dynamic SQL in stored procedures,
now the general log gets only one log entry per SQL statement.
mysql-test/r/sp-error.result:
- remove obsolete tests
- a better error message for the case when a stored procedure that
returns a result set is called from a function
mysql-test/r/trigger.result:
- a better error message for the case when a stored procedure that
returns a result set is called from a trigger
mysql-test/t/sp-error.test:
- a better error message for the case when a stored procedure that
returns a result set is called from a function.
- move the comment to its place (end of file).
mysql-test/t/trigger.test:
- a better error message for the case when a stored procedure that
returns a result set is called from a trigger
sql/item_func.cc:
- we need to pass sql_command explicitly to get_var_with_binlog, because
when creating a query for SQL prepared statement thd->lex->sql_command
points at SQLCOM_EXECUTE, which is not listed in the list of update
queries.
sql/log_event.h:
- remove an extra copy of the previous sentence
sql/mysql_priv.h:
- fix declarations of sql_prepare.cc API
sql/share/errmsg.txt:
- a new error message, when one attempts to execute a prepared statement
which is currently being executed (this can happen only in Dynamic SQL
at the moment).
sql/sp_head.cc:
- extend sp_multi_results_command to return different flags for a
command (and rename it)
- add support for SQLCOM_PREPARE,SQLCOM_EXECUTE, SQLCOM_DEALLOCATE
to sp_get_flags_for_command
- replace multiple boolean sp_head members with uint m_flags
- a fix for a crash when user variables are used in a stored procedure
and binlog is on. A temporary fix for Bug#12637 "SP crashes the server
if it has update query with user var & binlog is enabled", which actually
stands for stored functions: now instead of a crash we break
replication if a user variable is used in a stored function which
is executed in prelocked mode.
sql/sp_head.h:
- replace multiple boolean flags of sp_head with uint m_flags;
- add flag CONTAINS_DYNAMIC_SQL
- use this flag to error if a stored procedure with Dynamic SQL is
called from a function or trigger.
sql/sql_class.cc:
- Statement_map::insert should not delete a statement if it exists,
now it's done externally to be able to handle the case when the
statement being deleted is in use.
- remove extra code (free_list is already reset in free_items)
sql/sql_lex.cc:
- add lex->stmt_prepare_mode; we can't rely on thd->command any more,
because we don't reset it any more (Dynamic SQL requirement is that
PS are as little intrusive as possible).
sql/sql_lex.h:
- declare bool LEX::stmt_prepare_mode
sql/sql_parse.cc:
- move prepared statement code to sql_prepare.cc
- change declarations (refactored code)
- better error message when one attempts to use Dynamic SQL or a
stored procedure that returns a result set in a function or trigger.
sql/sql_prepare.cc:
- major refactoring to ensure PREPARE/EXECUTE commands do not reset global THD
state and allow their use in stored procedures.
- add Prepared_statement::flags and use it to ensure no recursive execution
of a prepared statement is possible
- better comments
sql/sql_yacc.yy:
- enable PREPARE/EXECUTE/DEALLOCATE in stored procedures
- produce an error message on attempt to use PREPARE/EXECUTE/DEALLOCATE
in a stored function or trigger
mysql-test/r/sp-dynamic.result:
- sp-dynamic.test results
mysql-test/t/sp-dynamic.test:
- a new test for PREPARE/EXECUTE/DEALLOCATE in stored procedures.
2005-09-03 01:13:18 +02:00
|
|
|
--error ER_SP_NO_RETSET
|
2005-08-15 17:15:12 +02:00
|
|
|
insert into t1 (c1) values (4),(5),(6);
|
|
|
|
select * from t1;
|
|
|
|
|
|
|
|
drop procedure bug11587;
|
2005-08-09 22:23:56 +02:00
|
|
|
drop table t1;
|
2005-08-18 17:07:23 +02:00
|
|
|
|
|
|
|
# Test for bug #11896 "Partial locking in case of recursive trigger
|
|
|
|
# definitions". Recursion in triggers should not be allowed.
|
|
|
|
# We also should not allow to change tables which are used in
|
|
|
|
# statements invoking this trigger.
|
|
|
|
create table t1 (f1 integer);
|
|
|
|
create table t2 (f2 integer);
|
|
|
|
create trigger t1_ai after insert on t1
|
|
|
|
for each row insert into t2 values (new.f1+1);
|
|
|
|
create trigger t2_ai after insert on t2
|
|
|
|
for each row insert into t1 values (new.f2+1);
|
2005-11-23 00:11:19 +01:00
|
|
|
# Allow SP resursion to be show that it has not influence here
|
|
|
|
set @SAVE_SP_RECURSION_LEVELS=@@max_sp_recursion_depth;
|
|
|
|
set @@max_sp_recursion_depth=100;
|
2005-08-18 17:07:23 +02:00
|
|
|
--error ER_CANT_UPDATE_USED_TABLE_IN_SF_OR_TRG
|
|
|
|
insert into t1 values (1);
|
2005-11-23 00:11:19 +01:00
|
|
|
set @@max_sp_recursion_depth=@SAVE_SP_RECURSION_LEVELS;
|
2005-08-18 17:07:23 +02:00
|
|
|
select * from t1;
|
|
|
|
select * from t2;
|
|
|
|
drop trigger t1_ai;
|
|
|
|
drop trigger t2_ai;
|
|
|
|
create trigger t1_bu before update on t1
|
|
|
|
for each row insert into t1 values (2);
|
|
|
|
--error ER_CANT_UPDATE_USED_TABLE_IN_SF_OR_TRG
|
|
|
|
update t1 set f1= 10;
|
|
|
|
select * from t1;
|
|
|
|
drop trigger t1_bu;
|
|
|
|
create trigger t1_bu before update on t1
|
|
|
|
for each row delete from t1 where f1=new.f1;
|
|
|
|
--error ER_CANT_UPDATE_USED_TABLE_IN_SF_OR_TRG
|
|
|
|
update t1 set f1= 10;
|
|
|
|
select * from t1;
|
|
|
|
drop trigger t1_bu;
|
|
|
|
# This should work tough
|
|
|
|
create trigger t1_bi before insert on t1
|
|
|
|
for each row set new.f1=(select sum(f1) from t1);
|
|
|
|
insert into t1 values (3);
|
|
|
|
select * from t1;
|
|
|
|
drop trigger t1_bi;
|
|
|
|
drop tables t1, t2;
|
2005-09-15 01:56:09 +02:00
|
|
|
|
|
|
|
# Tests for bug #12704 "Server crashes during trigger execution".
|
|
|
|
# If we run DML statements and CREATE TRIGGER statements concurrently
|
|
|
|
# it may happen that trigger will be created while DML statement is
|
|
|
|
# waiting for table lock. In this case we have to reopen tables and
|
|
|
|
# recalculate prelocking set.
|
|
|
|
# Unfortunately these tests rely on the order in which tables are locked
|
|
|
|
# by statement so they are non determenistic and are disabled.
|
|
|
|
--disable_parsing
|
|
|
|
create table t1 (id int);
|
|
|
|
create table t2 (id int);
|
|
|
|
create table t3 (id int);
|
|
|
|
create function f1() returns int return (select max(id)+2 from t2);
|
|
|
|
create view v1 as select f1() as f;
|
|
|
|
|
|
|
|
# Let us check that we notice trigger at all
|
|
|
|
connection addconroot1;
|
|
|
|
lock tables t2 write;
|
|
|
|
connection default;
|
|
|
|
send insert into t1 values ((select max(id) from t2)), (2);
|
|
|
|
--sleep 1
|
|
|
|
connection addconroot2;
|
|
|
|
create trigger t1_trg before insert on t1 for each row set NEW.id:= 1;
|
|
|
|
connection addconroot1;
|
|
|
|
unlock tables;
|
|
|
|
connection default;
|
|
|
|
reap;
|
|
|
|
select * from t1;
|
|
|
|
|
|
|
|
# Check that we properly calculate new prelocking set
|
|
|
|
insert into t2 values (3);
|
|
|
|
connection addconroot1;
|
|
|
|
lock tables t2 write;
|
|
|
|
connection default;
|
|
|
|
send insert into t1 values ((select max(id) from t2)), (4);
|
|
|
|
--sleep 1
|
|
|
|
connection addconroot2;
|
|
|
|
drop trigger t1_trg;
|
|
|
|
create trigger t1_trg before insert on t1 for each row
|
|
|
|
insert into t3 values (new.id);
|
|
|
|
connection addconroot1;
|
|
|
|
unlock tables;
|
|
|
|
connection default;
|
|
|
|
reap;
|
|
|
|
select * from t1;
|
|
|
|
select * from t3;
|
|
|
|
|
|
|
|
# We should be able to do this even if fancy views are involved
|
|
|
|
connection addconroot1;
|
|
|
|
lock tables t2 write;
|
|
|
|
connection default;
|
|
|
|
send insert into t1 values ((select max(f) from v1)), (6);
|
|
|
|
--sleep 1
|
|
|
|
connection addconroot2;
|
|
|
|
drop trigger t1_trg;
|
|
|
|
create trigger t1_trg before insert on t1 for each row
|
|
|
|
insert into t3 values (new.id + 100);
|
|
|
|
connection addconroot1;
|
|
|
|
unlock tables;
|
|
|
|
connection default;
|
|
|
|
reap;
|
|
|
|
select * from t1;
|
|
|
|
select * from t3;
|
|
|
|
|
|
|
|
# This also should work for multi-update
|
|
|
|
# Let us drop trigger to demonstrate that prelocking set is really
|
|
|
|
# rebuilt
|
|
|
|
drop trigger t1_trg;
|
|
|
|
connection addconroot1;
|
|
|
|
lock tables t2 write;
|
|
|
|
connection default;
|
|
|
|
send update t1, t2 set t1.id=10 where t1.id=t2.id;
|
|
|
|
--sleep 1
|
|
|
|
connection addconroot2;
|
|
|
|
create trigger t1_trg before update on t1 for each row
|
|
|
|
insert into t3 values (new.id);
|
|
|
|
connection addconroot1;
|
|
|
|
unlock tables;
|
|
|
|
connection default;
|
|
|
|
reap;
|
|
|
|
select * from t1;
|
|
|
|
select * from t3;
|
|
|
|
|
|
|
|
# And even for multi-update converted from ordinary update thanks to view
|
|
|
|
drop view v1;
|
|
|
|
drop trigger t1_trg;
|
|
|
|
create view v1 as select t1.id as id1 from t1, t2 where t1.id= t2.id;
|
|
|
|
insert into t2 values (10);
|
|
|
|
connection addconroot1;
|
|
|
|
lock tables t2 write;
|
|
|
|
connection default;
|
|
|
|
send update v1 set id1= 11;
|
|
|
|
--sleep 1
|
|
|
|
connection addconroot2;
|
|
|
|
create trigger t1_trg before update on t1 for each row
|
|
|
|
insert into t3 values (new.id + 100);
|
|
|
|
connection addconroot1;
|
|
|
|
unlock tables;
|
|
|
|
connection default;
|
|
|
|
reap;
|
|
|
|
select * from t1;
|
|
|
|
select * from t3;
|
|
|
|
|
|
|
|
drop function f1;
|
|
|
|
drop view v1;
|
|
|
|
drop table t1, t2, t3;
|
|
|
|
--enable_parsing
|
2005-11-17 01:51:14 +01:00
|
|
|
|
|
|
|
#
|
|
|
|
# Test for bug #13399 "Crash when executing PS/SP which should activate
|
|
|
|
# trigger which is now dropped". See also test for similar bug for stored
|
|
|
|
# routines in sp-error.test (#12329).
|
|
|
|
create table t1 (id int);
|
|
|
|
create table t2 (id int);
|
|
|
|
create trigger t1_bi before insert on t1 for each row insert into t2 values (new.id);
|
|
|
|
prepare stmt1 from "insert into t1 values (10)";
|
|
|
|
create procedure p1() insert into t1 values (10);
|
|
|
|
call p1();
|
|
|
|
# Actually it is enough to do FLUSH TABLES instead of DROP TRIGGER
|
|
|
|
drop trigger t1_bi;
|
|
|
|
# Server should not crash on these two statements
|
|
|
|
execute stmt1;
|
|
|
|
call p1();
|
|
|
|
deallocate prepare stmt1;
|
|
|
|
drop procedure p1;
|
|
|
|
|
|
|
|
# Let us test more complex situation when we alter trigger in such way that
|
|
|
|
# it uses different set of tables (or simply add new trigger).
|
|
|
|
create table t3 (id int);
|
|
|
|
create trigger t1_bi after insert on t1 for each row insert into t2 values (new.id);
|
|
|
|
prepare stmt1 from "insert into t1 values (10)";
|
|
|
|
create procedure p1() insert into t1 values (10);
|
|
|
|
call p1();
|
|
|
|
# Altering trigger forcing it use different set of tables
|
|
|
|
drop trigger t1_bi;
|
|
|
|
create trigger t1_bi after insert on t1 for each row insert into t3 values (new.id);
|
|
|
|
execute stmt1;
|
|
|
|
call p1();
|
|
|
|
deallocate prepare stmt1;
|
|
|
|
drop procedure p1;
|
|
|
|
drop table t1, t2, t3;
|
2005-11-22 23:58:13 +01:00
|
|
|
|
2005-11-22 23:50:37 +01:00
|
|
|
#
|
|
|
|
# BUG#13549 "Server crash with nested stored procedures".
|
|
|
|
# Server should not crash when during execution of stored procedure
|
|
|
|
# we have to parse trigger/function definition and this new trigger/
|
|
|
|
# function has more local variables declared than invoking stored
|
|
|
|
# procedure and last of these variables is used in argument of NOT
|
|
|
|
# operator.
|
|
|
|
#
|
|
|
|
create table t1 (a int);
|
|
|
|
DELIMITER //;
|
2006-01-05 23:47:49 +01:00
|
|
|
CREATE PROCEDURE `p1`()
|
2005-11-22 23:50:37 +01:00
|
|
|
begin
|
|
|
|
insert into t1 values (1);
|
|
|
|
end//
|
|
|
|
create trigger trg before insert on t1 for each row
|
|
|
|
begin
|
|
|
|
declare done int default 0;
|
|
|
|
set done= not done;
|
|
|
|
end//
|
|
|
|
DELIMITER ;//
|
2006-01-05 23:47:49 +01:00
|
|
|
CALL p1();
|
|
|
|
drop procedure p1;
|
2005-11-22 23:50:37 +01:00
|
|
|
drop table t1;
|
|
|
|
|
2005-12-11 13:26:15 +01:00
|
|
|
#
|
|
|
|
# Test for bug #14863 "Triggers: crash if create and there is no current
|
|
|
|
# database". We should not crash and give proper error when database for
|
|
|
|
# trigger or its table is not specified and there is no current database.
|
|
|
|
#
|
|
|
|
connection addconwithoutdb;
|
|
|
|
--error ER_NO_DB_ERROR
|
|
|
|
create trigger t1_bi before insert on test.t1 for each row set @a:=0;
|
A fix and a test case for Bug#29050 Creation of a legal stored procedure
fails if a database is not selected prior.
The problem manifested itself when a user tried to
create a routine that had non-fully-qualified identifiers in its bodies
and there was no current database selected.
This is a regression introduced by the fix for Bug 19022:
The patch for Bug 19022 changes the code to always produce a warning
if we can't resolve the current database in the parser.
In this case this was not necessary, since even though the produced
parsed tree was incorrect, we never re-use sphead
that was obtained at first parsing of CREATE PROCEDURE.
The sphead that is anyhow used is always obtained through db_load_routine,
and there we change the current database to sphead->m_db before
calling yyparse.
The idea of the fix is to resolve the current database directly using
lex->sphead->m_db member when parsing a stored routine body, when
such is present.
This patch removes the need to reset the current database
when loading a trigger or routine definition into SP cache.
The redundant code will be removed in 5.1.
mysql-test/r/sp.result:
Update test results (Bug#29050)
mysql-test/r/trigger.result:
Update results.
mysql-test/t/sp.test:
Add a test case for Bug#29050
mysql-test/t/trigger.test:
Fix wrong behavior covered with tests.
sql/sql_lex.cc:
Implement st_lex::copy_db_to().
sql/sql_lex.h:
Declare st_lex::copy_db_to().
sql/sql_parse.cc:
Use st_lex::copy_db_to() in add_table_to_list, rather than
THD::copy_db_to(). The former will use the database of the sphead,
if we're parsing a stored routine, not the default database in
THD. The default database is needed to initialize tables->db
when the database part was not explicitly specified in the identifier.
sql/sql_yacc.yy:
Use st_lex::copy_db_to() in the parser, rather than
THD::copy_db_to(). The former will use the database of the sphead,
if we're parsing a stored routine, not the default database in
THD.
2007-07-05 09:34:04 +02:00
|
|
|
--error ER_NO_SUCH_TABLE
|
2005-12-11 13:26:15 +01:00
|
|
|
create trigger test.t1_bi before insert on t1 for each row set @a:=0;
|
|
|
|
--error ER_NO_DB_ERROR
|
|
|
|
drop trigger t1_bi;
|
|
|
|
connection default;
|
2006-01-28 10:50:16 +01:00
|
|
|
|
2006-02-24 21:50:36 +01:00
|
|
|
#
|
2006-03-04 14:55:06 +01:00
|
|
|
# Tests for bug #13525 "Rename table does not keep info of triggers"
|
|
|
|
# and bug #17866 "Problem with renaming table with triggers with fully
|
|
|
|
# qualified subject table".
|
2006-02-24 21:50:36 +01:00
|
|
|
#
|
|
|
|
create table t1 (id int);
|
|
|
|
create trigger t1_bi before insert on t1 for each row set @a:=new.id;
|
2006-03-04 14:55:06 +01:00
|
|
|
create trigger t1_ai after insert on test.t1 for each row set @b:=new.id;
|
2006-02-24 21:50:36 +01:00
|
|
|
insert into t1 values (101);
|
2006-03-04 14:55:06 +01:00
|
|
|
select @a, @b;
|
2006-02-24 21:50:36 +01:00
|
|
|
select trigger_schema, trigger_name, event_object_schema,
|
|
|
|
event_object_table, action_statement from information_schema.triggers
|
|
|
|
where event_object_schema = 'test';
|
|
|
|
rename table t1 to t2;
|
|
|
|
# Trigger should work after rename
|
|
|
|
insert into t2 values (102);
|
2006-03-04 14:55:06 +01:00
|
|
|
select @a, @b;
|
2006-02-24 21:50:36 +01:00
|
|
|
select trigger_schema, trigger_name, event_object_schema,
|
|
|
|
event_object_table, action_statement from information_schema.triggers
|
|
|
|
where event_object_schema = 'test';
|
|
|
|
# Let us check that the same works for simple ALTER TABLE ... RENAME
|
|
|
|
alter table t2 rename to t3;
|
|
|
|
insert into t3 values (103);
|
2006-03-04 14:55:06 +01:00
|
|
|
select @a, @b;
|
2006-02-24 21:50:36 +01:00
|
|
|
select trigger_schema, trigger_name, event_object_schema,
|
|
|
|
event_object_table, action_statement from information_schema.triggers
|
|
|
|
where event_object_schema = 'test';
|
|
|
|
# And for more complex ALTER TABLE
|
|
|
|
alter table t3 rename to t4, add column val int default 0;
|
|
|
|
insert into t4 values (104, 1);
|
2006-03-04 14:55:06 +01:00
|
|
|
select @a, @b;
|
2006-02-24 21:50:36 +01:00
|
|
|
select trigger_schema, trigger_name, event_object_schema,
|
|
|
|
event_object_table, action_statement from information_schema.triggers
|
|
|
|
where event_object_schema = 'test';
|
|
|
|
# .TRN file should be updated with new table name
|
|
|
|
drop trigger t1_bi;
|
2006-03-04 14:55:06 +01:00
|
|
|
drop trigger t1_ai;
|
2006-02-24 21:50:36 +01:00
|
|
|
drop table t4;
|
|
|
|
# Rename between different databases if triggers exist should fail
|
|
|
|
create database mysqltest;
|
|
|
|
use mysqltest;
|
|
|
|
create table t1 (id int);
|
|
|
|
create trigger t1_bi before insert on t1 for each row set @a:=new.id;
|
|
|
|
insert into t1 values (101);
|
|
|
|
select @a;
|
|
|
|
select trigger_schema, trigger_name, event_object_schema,
|
|
|
|
event_object_table, action_statement from information_schema.triggers
|
|
|
|
where event_object_schema = 'test' or event_object_schema = 'mysqltest';
|
|
|
|
--error ER_TRG_IN_WRONG_SCHEMA
|
|
|
|
rename table t1 to test.t2;
|
|
|
|
insert into t1 values (102);
|
|
|
|
select @a;
|
|
|
|
select trigger_schema, trigger_name, event_object_schema,
|
|
|
|
event_object_table, action_statement from information_schema.triggers
|
|
|
|
where event_object_schema = 'test' or event_object_schema = 'mysqltest';
|
|
|
|
# There should be no fantom .TRN files
|
|
|
|
--error ER_TRG_DOES_NOT_EXIST
|
|
|
|
drop trigger test.t1_bi;
|
2006-03-24 12:58:18 +01:00
|
|
|
# Let us also check handling of this restriction in ALTER TABLE ... RENAME
|
|
|
|
--error ER_TRG_IN_WRONG_SCHEMA
|
|
|
|
alter table t1 rename to test.t1;
|
|
|
|
insert into t1 values (103);
|
|
|
|
select @a;
|
|
|
|
select trigger_schema, trigger_name, event_object_schema,
|
|
|
|
event_object_table, action_statement from information_schema.triggers
|
|
|
|
where event_object_schema = 'test' or event_object_schema = 'mysqltest';
|
|
|
|
# Again there should be no fantom .TRN files
|
|
|
|
--error ER_TRG_DOES_NOT_EXIST
|
|
|
|
drop trigger test.t1_bi;
|
|
|
|
--error ER_TRG_IN_WRONG_SCHEMA
|
|
|
|
alter table t1 rename to test.t1, add column val int default 0;
|
|
|
|
insert into t1 values (104);
|
|
|
|
select @a;
|
|
|
|
select trigger_schema, trigger_name, event_object_schema,
|
|
|
|
event_object_table, action_statement from information_schema.triggers
|
|
|
|
where event_object_schema = 'test' or event_object_schema = 'mysqltest';
|
|
|
|
# Table definition should not change
|
|
|
|
show create table t1;
|
|
|
|
# And once again check for fantom .TRN files
|
|
|
|
--error ER_TRG_DOES_NOT_EXIST
|
|
|
|
drop trigger test.t1_bi;
|
2006-02-24 21:50:36 +01:00
|
|
|
drop trigger t1_bi;
|
|
|
|
drop table t1;
|
|
|
|
drop database mysqltest;
|
|
|
|
use test;
|
|
|
|
# And now let us check that the properly handle rename if there is some
|
|
|
|
# error during it (that we rollback such renames completely).
|
|
|
|
create table t1 (id int);
|
|
|
|
create trigger t1_bi before insert on t1 for each row set @a:=new.id;
|
|
|
|
create trigger t1_ai after insert on t1 for each row set @b:=new.id;
|
|
|
|
insert into t1 values (101);
|
|
|
|
select @a, @b;
|
|
|
|
select trigger_schema, trigger_name, event_object_schema,
|
|
|
|
event_object_table, action_statement from information_schema.triggers
|
|
|
|
where event_object_schema = 'test';
|
|
|
|
# Trick which makes update of second .TRN file impossible
|
2007-12-12 18:19:24 +01:00
|
|
|
let $MYSQLD_DATADIR= `select @@datadir`;
|
|
|
|
write_file $MYSQLD_DATADIR/test/t1_ai.TRN~;
|
2006-12-22 00:38:34 +01:00
|
|
|
dummy
|
|
|
|
EOF
|
2007-12-12 18:19:24 +01:00
|
|
|
chmod 0000 $MYSQLD_DATADIR/test/t1_ai.TRN~;
|
2007-08-15 10:18:41 +02:00
|
|
|
# Normalize the datadir path; the embedded server doesn't chdir to datadir
|
2008-02-25 16:41:59 +01:00
|
|
|
--replace_result $MYSQLTEST_VARDIR . mysqld.1/data/ ''
|
2006-02-24 21:50:36 +01:00
|
|
|
--error 1
|
|
|
|
rename table t1 to t2;
|
|
|
|
# 't1' should be still there and triggers should work correctly
|
|
|
|
insert into t1 values (102);
|
|
|
|
select @a, @b;
|
|
|
|
select trigger_schema, trigger_name, event_object_schema,
|
|
|
|
event_object_table, action_statement from information_schema.triggers
|
|
|
|
where event_object_schema = 'test';
|
2007-12-12 18:19:24 +01:00
|
|
|
chmod 0600 $MYSQLD_DATADIR/test/t1_ai.TRN~;
|
|
|
|
remove_file $MYSQLD_DATADIR/test/t1_ai.TRN~;
|
2006-02-24 21:50:36 +01:00
|
|
|
# Let us check that updates to .TRN files were rolled back too
|
|
|
|
drop trigger t1_bi;
|
|
|
|
drop trigger t1_ai;
|
|
|
|
drop table t1;
|
2006-02-26 14:38:48 +01:00
|
|
|
|
2006-01-28 10:50:16 +01:00
|
|
|
# Test for bug #16829 "Firing trigger with RETURN crashes the server"
|
|
|
|
# RETURN is not supposed to be used anywhere except functions, so error
|
|
|
|
# should be returned when one attempts to create trigger with RETURN.
|
|
|
|
create table t1 (i int);
|
|
|
|
--error ER_SP_BADRETURN
|
|
|
|
create trigger t1_bi before insert on t1 for each row return 0;
|
|
|
|
insert into t1 values (1);
|
|
|
|
drop table t1;
|
2006-03-29 12:53:00 +02:00
|
|
|
|
|
|
|
# Test for bug #17764 "Trigger crashes MyISAM table"
|
|
|
|
#
|
|
|
|
# Table was reported as crashed when it was subject table of trigger invoked
|
|
|
|
# by insert statement which was executed with enabled bulk insert mode (which
|
|
|
|
# is actually set of optimizations enabled by handler::start_bulk_insert())
|
|
|
|
# and this trigger also explicitly referenced it.
|
|
|
|
# The same problem arose when table to which bulk insert was done was also
|
|
|
|
# referenced in function called by insert statement.
|
|
|
|
create table t1 (a varchar(64), b int);
|
|
|
|
create table t2 like t1;
|
|
|
|
create trigger t1_ai after insert on t1 for each row
|
|
|
|
set @a:= (select max(a) from t1);
|
|
|
|
insert into t1 (a) values
|
|
|
|
("Twas"),("brillig"),("and"),("the"),("slithy"),("toves"),
|
|
|
|
("Did"),("gyre"),("and"),("gimble"),("in"),("the"),("wabe");
|
|
|
|
create trigger t2_ai after insert on t2 for each row
|
|
|
|
set @a:= (select max(a) from t2);
|
|
|
|
insert into t2 select * from t1;
|
2007-12-12 18:19:24 +01:00
|
|
|
load data infile '../../std_data/words.dat' into table t1 (a);
|
2006-03-29 12:53:00 +02:00
|
|
|
drop trigger t1_ai;
|
|
|
|
drop trigger t2_ai;
|
|
|
|
# Test that the problem for functions is fixed as well
|
|
|
|
create function f1() returns int return (select max(b) from t1);
|
|
|
|
insert into t1 values
|
|
|
|
("All",f1()),("mimsy",f1()),("were",f1()),("the",f1()),("borogoves",f1()),
|
|
|
|
("And",f1()),("the",f1()),("mome", f1()),("raths",f1()),("outgrabe",f1());
|
|
|
|
create function f2() returns int return (select max(b) from t2);
|
|
|
|
insert into t2 select a, f2() from t1;
|
2007-12-12 18:19:24 +01:00
|
|
|
load data infile '../../std_data/words.dat' into table t1 (a) set b:= f1();
|
2006-03-29 12:53:00 +02:00
|
|
|
drop function f1;
|
|
|
|
drop function f2;
|
2006-05-10 21:35:05 +02:00
|
|
|
drop table t1, t2;
|
2006-04-12 17:31:00 +02:00
|
|
|
|
2006-04-19 17:13:03 +02:00
|
|
|
#
|
|
|
|
# Test for bug #16021 "Wrong index given to function in trigger" which
|
|
|
|
# was caused by the same bulk insert optimization as bug #17764 but had
|
|
|
|
# slightly different symptoms (instead of reporting table as crashed
|
|
|
|
# storage engine reported error number 124)
|
|
|
|
#
|
|
|
|
create table t1(i int not null, j int not null, n numeric(15,2), primary key(i,j));
|
|
|
|
create table t2(i int not null, n numeric(15,2), primary key(i));
|
|
|
|
delimiter |;
|
|
|
|
create trigger t1_ai after insert on t1 for each row
|
|
|
|
begin
|
|
|
|
declare sn numeric(15,2);
|
|
|
|
select sum(n) into sn from t1 where i=new.i;
|
|
|
|
replace into t2 values(new.i, sn);
|
|
|
|
end|
|
|
|
|
delimiter ;|
|
|
|
|
insert into t1 values
|
|
|
|
(1,1,10.00),(1,2,10.00),(1,3,10.00),(1,4,10.00),(1,5,10.00),
|
|
|
|
(1,6,10.00),(1,7,10.00),(1,8,10.00),(1,9,10.00),(1,10,10.00),
|
|
|
|
(1,11,10.00),(1,12,10.00),(1,13,10.00),(1,14,10.00),(1,15,10.00);
|
|
|
|
select * from t1;
|
|
|
|
select * from t2;
|
|
|
|
drop tables t1, t2;
|
|
|
|
|
2006-04-12 17:31:00 +02:00
|
|
|
#
|
|
|
|
# Test for Bug #16461 connection_id() does not work properly inside trigger
|
|
|
|
#
|
|
|
|
--disable_warnings
|
|
|
|
DROP TABLE IF EXISTS t1;
|
|
|
|
--enable_warnings
|
|
|
|
|
|
|
|
CREATE TABLE t1 (
|
|
|
|
conn_id INT,
|
|
|
|
trigger_conn_id INT
|
|
|
|
);
|
|
|
|
CREATE TRIGGER t1_bi BEFORE INSERT ON t1 FOR EACH ROW
|
|
|
|
SET NEW.trigger_conn_id = CONNECTION_ID();
|
|
|
|
|
|
|
|
INSERT INTO t1 (conn_id, trigger_conn_id) VALUES (CONNECTION_ID(), -1);
|
|
|
|
|
|
|
|
connect (con1,localhost,root,,);
|
|
|
|
INSERT INTO t1 (conn_id, trigger_conn_id) VALUES (CONNECTION_ID(), -1);
|
|
|
|
connection default;
|
|
|
|
disconnect con1;
|
|
|
|
|
|
|
|
SELECT * FROM t1 WHERE conn_id != trigger_conn_id;
|
|
|
|
|
|
|
|
DROP TRIGGER t1_bi;
|
|
|
|
DROP TABLE t1;
|
|
|
|
|
2006-04-19 12:27:59 +02:00
|
|
|
|
|
|
|
#
|
|
|
|
# Bug#6951: Triggers/Traditional: SET @ result wrong
|
|
|
|
#
|
|
|
|
--disable_warnings
|
|
|
|
DROP TABLE IF EXISTS t1;
|
|
|
|
--enable_warnings
|
|
|
|
|
|
|
|
CREATE TABLE t1 (i1 INT);
|
|
|
|
|
|
|
|
SET @save_sql_mode=@@sql_mode;
|
|
|
|
|
|
|
|
SET SQL_MODE='';
|
|
|
|
|
|
|
|
CREATE TRIGGER t1_ai AFTER INSERT ON t1 FOR EACH ROW
|
|
|
|
SET @x = 5/0;
|
|
|
|
|
|
|
|
SET SQL_MODE='traditional';
|
|
|
|
|
|
|
|
CREATE TRIGGER t1_au AFTER UPDATE ON t1 FOR EACH ROW
|
|
|
|
SET @x = 5/0;
|
|
|
|
|
|
|
|
SET @x=1;
|
|
|
|
INSERT INTO t1 VALUES (@x);
|
|
|
|
SELECT @x;
|
|
|
|
|
|
|
|
SET @x=2;
|
|
|
|
UPDATE t1 SET i1 = @x;
|
|
|
|
SELECT @x;
|
|
|
|
|
|
|
|
SET SQL_MODE='';
|
|
|
|
|
|
|
|
SET @x=3;
|
|
|
|
INSERT INTO t1 VALUES (@x);
|
|
|
|
SELECT @x;
|
|
|
|
|
|
|
|
SET @x=4;
|
|
|
|
UPDATE t1 SET i1 = @x;
|
|
|
|
SELECT @x;
|
|
|
|
|
|
|
|
SET @@sql_mode=@save_sql_mode;
|
|
|
|
|
|
|
|
DROP TRIGGER t1_ai;
|
|
|
|
DROP TRIGGER t1_au;
|
|
|
|
DROP TABLE t1;
|
|
|
|
|
2006-05-12 11:55:21 +02:00
|
|
|
|
|
|
|
#
|
|
|
|
# Test for bug #14635 Accept NEW.x as INOUT parameters to stored
|
|
|
|
# procedures from within triggers
|
|
|
|
#
|
|
|
|
--disable_warnings
|
|
|
|
DROP TABLE IF EXISTS t1;
|
|
|
|
DROP PROCEDURE IF EXISTS p1;
|
|
|
|
DROP PROCEDURE IF EXISTS p2;
|
|
|
|
--enable_warnings
|
|
|
|
|
|
|
|
CREATE TABLE t1 (i1 INT);
|
|
|
|
|
|
|
|
# Check that NEW.x pseudo variable is accepted as INOUT and OUT
|
|
|
|
# parameter to stored routine.
|
|
|
|
INSERT INTO t1 VALUES (3);
|
|
|
|
CREATE PROCEDURE p1(OUT i1 INT) DETERMINISTIC NO SQL SET i1 = 5;
|
|
|
|
CREATE PROCEDURE p2(INOUT i1 INT) DETERMINISTIC NO SQL SET i1 = i1 * 7;
|
|
|
|
delimiter //;
|
|
|
|
CREATE TRIGGER t1_bu BEFORE UPDATE ON t1 FOR EACH ROW
|
|
|
|
BEGIN
|
|
|
|
CALL p1(NEW.i1);
|
|
|
|
CALL p2(NEW.i1);
|
|
|
|
END//
|
|
|
|
delimiter ;//
|
|
|
|
UPDATE t1 SET i1 = 11 WHERE i1 = 3;
|
|
|
|
DROP TRIGGER t1_bu;
|
|
|
|
DROP PROCEDURE p2;
|
|
|
|
DROP PROCEDURE p1;
|
|
|
|
|
|
|
|
# Check that OLD.x pseudo variable is not accepted as INOUT and OUT
|
|
|
|
# parameter to stored routine.
|
|
|
|
INSERT INTO t1 VALUES (13);
|
|
|
|
CREATE PROCEDURE p1(OUT i1 INT) DETERMINISTIC NO SQL SET @a = 17;
|
|
|
|
CREATE TRIGGER t1_bu BEFORE UPDATE ON t1 FOR EACH ROW
|
|
|
|
CALL p1(OLD.i1);
|
|
|
|
--error ER_SP_NOT_VAR_ARG
|
|
|
|
UPDATE t1 SET i1 = 19 WHERE i1 = 13;
|
|
|
|
DROP TRIGGER t1_bu;
|
|
|
|
DROP PROCEDURE p1;
|
|
|
|
|
|
|
|
INSERT INTO t1 VALUES (23);
|
|
|
|
CREATE PROCEDURE p1(INOUT i1 INT) DETERMINISTIC NO SQL SET @a = i1 * 29;
|
|
|
|
CREATE TRIGGER t1_bu BEFORE UPDATE ON t1 FOR EACH ROW
|
|
|
|
CALL p1(OLD.i1);
|
|
|
|
--error ER_SP_NOT_VAR_ARG
|
|
|
|
UPDATE t1 SET i1 = 31 WHERE i1 = 23;
|
|
|
|
DROP TRIGGER t1_bu;
|
|
|
|
DROP PROCEDURE p1;
|
|
|
|
|
|
|
|
# Check that NEW.x pseudo variable is read-only in the AFTER TRIGGER.
|
|
|
|
INSERT INTO t1 VALUES (37);
|
|
|
|
CREATE PROCEDURE p1(OUT i1 INT) DETERMINISTIC NO SQL SET @a = 41;
|
|
|
|
CREATE TRIGGER t1_au AFTER UPDATE ON t1 FOR EACH ROW
|
|
|
|
CALL p1(NEW.i1);
|
|
|
|
--error ER_SP_NOT_VAR_ARG
|
|
|
|
UPDATE t1 SET i1 = 43 WHERE i1 = 37;
|
|
|
|
DROP TRIGGER t1_au;
|
|
|
|
DROP PROCEDURE p1;
|
|
|
|
|
|
|
|
INSERT INTO t1 VALUES (47);
|
|
|
|
CREATE PROCEDURE p1(INOUT i1 INT) DETERMINISTIC NO SQL SET @a = i1 * 49;
|
|
|
|
CREATE TRIGGER t1_au AFTER UPDATE ON t1 FOR EACH ROW
|
|
|
|
CALL p1(NEW.i1);
|
|
|
|
--error ER_SP_NOT_VAR_ARG
|
|
|
|
UPDATE t1 SET i1 = 51 WHERE i1 = 47;
|
|
|
|
DROP TRIGGER t1_au;
|
|
|
|
DROP PROCEDURE p1;
|
|
|
|
|
|
|
|
# Post requisite.
|
|
|
|
SELECT * FROM t1;
|
|
|
|
|
|
|
|
DROP TABLE t1;
|
|
|
|
|
2006-06-28 02:16:02 +02:00
|
|
|
#
|
|
|
|
# Bug #18005: Creating a trigger on mysql.event leads to server crash on
|
|
|
|
# scheduler startup
|
|
|
|
#
|
|
|
|
# Bug #18361: Triggers on mysql.user table cause server crash
|
|
|
|
#
|
|
|
|
# We don't allow triggers on the mysql schema
|
|
|
|
delimiter |;
|
|
|
|
--error ER_NO_TRIGGERS_ON_SYSTEM_SCHEMA
|
|
|
|
create trigger wont_work after update on mysql.user for each row
|
|
|
|
begin
|
|
|
|
set @a:= 1;
|
|
|
|
end|
|
|
|
|
# Try when we're already using the mysql schema
|
|
|
|
use mysql|
|
|
|
|
--error ER_NO_TRIGGERS_ON_SYSTEM_SCHEMA
|
|
|
|
create trigger wont_work after update on event for each row
|
|
|
|
begin
|
|
|
|
set @a:= 1;
|
|
|
|
end|
|
2006-08-23 19:31:00 +02:00
|
|
|
use test|
|
2006-06-28 02:16:02 +02:00
|
|
|
delimiter ;|
|
|
|
|
|
2006-08-23 19:31:00 +02:00
|
|
|
|
|
|
|
#
|
|
|
|
# Test for BUG#16899: Possible buffer overflow in handling of DEFINER-clause.
|
|
|
|
#
|
|
|
|
|
|
|
|
# Prepare.
|
|
|
|
|
|
|
|
--disable_warnings
|
|
|
|
DROP TABLE IF EXISTS t1;
|
|
|
|
DROP TABLE IF EXISTS t2;
|
|
|
|
--enable_warnings
|
|
|
|
|
|
|
|
CREATE TABLE t1(c INT);
|
|
|
|
CREATE TABLE t2(c INT);
|
|
|
|
|
|
|
|
--error ER_WRONG_STRING_LENGTH
|
2013-11-03 16:31:52 +01:00
|
|
|
CREATE DEFINER=longer_than_80_456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789@localhost
|
2006-08-23 19:31:00 +02:00
|
|
|
TRIGGER t1_bi BEFORE INSERT ON t1 FOR EACH ROW SET @a = 1;
|
|
|
|
|
|
|
|
--error ER_WRONG_STRING_LENGTH
|
|
|
|
CREATE DEFINER=some_user_name@1234567890abcdefghij1234567890abcdefghij1234567890abcdefghijQWERTY
|
|
|
|
TRIGGER t2_bi BEFORE INSERT ON t2 FOR EACH ROW SET @a = 2;
|
|
|
|
|
|
|
|
# Cleanup.
|
|
|
|
|
|
|
|
DROP TABLE t1;
|
|
|
|
DROP TABLE t2;
|
|
|
|
|
2006-10-19 20:39:51 +02:00
|
|
|
#
|
|
|
|
# Bug#20028 Function with select return no data
|
|
|
|
#
|
|
|
|
|
|
|
|
--disable_warnings
|
|
|
|
drop table if exists t1;
|
|
|
|
drop table if exists t2;
|
|
|
|
drop table if exists t3;
|
|
|
|
drop table if exists t4;
|
|
|
|
--enable_warnings
|
|
|
|
|
|
|
|
SET @save_sql_mode=@@sql_mode;
|
|
|
|
|
|
|
|
delimiter |;
|
|
|
|
SET sql_mode='TRADITIONAL'|
|
|
|
|
create table t1 (id int(10) not null primary key, v int(10) )|
|
|
|
|
create table t2 (id int(10) not null primary key, v int(10) )|
|
|
|
|
create table t3 (id int(10) not null primary key, v int(10) )|
|
|
|
|
create table t4 (c int)|
|
|
|
|
|
|
|
|
create trigger t4_bi before insert on t4 for each row set @t4_bi_called:=1|
|
|
|
|
create trigger t4_bu before update on t4 for each row set @t4_bu_called:=1|
|
|
|
|
|
|
|
|
insert into t1 values(10, 10)|
|
|
|
|
set @a:=1/0|
|
|
|
|
select 1/0 from t1|
|
|
|
|
|
|
|
|
create trigger t1_bi before insert on t1 for each row set @a:=1/0|
|
|
|
|
|
|
|
|
insert into t1 values(20, 20)|
|
|
|
|
|
|
|
|
drop trigger t1_bi|
|
|
|
|
create trigger t1_bi before insert on t1 for each row
|
|
|
|
begin
|
|
|
|
insert into t2 values (new.id, new.v);
|
|
|
|
update t2 set v=v+1 where id= new.id;
|
|
|
|
replace t3 values (new.id, 0);
|
|
|
|
update t2, t3 set t2.v=new.v, t3.v=new.v where t2.id=t3.id;
|
|
|
|
create temporary table t5 select * from t1;
|
|
|
|
delete from t5;
|
|
|
|
insert into t5 select * from t1;
|
|
|
|
insert into t4 values (0);
|
|
|
|
set @check= (select count(*) from t5);
|
|
|
|
update t4 set c= @check;
|
|
|
|
drop temporary table t5;
|
|
|
|
|
|
|
|
set @a:=1/0;
|
|
|
|
end|
|
|
|
|
|
|
|
|
set @check=0, @t4_bi_called=0, @t4_bu_called=0|
|
|
|
|
insert into t1 values(30, 30)|
|
|
|
|
select @check, @t4_bi_called, @t4_bu_called|
|
|
|
|
|
|
|
|
delimiter ;|
|
|
|
|
|
|
|
|
SET @@sql_mode=@save_sql_mode;
|
|
|
|
|
|
|
|
drop table t1;
|
|
|
|
drop table t2;
|
|
|
|
drop table t3;
|
|
|
|
drop table t4;
|
2006-08-23 19:31:00 +02:00
|
|
|
|
2006-09-21 09:35:38 +02:00
|
|
|
#
|
|
|
|
# Bug#20670 "UPDATE using key and invoking trigger that modifies
|
|
|
|
# this key does not stop"
|
|
|
|
#
|
|
|
|
|
|
|
|
--disable_warnings
|
|
|
|
drop table if exists t1;
|
|
|
|
--enable_warnings
|
|
|
|
create table t1 (i int, j int key);
|
|
|
|
insert into t1 values (1,1), (2,2), (3,3);
|
|
|
|
create trigger t1_bu before update on t1 for each row
|
|
|
|
set new.j = new.j + 10;
|
|
|
|
# This should not work indefinitely and should cause
|
|
|
|
# expected result
|
|
|
|
update t1 set i= i+ 10 where j > 2;
|
|
|
|
select * from t1;
|
|
|
|
drop table t1;
|
|
|
|
|
2006-11-21 09:11:43 +01:00
|
|
|
#
|
|
|
|
# Bug#23556 TRUNCATE TABLE still maps to DELETE
|
|
|
|
#
|
|
|
|
CREATE TABLE t1 (a INT PRIMARY KEY);
|
|
|
|
CREATE TABLE t2 (a INT PRIMARY KEY);
|
|
|
|
INSERT INTO t1 VALUES (1),(2),(3),(4),(5),(6),(7),(8);
|
|
|
|
|
|
|
|
CREATE TRIGGER trg_t1 BEFORE DELETE on t1 FOR EACH ROW
|
|
|
|
INSERT INTO t2 VALUES (OLD.a);
|
|
|
|
|
|
|
|
FLUSH STATUS;
|
|
|
|
TRUNCATE t1;
|
|
|
|
SHOW STATUS LIKE 'handler_delete';
|
|
|
|
SELECT COUNT(*) FROM t2;
|
|
|
|
|
|
|
|
INSERT INTO t1 VALUES (1),(2),(3),(4),(5),(6),(7),(8);
|
|
|
|
DELETE FROM t2;
|
|
|
|
|
|
|
|
FLUSH STATUS;
|
|
|
|
DELETE FROM t1;
|
|
|
|
SHOW STATUS LIKE 'handler_delete';
|
|
|
|
SELECT COUNT(*) FROM t2;
|
|
|
|
|
|
|
|
DROP TRIGGER trg_t1;
|
|
|
|
DROP TABLE t1,t2;
|
2006-09-21 09:35:38 +02:00
|
|
|
|
2006-11-13 09:10:49 +01:00
|
|
|
#
|
|
|
|
# Bug #23651 "Server crashes when trigger which uses stored function
|
|
|
|
# invoked from different connections".
|
|
|
|
#
|
|
|
|
--disable_warnings
|
|
|
|
drop table if exists t1;
|
|
|
|
drop function if exists f1;
|
|
|
|
--enable_warnings
|
|
|
|
create table t1 (i int);
|
|
|
|
create function f1() returns int return 10;
|
|
|
|
create trigger t1_bi before insert on t1 for each row set @a:= f1() + 10;
|
|
|
|
insert into t1 values ();
|
|
|
|
select @a;
|
|
|
|
connection addconroot1;
|
|
|
|
insert into t1 values ();
|
|
|
|
select @a;
|
|
|
|
connection default;
|
|
|
|
drop table t1;
|
|
|
|
drop function f1;
|
|
|
|
|
Bug#23703 (DROP TRIGGER needs an IF EXISTS)
This change set implements the DROP TRIGGER IF EXISTS functionality.
This fix is considered a bug and not a feature, because without it,
there is no known method to write a database creation script that can create
a trigger without failing, when executed on a database that may or may not
contain already a trigger of the same name.
Implementing this functionality closes an orthogonality gap between triggers
and stored procedures / stored functions (which do support the DROP IF
EXISTS syntax).
In sql_trigger.cc, in mysql_create_or_drop_trigger,
the code has been reordered to:
- perform the tests that do not depend on the file system (access()),
- get the locks (wait_if_global_read_lock, LOCK_open)
- call access()
- perform the operation
- write to the binlog
- unlock (LOCK_open, start_waiting_global_read_lock)
This is to ensure that all the code that depends on the presence of the
trigger file is executed in the same critical section,
and prevents race conditions similar to the case fixed by Bug 14262 :
- thread 1 executes DROP TRIGGER IF EXISTS, access() returns a failure
- thread 2 executes CREATE TRIGGER
- thread 2 logs CREATE TRIGGER
- thread 1 logs DROP TRIGGER IF EXISTS
The patch itself is based on code contributed by the MySQL community,
under the terms of the Contributor License Agreement (See Bug 18161).
mysql-test/r/rpl_trigger.result:
DROP TRIGGER IF EXISTS
mysql-test/r/trigger.result:
DROP TRIGGER IF EXISTS
mysql-test/t/rpl_trigger.test:
DROP TRIGGER IF EXISTS
mysql-test/t/trigger.test:
DROP TRIGGER IF EXISTS
sql/sql_trigger.cc:
DROP TRIGGER IF EXISTS
sql/sql_yacc.yy:
DROP TRIGGER IF EXISTS
2006-11-13 23:40:22 +01:00
|
|
|
#
|
|
|
|
# Bug#23703: DROP TRIGGER needs an IF EXISTS
|
|
|
|
#
|
|
|
|
|
|
|
|
--disable_warnings
|
|
|
|
drop table if exists t1;
|
|
|
|
--enable_warnings
|
|
|
|
|
|
|
|
create table t1(a int, b varchar(50));
|
|
|
|
|
|
|
|
-- error ER_TRG_DOES_NOT_EXIST
|
|
|
|
drop trigger not_a_trigger;
|
|
|
|
|
|
|
|
drop trigger if exists not_a_trigger;
|
|
|
|
|
|
|
|
create trigger t1_bi before insert on t1
|
|
|
|
for each row set NEW.b := "In trigger t1_bi";
|
|
|
|
|
|
|
|
insert into t1 values (1, "a");
|
|
|
|
drop trigger if exists t1_bi;
|
|
|
|
insert into t1 values (2, "b");
|
|
|
|
drop trigger if exists t1_bi;
|
|
|
|
insert into t1 values (3, "c");
|
|
|
|
|
|
|
|
select * from t1;
|
|
|
|
|
|
|
|
drop table t1;
|
|
|
|
|
2007-01-12 22:43:25 +01:00
|
|
|
#
|
|
|
|
# Bug#25398: crash when a trigger contains a SELECT with
|
|
|
|
# trigger fields in the select list under DISTINCT
|
|
|
|
#
|
|
|
|
|
|
|
|
CREATE TABLE t1 (
|
|
|
|
id int NOT NULL DEFAULT '0',
|
|
|
|
a varchar(10) NOT NULL,
|
|
|
|
b varchar(10),
|
|
|
|
c varchar(10),
|
|
|
|
d timestamp NOT NULL,
|
|
|
|
PRIMARY KEY (id, a)
|
|
|
|
);
|
|
|
|
|
|
|
|
CREATE TABLE t2 (
|
|
|
|
fubar_id int unsigned NOT NULL DEFAULT '0',
|
|
|
|
last_change_time datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
|
|
|
|
PRIMARY KEY (fubar_id)
|
|
|
|
);
|
|
|
|
|
|
|
|
DELIMITER |;
|
|
|
|
|
|
|
|
CREATE TRIGGER fubar_change
|
|
|
|
AFTER UPDATE ON t1
|
|
|
|
FOR EACH ROW
|
|
|
|
BEGIN
|
|
|
|
INSERT INTO t2 (fubar_id, last_change_time)
|
|
|
|
SELECT DISTINCT NEW.id AS fubar_id, NOW() AS last_change_time
|
|
|
|
FROM t1 WHERE (id = NEW.id) AND (OLD.c != NEW.c)
|
|
|
|
ON DUPLICATE KEY UPDATE
|
|
|
|
last_change_time =
|
|
|
|
IF((fubar_id = NEW.id)AND(OLD.c != NEW.c),NOW(),last_change_time);
|
|
|
|
END
|
|
|
|
|
|
|
|
|
|
|
|
|
DELIMITER ;|
|
|
|
|
|
|
|
|
INSERT INTO t1 (id,a, b,c,d) VALUES
|
|
|
|
(1,'a','b','c',now()),(2,'a','b','c',now());
|
|
|
|
|
|
|
|
UPDATE t1 SET c='Bang!' WHERE id=1;
|
|
|
|
|
|
|
|
SELECT fubar_id FROM t2;
|
|
|
|
|
|
|
|
DROP TABLE t1,t2;
|
|
|
|
|
2007-03-06 21:46:33 +01:00
|
|
|
#
|
|
|
|
# Bug#21285 (Incorrect message error deleting records in a table with a
|
|
|
|
# trigger for inserting)
|
|
|
|
#
|
|
|
|
|
|
|
|
--disable_warnings
|
|
|
|
DROP TABLE IF EXISTS bug21825_A;
|
|
|
|
DROP TABLE IF EXISTS bug21825_B;
|
|
|
|
--enable_warnings
|
|
|
|
|
|
|
|
CREATE TABLE bug21825_A (id int(10));
|
|
|
|
CREATE TABLE bug21825_B (id int(10));
|
|
|
|
|
|
|
|
delimiter //;
|
|
|
|
|
|
|
|
CREATE TRIGGER trgA AFTER INSERT ON bug21825_A
|
|
|
|
FOR EACH ROW
|
|
|
|
BEGIN
|
|
|
|
INSERT INTO bug21825_B (id) values (1);
|
|
|
|
END//
|
|
|
|
delimiter ;//
|
|
|
|
|
|
|
|
INSERT INTO bug21825_A (id) VALUES (10);
|
|
|
|
INSERT INTO bug21825_A (id) VALUES (20);
|
|
|
|
|
|
|
|
DROP TABLE bug21825_B;
|
|
|
|
|
|
|
|
# Must pass, the missing table in the insert trigger should not matter.
|
|
|
|
DELETE FROM bug21825_A WHERE id = 20;
|
|
|
|
|
|
|
|
DROP TABLE bug21825_A;
|
|
|
|
|
|
|
|
#
|
|
|
|
# Bug#22580 (DROP TABLE in nested stored procedure causes strange dependancy
|
|
|
|
# error)
|
|
|
|
#
|
|
|
|
|
|
|
|
--disable_warnings
|
|
|
|
DROP TABLE IF EXISTS bug22580_t1;
|
|
|
|
DROP PROCEDURE IF EXISTS bug22580_proc_1;
|
|
|
|
DROP PROCEDURE IF EXISTS bug22580_proc_2;
|
|
|
|
--enable_warnings
|
|
|
|
|
|
|
|
CREATE TABLE bug22580_t1 (a INT, b INT);
|
|
|
|
|
|
|
|
DELIMITER ||;
|
|
|
|
|
|
|
|
CREATE PROCEDURE bug22580_proc_2()
|
|
|
|
BEGIN
|
|
|
|
DROP TABLE IF EXISTS bug22580_tmp;
|
|
|
|
CREATE TEMPORARY TABLE bug22580_tmp (a INT);
|
|
|
|
DROP TABLE bug22580_tmp;
|
|
|
|
END||
|
|
|
|
|
|
|
|
CREATE PROCEDURE bug22580_proc_1()
|
|
|
|
BEGIN
|
|
|
|
CALL bug22580_proc_2();
|
|
|
|
END||
|
|
|
|
|
|
|
|
CREATE TRIGGER t1bu BEFORE UPDATE ON bug22580_t1
|
|
|
|
FOR EACH ROW
|
|
|
|
BEGIN
|
|
|
|
CALL bug22580_proc_1();
|
|
|
|
END||
|
|
|
|
|
|
|
|
DELIMITER ;||
|
|
|
|
|
|
|
|
# Must pass, the actions of the update trigger should not matter
|
|
|
|
INSERT INTO bug22580_t1 VALUES (1,1);
|
|
|
|
|
|
|
|
DROP TABLE bug22580_t1;
|
|
|
|
DROP PROCEDURE bug22580_proc_1;
|
|
|
|
DROP PROCEDURE bug22580_proc_2;
|
|
|
|
|
2007-03-16 15:23:26 +01:00
|
|
|
#
|
2007-03-19 22:46:19 +01:00
|
|
|
# Bug#27006: AFTER UPDATE triggers not fired with INSERT ... ON DUPLICATE
|
2007-03-16 15:23:26 +01:00
|
|
|
#
|
|
|
|
--disable_warnings
|
|
|
|
DROP TRIGGER IF EXISTS trg27006_a_update;
|
|
|
|
DROP TRIGGER IF EXISTS trg27006_a_insert;
|
|
|
|
--enable_warnings
|
|
|
|
|
|
|
|
CREATE TABLE t1 (
|
|
|
|
`id` int(10) unsigned NOT NULL auto_increment,
|
|
|
|
`val` varchar(10) NOT NULL,
|
|
|
|
PRIMARY KEY (`id`)
|
|
|
|
);
|
|
|
|
CREATE TABLE t2 like t1;
|
|
|
|
DELIMITER |;
|
|
|
|
|
|
|
|
CREATE TRIGGER trg27006_a_insert AFTER INSERT ON t1 FOR EACH ROW
|
|
|
|
BEGIN
|
|
|
|
insert into t2 values (NULL,new.val);
|
|
|
|
END |
|
|
|
|
CREATE TRIGGER trg27006_a_update AFTER UPDATE ON t1 FOR EACH ROW
|
|
|
|
BEGIN
|
|
|
|
insert into t2 values (NULL,new.val);
|
|
|
|
END |
|
|
|
|
DELIMITER ;|
|
|
|
|
|
|
|
|
INSERT INTO t1(val) VALUES ('test1'),('test2');
|
|
|
|
SELECT * FROM t1;
|
|
|
|
SELECT * FROM t2;
|
|
|
|
INSERT INTO t1 VALUES (2,'test2') ON DUPLICATE KEY UPDATE val=VALUES(val);
|
2007-03-19 22:46:19 +01:00
|
|
|
INSERT INTO t1 VALUES (2,'test3') ON DUPLICATE KEY UPDATE val=VALUES(val);
|
|
|
|
INSERT INTO t1 VALUES (3,'test4') ON DUPLICATE KEY UPDATE val=VALUES(val);
|
2007-03-16 15:23:26 +01:00
|
|
|
SELECT * FROM t1;
|
|
|
|
SELECT * FROM t2;
|
|
|
|
DROP TRIGGER trg27006_a_insert;
|
|
|
|
DROP TRIGGER trg27006_a_update;
|
|
|
|
drop table t1,t2;
|
|
|
|
|
2007-05-11 19:51:03 +02:00
|
|
|
#
|
|
|
|
# Bug #20903 "Crash when using CREATE TABLE .. SELECT and triggers"
|
|
|
|
#
|
|
|
|
|
|
|
|
--disable_warnings
|
|
|
|
drop table if exists t1, t2, t3;
|
|
|
|
--enable_warnings
|
|
|
|
create table t1 (i int);
|
|
|
|
create trigger t1_bi before insert on t1 for each row set new.i = 7;
|
|
|
|
create trigger t1_ai after insert on t1 for each row set @a := 7;
|
|
|
|
create table t2 (j int);
|
|
|
|
insert into t2 values (1), (2);
|
|
|
|
set @a:="";
|
2010-08-18 11:35:41 +02:00
|
|
|
insert into t1 select * from t2;
|
2007-05-11 19:51:03 +02:00
|
|
|
select * from t1;
|
|
|
|
select @a;
|
|
|
|
# Let us check that trigger that involves table also works ok.
|
|
|
|
drop trigger t1_bi;
|
|
|
|
drop trigger t1_ai;
|
|
|
|
create table t3 (isave int);
|
|
|
|
create trigger t1_bi before insert on t1 for each row insert into t3 values (new.i);
|
2010-08-18 11:35:41 +02:00
|
|
|
insert into t1 select * from t2;
|
2007-05-11 19:51:03 +02:00
|
|
|
select * from t1;
|
|
|
|
select * from t3;
|
|
|
|
drop table t1, t2, t3;
|
|
|
|
|
2007-06-12 13:35:36 +02:00
|
|
|
disconnect addconroot1;
|
|
|
|
disconnect addconroot2;
|
|
|
|
disconnect addconwithoutdb;
|
A fix and a test case for Bug#26141 mixing table types in trigger
causes full table lock on innodb table.
Also fixes Bug#28502 Triggers that update another innodb table
will block on X lock unnecessarily (duplciate).
Code review fixes.
Both bugs' synopses are misleading: InnoDB table is
not X locked. The statements, however, cannot proceed concurrently,
but this happens due to lock conflicts for tables used in triggers,
not for the InnoDB table.
If a user had an InnoDB table, and two triggers, AFTER UPDATE and
AFTER INSERT, competing for different resources (e.g. two distinct
MyISAM tables), then these two triggers would not be able to execute
concurrently. Moreover, INSERTS/UPDATES of the InnoDB table would
not be able to run concurrently.
The problem had other side-effects (see respective bug reports).
This behavior was a consequence of a shortcoming of the pre-locking
algorithm, which would not distinguish between different DML operations
(e.g. INSERT and DELETE) and pre-lock all the tables
that are used by any trigger defined on the subject table.
The idea of the fix is to extend the pre-locking algorithm to keep track,
for each table, what DML operation it is used for and not
load triggers that are known to never be fired.
mysql-test/r/trigger-trans.result:
Update results (Bug#26141)
mysql-test/r/trigger.result:
Update results (Bug#28502)
mysql-test/t/trigger-trans.test:
Add a test case for Bug#26141 mixing table types in trigger causes
full table lock on innodb table.
mysql-test/t/trigger.test:
Add a test case for Bug#28502 Triggers that update another innodb
table will block echo on X lock unnecessarily. Add more test
coverage for triggers.
sql/item.h:
enum trg_event_type is needed in table.h
sql/sp.cc:
Take into account table_list->trg_event_map when determining
what tables to pre-lock.
After this change, if we attempt to fire a
trigger for which we had not pre-locked any tables, error
'Table was not locked with LOCK TABLES' will be printed.
This, however, should never happen, provided the pre-locking
algorithm has no programming bugs.
Previously a trigger key in the sroutines hash was based on the name
of the table the trigger belongs to. This was possible because we would
always add to the pre-locking list all the triggers defined for a table when
handling this table.
Now the key is based on the name of the trigger, owing
to the fact that a trigger name must be unique in the database it
belongs to.
sql/sp_head.cc:
Generate sroutines hash key in init_spname(). This is a convenient
place since there we have all the necessary information and can
avoid an extra alloc.
Maintain and merge trg_event_map when adding and merging elements
of the pre-locking list.
sql/sp_head.h:
Add ,m_sroutines_key member, used when inserting the sphead for a
trigger into the cache of routines used by a statement.
Previously the key was based on the table name the trigger belonged
to, since for a given table we would add to the sroutines list
all the triggers defined on it.
sql/sql_lex.cc:
Introduce a new lex step: set_trg_event_type_for_tables().
It is called when we have finished parsing but before opening
and locking tables. Now this step is used to evaluate for each
TABLE_LIST instance which INSERT/UPDATE/DELETE operation, if any,
it is used in.
In future this method could be extended to aggregate other information
that is hard to aggregate during parsing.
sql/sql_lex.h:
Add declaration for set_trg_event_type_for_tables().
sql/sql_parse.cc:
Call set_trg_event_type_for_tables() after MYSQLparse(). Remove tabs.
sql/sql_prepare.cc:
Call set_trg_event_type_for_tables() after MYSQLparse().
sql/sql_trigger.cc:
Call set_trg_event_type_for_tables() after MYSQLparse().
sql/sql_trigger.h:
Remove an obsolete member.
sql/sql_view.cc:
Call set_trg_event_type_for_tables() after MYSQLparse().
sql/sql_yacc.yy:
Move assignment of sp_head::m_type before calling sp_head::init_spname(),
one is now used inside another.
sql/table.cc:
Implement TABLE_LIST::set_trg_event_map() - a method that calculates
wh triggers may be fired on this table when executing a statement.
sql/table.h:
Add missing declarations.
Move declaration of trg_event_type from item.h (it will be needed for
trg_event_map bitmap when we start using Bitmap template instead
of uint8).
2007-07-12 20:26:41 +02:00
|
|
|
--echo
|
|
|
|
--echo Bug#28502 Triggers that update another innodb table will block
|
|
|
|
--echo on X lock unnecessarily
|
|
|
|
--echo
|
|
|
|
--echo Ensure we do not open and lock tables for triggers we do not fire.
|
|
|
|
--echo
|
|
|
|
--disable_warnings
|
|
|
|
drop table if exists t1, t2;
|
|
|
|
drop trigger if exists trg_bug28502_au;
|
|
|
|
--enable_warnings
|
|
|
|
|
|
|
|
create table t1 (id int, count int);
|
|
|
|
create table t2 (id int);
|
|
|
|
delimiter |;
|
|
|
|
|
|
|
|
create trigger trg_bug28502_au before update on t2
|
|
|
|
for each row
|
|
|
|
begin
|
|
|
|
if (new.id is not null) then
|
|
|
|
update t1 set count= count + 1 where id = old.id;
|
|
|
|
end if;
|
|
|
|
end|
|
|
|
|
|
|
|
|
delimiter ;|
|
|
|
|
insert into t1 (id, count) values (1, 0);
|
|
|
|
|
|
|
|
lock table t1 write;
|
|
|
|
|
|
|
|
--connect (connection_insert, localhost, root, , test, , )
|
|
|
|
connection connection_insert;
|
|
|
|
# Is expected to pass.
|
|
|
|
insert into t2 set id=1;
|
|
|
|
connection default;
|
|
|
|
unlock tables;
|
|
|
|
update t2 set id=1 where id=1;
|
|
|
|
select * from t1;
|
|
|
|
select * from t2;
|
|
|
|
# Will drop the trigger
|
|
|
|
drop table t1, t2;
|
|
|
|
disconnect connection_insert;
|
|
|
|
--echo
|
|
|
|
--echo Additionally, provide test coverage for triggers and
|
|
|
|
--echo all MySQL data changing commands.
|
|
|
|
--echo
|
|
|
|
--disable_warnings
|
|
|
|
drop table if exists t1, t2, t1_op_log;
|
|
|
|
drop view if exists v1;
|
|
|
|
drop trigger if exists trg_bug28502_bi;
|
|
|
|
drop trigger if exists trg_bug28502_ai;
|
|
|
|
drop trigger if exists trg_bug28502_bu;
|
|
|
|
drop trigger if exists trg_bug28502_au;
|
|
|
|
drop trigger if exists trg_bug28502_bd;
|
|
|
|
drop trigger if exists trg_bug28502_ad;
|
|
|
|
--enable_warnings
|
|
|
|
create table t1 (id int primary key auto_increment, operation varchar(255));
|
|
|
|
create table t2 (id int primary key);
|
|
|
|
create table t1_op_log(operation varchar(255));
|
|
|
|
create view v1 as select * from t1;
|
|
|
|
create trigger trg_bug28502_bi before insert on t1
|
|
|
|
for each row
|
|
|
|
insert into t1_op_log (operation)
|
|
|
|
values (concat("Before INSERT, new=", new.operation));
|
|
|
|
|
|
|
|
create trigger trg_bug28502_ai after insert on t1
|
|
|
|
for each row
|
|
|
|
insert into t1_op_log (operation)
|
|
|
|
values (concat("After INSERT, new=", new.operation));
|
|
|
|
|
|
|
|
create trigger trg_bug28502_bu before update on t1
|
|
|
|
for each row
|
|
|
|
insert into t1_op_log (operation)
|
|
|
|
values (concat("Before UPDATE, new=", new.operation,
|
|
|
|
", old=", old.operation));
|
|
|
|
|
|
|
|
create trigger trg_bug28502_au after update on t1
|
|
|
|
for each row
|
|
|
|
insert into t1_op_log (operation)
|
|
|
|
values (concat("After UPDATE, new=", new.operation,
|
|
|
|
", old=", old.operation));
|
|
|
|
|
|
|
|
create trigger trg_bug28502_bd before delete on t1
|
|
|
|
for each row
|
|
|
|
insert into t1_op_log (operation)
|
|
|
|
values (concat("Before DELETE, old=", old.operation));
|
|
|
|
|
|
|
|
create trigger trg_bug28502_ad after delete on t1
|
|
|
|
for each row
|
|
|
|
insert into t1_op_log (operation)
|
|
|
|
values (concat("After DELETE, old=", old.operation));
|
|
|
|
|
|
|
|
insert into t1 (operation) values ("INSERT");
|
|
|
|
|
|
|
|
set @id=last_insert_id();
|
|
|
|
|
|
|
|
select * from t1;
|
|
|
|
select * from t1_op_log;
|
|
|
|
truncate t1_op_log;
|
|
|
|
|
|
|
|
update t1 set operation="UPDATE" where id=@id;
|
|
|
|
|
|
|
|
select * from t1;
|
|
|
|
select * from t1_op_log;
|
|
|
|
truncate t1_op_log;
|
|
|
|
|
|
|
|
delete from t1 where id=@id;
|
|
|
|
|
|
|
|
select * from t1;
|
|
|
|
select * from t1_op_log;
|
|
|
|
truncate t1;
|
|
|
|
truncate t1_op_log;
|
|
|
|
|
|
|
|
insert into t1 (id, operation) values
|
|
|
|
(NULL, "INSERT ON DUPLICATE KEY UPDATE, inserting a new key")
|
|
|
|
on duplicate key update id=NULL, operation="Should never happen";
|
|
|
|
|
|
|
|
set @id=last_insert_id();
|
|
|
|
|
|
|
|
select * from t1;
|
|
|
|
select * from t1_op_log;
|
|
|
|
truncate t1_op_log;
|
|
|
|
|
|
|
|
insert into t1 (id, operation) values
|
|
|
|
(@id, "INSERT ON DUPLICATE KEY UPDATE, the key value is the same")
|
|
|
|
on duplicate key update id=NULL,
|
|
|
|
operation="INSERT ON DUPLICATE KEY UPDATE, updating the duplicate";
|
|
|
|
|
|
|
|
select * from t1;
|
|
|
|
select * from t1_op_log;
|
|
|
|
truncate t1;
|
|
|
|
truncate t1_op_log;
|
|
|
|
|
|
|
|
replace into t1 values (NULL, "REPLACE, inserting a new key");
|
|
|
|
|
|
|
|
set @id=last_insert_id();
|
|
|
|
|
|
|
|
select * from t1;
|
|
|
|
select * from t1_op_log;
|
|
|
|
truncate t1_op_log;
|
|
|
|
|
|
|
|
replace into t1 values (@id, "REPLACE, deleting the duplicate");
|
|
|
|
|
|
|
|
select * from t1;
|
|
|
|
select * from t1_op_log;
|
|
|
|
truncate t1;
|
|
|
|
truncate t1_op_log;
|
|
|
|
|
2010-08-18 11:35:41 +02:00
|
|
|
insert into t1
|
A fix and a test case for Bug#26141 mixing table types in trigger
causes full table lock on innodb table.
Also fixes Bug#28502 Triggers that update another innodb table
will block on X lock unnecessarily (duplciate).
Code review fixes.
Both bugs' synopses are misleading: InnoDB table is
not X locked. The statements, however, cannot proceed concurrently,
but this happens due to lock conflicts for tables used in triggers,
not for the InnoDB table.
If a user had an InnoDB table, and two triggers, AFTER UPDATE and
AFTER INSERT, competing for different resources (e.g. two distinct
MyISAM tables), then these two triggers would not be able to execute
concurrently. Moreover, INSERTS/UPDATES of the InnoDB table would
not be able to run concurrently.
The problem had other side-effects (see respective bug reports).
This behavior was a consequence of a shortcoming of the pre-locking
algorithm, which would not distinguish between different DML operations
(e.g. INSERT and DELETE) and pre-lock all the tables
that are used by any trigger defined on the subject table.
The idea of the fix is to extend the pre-locking algorithm to keep track,
for each table, what DML operation it is used for and not
load triggers that are known to never be fired.
mysql-test/r/trigger-trans.result:
Update results (Bug#26141)
mysql-test/r/trigger.result:
Update results (Bug#28502)
mysql-test/t/trigger-trans.test:
Add a test case for Bug#26141 mixing table types in trigger causes
full table lock on innodb table.
mysql-test/t/trigger.test:
Add a test case for Bug#28502 Triggers that update another innodb
table will block echo on X lock unnecessarily. Add more test
coverage for triggers.
sql/item.h:
enum trg_event_type is needed in table.h
sql/sp.cc:
Take into account table_list->trg_event_map when determining
what tables to pre-lock.
After this change, if we attempt to fire a
trigger for which we had not pre-locked any tables, error
'Table was not locked with LOCK TABLES' will be printed.
This, however, should never happen, provided the pre-locking
algorithm has no programming bugs.
Previously a trigger key in the sroutines hash was based on the name
of the table the trigger belongs to. This was possible because we would
always add to the pre-locking list all the triggers defined for a table when
handling this table.
Now the key is based on the name of the trigger, owing
to the fact that a trigger name must be unique in the database it
belongs to.
sql/sp_head.cc:
Generate sroutines hash key in init_spname(). This is a convenient
place since there we have all the necessary information and can
avoid an extra alloc.
Maintain and merge trg_event_map when adding and merging elements
of the pre-locking list.
sql/sp_head.h:
Add ,m_sroutines_key member, used when inserting the sphead for a
trigger into the cache of routines used by a statement.
Previously the key was based on the table name the trigger belonged
to, since for a given table we would add to the sroutines list
all the triggers defined on it.
sql/sql_lex.cc:
Introduce a new lex step: set_trg_event_type_for_tables().
It is called when we have finished parsing but before opening
and locking tables. Now this step is used to evaluate for each
TABLE_LIST instance which INSERT/UPDATE/DELETE operation, if any,
it is used in.
In future this method could be extended to aggregate other information
that is hard to aggregate during parsing.
sql/sql_lex.h:
Add declaration for set_trg_event_type_for_tables().
sql/sql_parse.cc:
Call set_trg_event_type_for_tables() after MYSQLparse(). Remove tabs.
sql/sql_prepare.cc:
Call set_trg_event_type_for_tables() after MYSQLparse().
sql/sql_trigger.cc:
Call set_trg_event_type_for_tables() after MYSQLparse().
sql/sql_trigger.h:
Remove an obsolete member.
sql/sql_view.cc:
Call set_trg_event_type_for_tables() after MYSQLparse().
sql/sql_yacc.yy:
Move assignment of sp_head::m_type before calling sp_head::init_spname(),
one is now used inside another.
sql/table.cc:
Implement TABLE_LIST::set_trg_event_map() - a method that calculates
wh triggers may be fired on this table when executing a statement.
sql/table.h:
Add missing declarations.
Move declaration of trg_event_type from item.h (it will be needed for
trg_event_map bitmap when we start using Bitmap template instead
of uint8).
2007-07-12 20:26:41 +02:00
|
|
|
select NULL, "CREATE TABLE ... SELECT, inserting a new key";
|
|
|
|
|
|
|
|
set @id=last_insert_id();
|
|
|
|
|
|
|
|
select * from t1;
|
|
|
|
select * from t1_op_log;
|
|
|
|
truncate t1_op_log;
|
|
|
|
|
2010-08-18 11:35:41 +02:00
|
|
|
replace into t1
|
A fix and a test case for Bug#26141 mixing table types in trigger
causes full table lock on innodb table.
Also fixes Bug#28502 Triggers that update another innodb table
will block on X lock unnecessarily (duplciate).
Code review fixes.
Both bugs' synopses are misleading: InnoDB table is
not X locked. The statements, however, cannot proceed concurrently,
but this happens due to lock conflicts for tables used in triggers,
not for the InnoDB table.
If a user had an InnoDB table, and two triggers, AFTER UPDATE and
AFTER INSERT, competing for different resources (e.g. two distinct
MyISAM tables), then these two triggers would not be able to execute
concurrently. Moreover, INSERTS/UPDATES of the InnoDB table would
not be able to run concurrently.
The problem had other side-effects (see respective bug reports).
This behavior was a consequence of a shortcoming of the pre-locking
algorithm, which would not distinguish between different DML operations
(e.g. INSERT and DELETE) and pre-lock all the tables
that are used by any trigger defined on the subject table.
The idea of the fix is to extend the pre-locking algorithm to keep track,
for each table, what DML operation it is used for and not
load triggers that are known to never be fired.
mysql-test/r/trigger-trans.result:
Update results (Bug#26141)
mysql-test/r/trigger.result:
Update results (Bug#28502)
mysql-test/t/trigger-trans.test:
Add a test case for Bug#26141 mixing table types in trigger causes
full table lock on innodb table.
mysql-test/t/trigger.test:
Add a test case for Bug#28502 Triggers that update another innodb
table will block echo on X lock unnecessarily. Add more test
coverage for triggers.
sql/item.h:
enum trg_event_type is needed in table.h
sql/sp.cc:
Take into account table_list->trg_event_map when determining
what tables to pre-lock.
After this change, if we attempt to fire a
trigger for which we had not pre-locked any tables, error
'Table was not locked with LOCK TABLES' will be printed.
This, however, should never happen, provided the pre-locking
algorithm has no programming bugs.
Previously a trigger key in the sroutines hash was based on the name
of the table the trigger belongs to. This was possible because we would
always add to the pre-locking list all the triggers defined for a table when
handling this table.
Now the key is based on the name of the trigger, owing
to the fact that a trigger name must be unique in the database it
belongs to.
sql/sp_head.cc:
Generate sroutines hash key in init_spname(). This is a convenient
place since there we have all the necessary information and can
avoid an extra alloc.
Maintain and merge trg_event_map when adding and merging elements
of the pre-locking list.
sql/sp_head.h:
Add ,m_sroutines_key member, used when inserting the sphead for a
trigger into the cache of routines used by a statement.
Previously the key was based on the table name the trigger belonged
to, since for a given table we would add to the sroutines list
all the triggers defined on it.
sql/sql_lex.cc:
Introduce a new lex step: set_trg_event_type_for_tables().
It is called when we have finished parsing but before opening
and locking tables. Now this step is used to evaluate for each
TABLE_LIST instance which INSERT/UPDATE/DELETE operation, if any,
it is used in.
In future this method could be extended to aggregate other information
that is hard to aggregate during parsing.
sql/sql_lex.h:
Add declaration for set_trg_event_type_for_tables().
sql/sql_parse.cc:
Call set_trg_event_type_for_tables() after MYSQLparse(). Remove tabs.
sql/sql_prepare.cc:
Call set_trg_event_type_for_tables() after MYSQLparse().
sql/sql_trigger.cc:
Call set_trg_event_type_for_tables() after MYSQLparse().
sql/sql_trigger.h:
Remove an obsolete member.
sql/sql_view.cc:
Call set_trg_event_type_for_tables() after MYSQLparse().
sql/sql_yacc.yy:
Move assignment of sp_head::m_type before calling sp_head::init_spname(),
one is now used inside another.
sql/table.cc:
Implement TABLE_LIST::set_trg_event_map() - a method that calculates
wh triggers may be fired on this table when executing a statement.
sql/table.h:
Add missing declarations.
Move declaration of trg_event_type from item.h (it will be needed for
trg_event_map bitmap when we start using Bitmap template instead
of uint8).
2007-07-12 20:26:41 +02:00
|
|
|
select @id, "CREATE TABLE ... REPLACE SELECT, deleting a duplicate key";
|
|
|
|
|
|
|
|
select * from t1;
|
|
|
|
select * from t1_op_log;
|
|
|
|
truncate t1;
|
|
|
|
truncate t1_op_log;
|
|
|
|
|
|
|
|
insert into t1 (id, operation)
|
|
|
|
select NULL, "INSERT ... SELECT, inserting a new key";
|
|
|
|
|
|
|
|
set @id=last_insert_id();
|
|
|
|
|
|
|
|
select * from t1;
|
|
|
|
select * from t1_op_log;
|
|
|
|
truncate t1_op_log;
|
|
|
|
|
|
|
|
insert into t1 (id, operation)
|
|
|
|
select @id,
|
|
|
|
"INSERT ... SELECT ... ON DUPLICATE KEY UPDATE, updating a duplicate"
|
|
|
|
on duplicate key update id=NULL,
|
|
|
|
operation="INSERT ... SELECT ... ON DUPLICATE KEY UPDATE, updating a duplicate";
|
|
|
|
|
|
|
|
select * from t1;
|
|
|
|
select * from t1_op_log;
|
|
|
|
truncate t1;
|
|
|
|
truncate t1_op_log;
|
|
|
|
|
|
|
|
replace into t1 (id, operation)
|
|
|
|
select NULL, "REPLACE ... SELECT, inserting a new key";
|
|
|
|
|
|
|
|
set @id=last_insert_id();
|
|
|
|
|
|
|
|
select * from t1;
|
|
|
|
select * from t1_op_log;
|
|
|
|
truncate t1_op_log;
|
|
|
|
|
|
|
|
replace into t1 (id, operation)
|
|
|
|
select @id, "REPLACE ... SELECT, deleting a duplicate";
|
|
|
|
|
|
|
|
select * from t1;
|
|
|
|
select * from t1_op_log;
|
|
|
|
truncate t1;
|
|
|
|
truncate t1_op_log;
|
|
|
|
|
|
|
|
insert into t1 (id, operation) values (1, "INSERT for multi-DELETE");
|
|
|
|
insert into t2 (id) values (1);
|
2007-06-03 08:40:00 +02:00
|
|
|
|
A fix and a test case for Bug#26141 mixing table types in trigger
causes full table lock on innodb table.
Also fixes Bug#28502 Triggers that update another innodb table
will block on X lock unnecessarily (duplciate).
Code review fixes.
Both bugs' synopses are misleading: InnoDB table is
not X locked. The statements, however, cannot proceed concurrently,
but this happens due to lock conflicts for tables used in triggers,
not for the InnoDB table.
If a user had an InnoDB table, and two triggers, AFTER UPDATE and
AFTER INSERT, competing for different resources (e.g. two distinct
MyISAM tables), then these two triggers would not be able to execute
concurrently. Moreover, INSERTS/UPDATES of the InnoDB table would
not be able to run concurrently.
The problem had other side-effects (see respective bug reports).
This behavior was a consequence of a shortcoming of the pre-locking
algorithm, which would not distinguish between different DML operations
(e.g. INSERT and DELETE) and pre-lock all the tables
that are used by any trigger defined on the subject table.
The idea of the fix is to extend the pre-locking algorithm to keep track,
for each table, what DML operation it is used for and not
load triggers that are known to never be fired.
mysql-test/r/trigger-trans.result:
Update results (Bug#26141)
mysql-test/r/trigger.result:
Update results (Bug#28502)
mysql-test/t/trigger-trans.test:
Add a test case for Bug#26141 mixing table types in trigger causes
full table lock on innodb table.
mysql-test/t/trigger.test:
Add a test case for Bug#28502 Triggers that update another innodb
table will block echo on X lock unnecessarily. Add more test
coverage for triggers.
sql/item.h:
enum trg_event_type is needed in table.h
sql/sp.cc:
Take into account table_list->trg_event_map when determining
what tables to pre-lock.
After this change, if we attempt to fire a
trigger for which we had not pre-locked any tables, error
'Table was not locked with LOCK TABLES' will be printed.
This, however, should never happen, provided the pre-locking
algorithm has no programming bugs.
Previously a trigger key in the sroutines hash was based on the name
of the table the trigger belongs to. This was possible because we would
always add to the pre-locking list all the triggers defined for a table when
handling this table.
Now the key is based on the name of the trigger, owing
to the fact that a trigger name must be unique in the database it
belongs to.
sql/sp_head.cc:
Generate sroutines hash key in init_spname(). This is a convenient
place since there we have all the necessary information and can
avoid an extra alloc.
Maintain and merge trg_event_map when adding and merging elements
of the pre-locking list.
sql/sp_head.h:
Add ,m_sroutines_key member, used when inserting the sphead for a
trigger into the cache of routines used by a statement.
Previously the key was based on the table name the trigger belonged
to, since for a given table we would add to the sroutines list
all the triggers defined on it.
sql/sql_lex.cc:
Introduce a new lex step: set_trg_event_type_for_tables().
It is called when we have finished parsing but before opening
and locking tables. Now this step is used to evaluate for each
TABLE_LIST instance which INSERT/UPDATE/DELETE operation, if any,
it is used in.
In future this method could be extended to aggregate other information
that is hard to aggregate during parsing.
sql/sql_lex.h:
Add declaration for set_trg_event_type_for_tables().
sql/sql_parse.cc:
Call set_trg_event_type_for_tables() after MYSQLparse(). Remove tabs.
sql/sql_prepare.cc:
Call set_trg_event_type_for_tables() after MYSQLparse().
sql/sql_trigger.cc:
Call set_trg_event_type_for_tables() after MYSQLparse().
sql/sql_trigger.h:
Remove an obsolete member.
sql/sql_view.cc:
Call set_trg_event_type_for_tables() after MYSQLparse().
sql/sql_yacc.yy:
Move assignment of sp_head::m_type before calling sp_head::init_spname(),
one is now used inside another.
sql/table.cc:
Implement TABLE_LIST::set_trg_event_map() - a method that calculates
wh triggers may be fired on this table when executing a statement.
sql/table.h:
Add missing declarations.
Move declaration of trg_event_type from item.h (it will be needed for
trg_event_map bitmap when we start using Bitmap template instead
of uint8).
2007-07-12 20:26:41 +02:00
|
|
|
delete t1.*, t2.* from t1, t2 where t1.id=1;
|
|
|
|
|
|
|
|
select * from t1;
|
|
|
|
select * from t2;
|
|
|
|
select * from t1_op_log;
|
|
|
|
truncate t1;
|
|
|
|
truncate t2;
|
|
|
|
truncate t1_op_log;
|
|
|
|
|
|
|
|
insert into t1 (id, operation) values (1, "INSERT for multi-UPDATE");
|
|
|
|
insert into t2 (id) values (1);
|
|
|
|
update t1, t2 set t1.id=2, operation="multi-UPDATE" where t1.id=1;
|
|
|
|
update t1, t2
|
|
|
|
set t2.id=3, operation="multi-UPDATE, SET for t2, but the trigger is fired" where t1.id=2;
|
|
|
|
|
|
|
|
select * from t1;
|
|
|
|
select * from t2;
|
|
|
|
select * from t1_op_log;
|
|
|
|
truncate table t1;
|
|
|
|
truncate table t2;
|
|
|
|
truncate table t1_op_log;
|
|
|
|
|
|
|
|
--echo
|
|
|
|
--echo Now do the same but use a view instead of the base table.
|
|
|
|
--echo
|
|
|
|
|
|
|
|
insert into v1 (operation) values ("INSERT");
|
2007-06-03 08:40:00 +02:00
|
|
|
|
A fix and a test case for Bug#26141 mixing table types in trigger
causes full table lock on innodb table.
Also fixes Bug#28502 Triggers that update another innodb table
will block on X lock unnecessarily (duplciate).
Code review fixes.
Both bugs' synopses are misleading: InnoDB table is
not X locked. The statements, however, cannot proceed concurrently,
but this happens due to lock conflicts for tables used in triggers,
not for the InnoDB table.
If a user had an InnoDB table, and two triggers, AFTER UPDATE and
AFTER INSERT, competing for different resources (e.g. two distinct
MyISAM tables), then these two triggers would not be able to execute
concurrently. Moreover, INSERTS/UPDATES of the InnoDB table would
not be able to run concurrently.
The problem had other side-effects (see respective bug reports).
This behavior was a consequence of a shortcoming of the pre-locking
algorithm, which would not distinguish between different DML operations
(e.g. INSERT and DELETE) and pre-lock all the tables
that are used by any trigger defined on the subject table.
The idea of the fix is to extend the pre-locking algorithm to keep track,
for each table, what DML operation it is used for and not
load triggers that are known to never be fired.
mysql-test/r/trigger-trans.result:
Update results (Bug#26141)
mysql-test/r/trigger.result:
Update results (Bug#28502)
mysql-test/t/trigger-trans.test:
Add a test case for Bug#26141 mixing table types in trigger causes
full table lock on innodb table.
mysql-test/t/trigger.test:
Add a test case for Bug#28502 Triggers that update another innodb
table will block echo on X lock unnecessarily. Add more test
coverage for triggers.
sql/item.h:
enum trg_event_type is needed in table.h
sql/sp.cc:
Take into account table_list->trg_event_map when determining
what tables to pre-lock.
After this change, if we attempt to fire a
trigger for which we had not pre-locked any tables, error
'Table was not locked with LOCK TABLES' will be printed.
This, however, should never happen, provided the pre-locking
algorithm has no programming bugs.
Previously a trigger key in the sroutines hash was based on the name
of the table the trigger belongs to. This was possible because we would
always add to the pre-locking list all the triggers defined for a table when
handling this table.
Now the key is based on the name of the trigger, owing
to the fact that a trigger name must be unique in the database it
belongs to.
sql/sp_head.cc:
Generate sroutines hash key in init_spname(). This is a convenient
place since there we have all the necessary information and can
avoid an extra alloc.
Maintain and merge trg_event_map when adding and merging elements
of the pre-locking list.
sql/sp_head.h:
Add ,m_sroutines_key member, used when inserting the sphead for a
trigger into the cache of routines used by a statement.
Previously the key was based on the table name the trigger belonged
to, since for a given table we would add to the sroutines list
all the triggers defined on it.
sql/sql_lex.cc:
Introduce a new lex step: set_trg_event_type_for_tables().
It is called when we have finished parsing but before opening
and locking tables. Now this step is used to evaluate for each
TABLE_LIST instance which INSERT/UPDATE/DELETE operation, if any,
it is used in.
In future this method could be extended to aggregate other information
that is hard to aggregate during parsing.
sql/sql_lex.h:
Add declaration for set_trg_event_type_for_tables().
sql/sql_parse.cc:
Call set_trg_event_type_for_tables() after MYSQLparse(). Remove tabs.
sql/sql_prepare.cc:
Call set_trg_event_type_for_tables() after MYSQLparse().
sql/sql_trigger.cc:
Call set_trg_event_type_for_tables() after MYSQLparse().
sql/sql_trigger.h:
Remove an obsolete member.
sql/sql_view.cc:
Call set_trg_event_type_for_tables() after MYSQLparse().
sql/sql_yacc.yy:
Move assignment of sp_head::m_type before calling sp_head::init_spname(),
one is now used inside another.
sql/table.cc:
Implement TABLE_LIST::set_trg_event_map() - a method that calculates
wh triggers may be fired on this table when executing a statement.
sql/table.h:
Add missing declarations.
Move declaration of trg_event_type from item.h (it will be needed for
trg_event_map bitmap when we start using Bitmap template instead
of uint8).
2007-07-12 20:26:41 +02:00
|
|
|
set @id=last_insert_id();
|
|
|
|
|
|
|
|
select * from t1;
|
|
|
|
select * from t1_op_log;
|
|
|
|
truncate t1_op_log;
|
|
|
|
|
|
|
|
update v1 set operation="UPDATE" where id=@id;
|
|
|
|
|
|
|
|
select * from t1;
|
|
|
|
select * from t1_op_log;
|
|
|
|
truncate t1_op_log;
|
|
|
|
|
|
|
|
delete from v1 where id=@id;
|
|
|
|
|
|
|
|
select * from t1;
|
|
|
|
select * from t1_op_log;
|
|
|
|
truncate t1;
|
|
|
|
truncate t1_op_log;
|
|
|
|
|
|
|
|
insert into v1 (id, operation) values
|
|
|
|
(NULL, "INSERT ON DUPLICATE KEY UPDATE, inserting a new key")
|
|
|
|
on duplicate key update id=NULL, operation="Should never happen";
|
|
|
|
|
|
|
|
set @id=last_insert_id();
|
|
|
|
|
|
|
|
select * from t1;
|
|
|
|
select * from t1_op_log;
|
|
|
|
truncate t1_op_log;
|
|
|
|
|
|
|
|
insert into v1 (id, operation) values
|
|
|
|
(@id, "INSERT ON DUPLICATE KEY UPDATE, the key value is the same")
|
|
|
|
on duplicate key update id=NULL,
|
|
|
|
operation="INSERT ON DUPLICATE KEY UPDATE, updating the duplicate";
|
|
|
|
|
|
|
|
select * from t1;
|
|
|
|
select * from t1_op_log;
|
|
|
|
truncate t1;
|
|
|
|
truncate t1_op_log;
|
|
|
|
|
|
|
|
replace into v1 values (NULL, "REPLACE, inserting a new key");
|
|
|
|
|
|
|
|
set @id=last_insert_id();
|
|
|
|
|
|
|
|
select * from t1;
|
|
|
|
select * from t1_op_log;
|
|
|
|
truncate t1_op_log;
|
|
|
|
|
|
|
|
replace into v1 values (@id, "REPLACE, deleting the duplicate");
|
|
|
|
|
|
|
|
select * from t1;
|
|
|
|
select * from t1_op_log;
|
|
|
|
truncate t1;
|
|
|
|
truncate t1_op_log;
|
|
|
|
|
2010-08-18 11:35:41 +02:00
|
|
|
insert into v1
|
A fix and a test case for Bug#26141 mixing table types in trigger
causes full table lock on innodb table.
Also fixes Bug#28502 Triggers that update another innodb table
will block on X lock unnecessarily (duplciate).
Code review fixes.
Both bugs' synopses are misleading: InnoDB table is
not X locked. The statements, however, cannot proceed concurrently,
but this happens due to lock conflicts for tables used in triggers,
not for the InnoDB table.
If a user had an InnoDB table, and two triggers, AFTER UPDATE and
AFTER INSERT, competing for different resources (e.g. two distinct
MyISAM tables), then these two triggers would not be able to execute
concurrently. Moreover, INSERTS/UPDATES of the InnoDB table would
not be able to run concurrently.
The problem had other side-effects (see respective bug reports).
This behavior was a consequence of a shortcoming of the pre-locking
algorithm, which would not distinguish between different DML operations
(e.g. INSERT and DELETE) and pre-lock all the tables
that are used by any trigger defined on the subject table.
The idea of the fix is to extend the pre-locking algorithm to keep track,
for each table, what DML operation it is used for and not
load triggers that are known to never be fired.
mysql-test/r/trigger-trans.result:
Update results (Bug#26141)
mysql-test/r/trigger.result:
Update results (Bug#28502)
mysql-test/t/trigger-trans.test:
Add a test case for Bug#26141 mixing table types in trigger causes
full table lock on innodb table.
mysql-test/t/trigger.test:
Add a test case for Bug#28502 Triggers that update another innodb
table will block echo on X lock unnecessarily. Add more test
coverage for triggers.
sql/item.h:
enum trg_event_type is needed in table.h
sql/sp.cc:
Take into account table_list->trg_event_map when determining
what tables to pre-lock.
After this change, if we attempt to fire a
trigger for which we had not pre-locked any tables, error
'Table was not locked with LOCK TABLES' will be printed.
This, however, should never happen, provided the pre-locking
algorithm has no programming bugs.
Previously a trigger key in the sroutines hash was based on the name
of the table the trigger belongs to. This was possible because we would
always add to the pre-locking list all the triggers defined for a table when
handling this table.
Now the key is based on the name of the trigger, owing
to the fact that a trigger name must be unique in the database it
belongs to.
sql/sp_head.cc:
Generate sroutines hash key in init_spname(). This is a convenient
place since there we have all the necessary information and can
avoid an extra alloc.
Maintain and merge trg_event_map when adding and merging elements
of the pre-locking list.
sql/sp_head.h:
Add ,m_sroutines_key member, used when inserting the sphead for a
trigger into the cache of routines used by a statement.
Previously the key was based on the table name the trigger belonged
to, since for a given table we would add to the sroutines list
all the triggers defined on it.
sql/sql_lex.cc:
Introduce a new lex step: set_trg_event_type_for_tables().
It is called when we have finished parsing but before opening
and locking tables. Now this step is used to evaluate for each
TABLE_LIST instance which INSERT/UPDATE/DELETE operation, if any,
it is used in.
In future this method could be extended to aggregate other information
that is hard to aggregate during parsing.
sql/sql_lex.h:
Add declaration for set_trg_event_type_for_tables().
sql/sql_parse.cc:
Call set_trg_event_type_for_tables() after MYSQLparse(). Remove tabs.
sql/sql_prepare.cc:
Call set_trg_event_type_for_tables() after MYSQLparse().
sql/sql_trigger.cc:
Call set_trg_event_type_for_tables() after MYSQLparse().
sql/sql_trigger.h:
Remove an obsolete member.
sql/sql_view.cc:
Call set_trg_event_type_for_tables() after MYSQLparse().
sql/sql_yacc.yy:
Move assignment of sp_head::m_type before calling sp_head::init_spname(),
one is now used inside another.
sql/table.cc:
Implement TABLE_LIST::set_trg_event_map() - a method that calculates
wh triggers may be fired on this table when executing a statement.
sql/table.h:
Add missing declarations.
Move declaration of trg_event_type from item.h (it will be needed for
trg_event_map bitmap when we start using Bitmap template instead
of uint8).
2007-07-12 20:26:41 +02:00
|
|
|
select NULL, "CREATE TABLE ... SELECT, inserting a new key";
|
|
|
|
|
|
|
|
set @id=last_insert_id();
|
|
|
|
|
|
|
|
select * from t1;
|
|
|
|
select * from t1_op_log;
|
|
|
|
truncate t1_op_log;
|
|
|
|
|
2010-08-18 11:35:41 +02:00
|
|
|
replace into v1
|
A fix and a test case for Bug#26141 mixing table types in trigger
causes full table lock on innodb table.
Also fixes Bug#28502 Triggers that update another innodb table
will block on X lock unnecessarily (duplciate).
Code review fixes.
Both bugs' synopses are misleading: InnoDB table is
not X locked. The statements, however, cannot proceed concurrently,
but this happens due to lock conflicts for tables used in triggers,
not for the InnoDB table.
If a user had an InnoDB table, and two triggers, AFTER UPDATE and
AFTER INSERT, competing for different resources (e.g. two distinct
MyISAM tables), then these two triggers would not be able to execute
concurrently. Moreover, INSERTS/UPDATES of the InnoDB table would
not be able to run concurrently.
The problem had other side-effects (see respective bug reports).
This behavior was a consequence of a shortcoming of the pre-locking
algorithm, which would not distinguish between different DML operations
(e.g. INSERT and DELETE) and pre-lock all the tables
that are used by any trigger defined on the subject table.
The idea of the fix is to extend the pre-locking algorithm to keep track,
for each table, what DML operation it is used for and not
load triggers that are known to never be fired.
mysql-test/r/trigger-trans.result:
Update results (Bug#26141)
mysql-test/r/trigger.result:
Update results (Bug#28502)
mysql-test/t/trigger-trans.test:
Add a test case for Bug#26141 mixing table types in trigger causes
full table lock on innodb table.
mysql-test/t/trigger.test:
Add a test case for Bug#28502 Triggers that update another innodb
table will block echo on X lock unnecessarily. Add more test
coverage for triggers.
sql/item.h:
enum trg_event_type is needed in table.h
sql/sp.cc:
Take into account table_list->trg_event_map when determining
what tables to pre-lock.
After this change, if we attempt to fire a
trigger for which we had not pre-locked any tables, error
'Table was not locked with LOCK TABLES' will be printed.
This, however, should never happen, provided the pre-locking
algorithm has no programming bugs.
Previously a trigger key in the sroutines hash was based on the name
of the table the trigger belongs to. This was possible because we would
always add to the pre-locking list all the triggers defined for a table when
handling this table.
Now the key is based on the name of the trigger, owing
to the fact that a trigger name must be unique in the database it
belongs to.
sql/sp_head.cc:
Generate sroutines hash key in init_spname(). This is a convenient
place since there we have all the necessary information and can
avoid an extra alloc.
Maintain and merge trg_event_map when adding and merging elements
of the pre-locking list.
sql/sp_head.h:
Add ,m_sroutines_key member, used when inserting the sphead for a
trigger into the cache of routines used by a statement.
Previously the key was based on the table name the trigger belonged
to, since for a given table we would add to the sroutines list
all the triggers defined on it.
sql/sql_lex.cc:
Introduce a new lex step: set_trg_event_type_for_tables().
It is called when we have finished parsing but before opening
and locking tables. Now this step is used to evaluate for each
TABLE_LIST instance which INSERT/UPDATE/DELETE operation, if any,
it is used in.
In future this method could be extended to aggregate other information
that is hard to aggregate during parsing.
sql/sql_lex.h:
Add declaration for set_trg_event_type_for_tables().
sql/sql_parse.cc:
Call set_trg_event_type_for_tables() after MYSQLparse(). Remove tabs.
sql/sql_prepare.cc:
Call set_trg_event_type_for_tables() after MYSQLparse().
sql/sql_trigger.cc:
Call set_trg_event_type_for_tables() after MYSQLparse().
sql/sql_trigger.h:
Remove an obsolete member.
sql/sql_view.cc:
Call set_trg_event_type_for_tables() after MYSQLparse().
sql/sql_yacc.yy:
Move assignment of sp_head::m_type before calling sp_head::init_spname(),
one is now used inside another.
sql/table.cc:
Implement TABLE_LIST::set_trg_event_map() - a method that calculates
wh triggers may be fired on this table when executing a statement.
sql/table.h:
Add missing declarations.
Move declaration of trg_event_type from item.h (it will be needed for
trg_event_map bitmap when we start using Bitmap template instead
of uint8).
2007-07-12 20:26:41 +02:00
|
|
|
select @id, "CREATE TABLE ... REPLACE SELECT, deleting a duplicate key";
|
|
|
|
|
|
|
|
select * from t1;
|
|
|
|
select * from t1_op_log;
|
|
|
|
truncate t1;
|
|
|
|
truncate t1_op_log;
|
|
|
|
|
|
|
|
insert into v1 (id, operation)
|
|
|
|
select NULL, "INSERT ... SELECT, inserting a new key";
|
|
|
|
|
|
|
|
set @id=last_insert_id();
|
|
|
|
|
|
|
|
select * from t1;
|
|
|
|
select * from t1_op_log;
|
|
|
|
truncate t1_op_log;
|
|
|
|
|
|
|
|
insert into v1 (id, operation)
|
|
|
|
select @id,
|
|
|
|
"INSERT ... SELECT ... ON DUPLICATE KEY UPDATE, updating a duplicate"
|
|
|
|
on duplicate key update id=NULL,
|
|
|
|
operation="INSERT ... SELECT ... ON DUPLICATE KEY UPDATE, updating a duplicate";
|
|
|
|
|
|
|
|
select * from t1;
|
|
|
|
select * from t1_op_log;
|
|
|
|
truncate t1;
|
|
|
|
truncate t1_op_log;
|
|
|
|
|
|
|
|
replace into v1 (id, operation)
|
|
|
|
select NULL, "REPLACE ... SELECT, inserting a new key";
|
|
|
|
|
|
|
|
set @id=last_insert_id();
|
|
|
|
|
|
|
|
select * from t1;
|
|
|
|
select * from t1_op_log;
|
|
|
|
truncate t1_op_log;
|
|
|
|
|
|
|
|
replace into v1 (id, operation)
|
|
|
|
select @id, "REPLACE ... SELECT, deleting a duplicate";
|
|
|
|
|
|
|
|
select * from t1;
|
|
|
|
select * from t1_op_log;
|
|
|
|
truncate t1;
|
|
|
|
truncate t1_op_log;
|
|
|
|
|
|
|
|
insert into v1 (id, operation) values (1, "INSERT for multi-DELETE");
|
|
|
|
insert into t2 (id) values (1);
|
|
|
|
|
|
|
|
delete v1.*, t2.* from v1, t2 where v1.id=1;
|
|
|
|
|
|
|
|
select * from t1;
|
|
|
|
select * from t2;
|
|
|
|
select * from t1_op_log;
|
|
|
|
truncate t1;
|
|
|
|
truncate t2;
|
|
|
|
truncate t1_op_log;
|
|
|
|
|
|
|
|
insert into v1 (id, operation) values (1, "INSERT for multi-UPDATE");
|
|
|
|
insert into t2 (id) values (1);
|
|
|
|
update v1, t2 set v1.id=2, operation="multi-UPDATE" where v1.id=1;
|
|
|
|
update v1, t2
|
|
|
|
set t2.id=3, operation="multi-UPDATE, SET for t2, but the trigger is fired" where v1.id=2;
|
|
|
|
|
|
|
|
select * from t1;
|
|
|
|
select * from t2;
|
|
|
|
select * from t1_op_log;
|
|
|
|
|
|
|
|
drop view v1;
|
|
|
|
drop table t1, t2, t1_op_log;
|
|
|
|
|
|
|
|
#
|
|
|
|
# TODO: test LOAD DATA INFILE
|
2007-07-18 12:42:06 +02:00
|
|
|
#
|
|
|
|
--echo
|
|
|
|
--echo Bug#27248 Triggers: error if insert affects temporary table
|
|
|
|
--echo
|
|
|
|
--echo The bug was fixed by the fix for Bug#26141
|
|
|
|
--echo
|
|
|
|
--disable_warnings
|
|
|
|
drop table if exists t1;
|
|
|
|
drop temporary table if exists t2;
|
|
|
|
--enable_warnings
|
|
|
|
create table t1 (s1 int);
|
|
|
|
create temporary table t2 (s1 int);
|
|
|
|
create trigger t1_bi before insert on t1 for each row insert into t2 values (0);
|
|
|
|
create trigger t1_bd before delete on t1 for each row delete from t2;
|
|
|
|
insert into t1 values (0);
|
|
|
|
insert into t1 values (0);
|
|
|
|
select * from t1;
|
|
|
|
select * from t2;
|
|
|
|
delete from t1;
|
|
|
|
select * from t1;
|
|
|
|
select * from t2;
|
|
|
|
drop table t1;
|
|
|
|
drop temporary table t2;
|
2009-03-27 12:09:15 +01:00
|
|
|
|
|
|
|
--echo #------------------------------------------------------------------------
|
|
|
|
--echo # Bug#39953 Triggers are not working properly with multi table updates
|
|
|
|
--echo #------------------------------------------------------------------------
|
|
|
|
|
|
|
|
--disable_warnings
|
|
|
|
DROP TABLE IF EXISTS t1;
|
|
|
|
DROP TRIGGER IF EXISTS t_insert;
|
|
|
|
DROP TABLE IF EXISTS t2;
|
|
|
|
--enable_warnings
|
|
|
|
|
|
|
|
CREATE TABLE t1 (a int, date_insert timestamp, PRIMARY KEY (a));
|
|
|
|
INSERT INTO t1 (a) VALUES (2),(5);
|
|
|
|
CREATE TABLE t2 (a int, b int, PRIMARY KEY (a));
|
|
|
|
DELIMITER |;
|
|
|
|
CREATE TRIGGER t_insert AFTER INSERT ON t2 FOR EACH ROW BEGIN UPDATE t1,t2 SET
|
|
|
|
date_insert=NOW() WHERE t1.a=t2.b AND t2.a=NEW.a; END |
|
|
|
|
DELIMITER ;|
|
|
|
|
INSERT INTO t2 (a,b) VALUES (1,2);
|
|
|
|
|
|
|
|
DROP TRIGGER t_insert;
|
|
|
|
|
|
|
|
DELIMITER |;
|
|
|
|
CREATE TRIGGER t_insert AFTER INSERT ON t2 FOR EACH ROW BEGIN UPDATE t1,t2 SET
|
|
|
|
date_insert=NOW(),b=b+1 WHERE t1.a=t2.b AND t2.a=NEW.a; END |
|
|
|
|
DELIMITER ;|
|
|
|
|
--error ER_CANT_UPDATE_USED_TABLE_IN_SF_OR_TRG
|
|
|
|
INSERT INTO t2 (a,b) VALUES (3,5);
|
|
|
|
|
|
|
|
DROP TABLE t1;
|
|
|
|
DROP TRIGGER t_insert;
|
|
|
|
DROP TABLE t2;
|
|
|
|
|
2019-04-29 12:32:36 +02:00
|
|
|
--echo # End of 5.0 tests
|
Bug#25411 (trigger code truncated), PART II
Bug 28127 (Some valid identifiers names are not parsed correctly)
Bug 26302 (MySQL server cuts off trailing "*/" from comments in SP/func)
This patch is the second part of a major cleanup, required to fix
Bug 25411 (trigger code truncated).
The root cause of the issue stems from the function skip_rear_comments,
which was a work around to remove "extra" "*/" characters from the query
text, when parsing a query and reusing the text fragments to represent a
view, trigger, function or stored procedure.
The reason for this work around is that "special comments",
like /*!50002 XXX */, were not parsed properly, so that a query like:
AAA /*!50002 BBB */ CCC
would be seen by the parser as "AAA BBB */ CCC" when the current version
is greater or equal to 5.0.2
The root cause of this stems from how special comments are parsed.
Special comments are really out-of-bound text that appear inside a query,
that affects how the parser behave.
In nature, /*!50002 XXX */ in MySQL is similar to the C concept
of preprocessing :
#if VERSION >= 50002
XXX
#endif
Depending on the current VERSION of the server, either the special comment
should be expanded or it should be ignored, but in all cases the "text" of
the query should be re-written to strip the "/*!50002" and "*/" markers,
which does not belong to the SQL language itself.
Prior to this fix, these markers would leak into :
- the storage format for VIEW,
- the storage format for FUNCTION,
- the storage format for FUNCTION parameters, in mysql.proc (param_list),
- the storage format for PROCEDURE,
- the storage format for PROCEDURE parameters, in mysql.proc (param_list),
- the storage format for TRIGGER,
- the binary log used for replication.
In all cases, not only this cause format corruption, but also provide a vector
for dormant security issues, by allowing to tunnel code that will be activated
after an upgrade.
The proper solution is to deal with special comments strictly during parsing,
when accepting a query from the outside world.
Once a query is parsed and an object is created with a persistant
representation, this object should not arbitrarily mutate after an upgrade.
In short, special comments are a useful but limited feature for MYSQLdump,
when used at an *interface* level to facilitate import/export,
but bloating the server *internal* storage format is *not* the proper way
to deal with configuration management of the user logic.
With this fix:
- the Lex_input_stream class now acts as a comment pre-processor,
and either expands or ignore special comments on the fly.
- MYSQLlex and sql_yacc.yy have been cleaned up to strictly use the
public interface of Lex_input_stream. In particular, how the input stream
accepts or rejects a character is private to Lex_input_stream, and the
internal buffer pointers of that class are strictly private, and should not
be tempered with during parsing.
This caused many changes mostly in sql_lex.cc.
During the code cleanup in case MY_LEX_NUMBER_IDENT,
Bug 28127 (Some valid identifiers names are not parsed correctly)
was found and fixed.
By parsing special comments properly, and removing the function
'skip_rear_comments' [sic],
Bug 26302 (MySQL server cuts off trailing "*/" from comments in SP/func)
has been fixed as well.
sql/event_data_objects.cc:
Cleanup of the code that extracts the query text
sql/sp.cc:
Cleanup of the code that extracts the query text
sql/sp_head.cc:
Cleanup of the code that extracts the query text
sql/sql_trigger.cc:
Cleanup of the code that extracts the query text
sql/sql_view.cc:
Cleanup of the code that extracts the query text
mysql-test/r/comments.result:
Bug#25411 (trigger code truncated)
mysql-test/r/sp.result:
Bug#25411 (trigger code truncated)
Bug 26302 (MySQL server cuts off trailing "*/" from comments in SP/func)
mysql-test/r/trigger.result:
Bug#25411 (trigger code truncated)
mysql-test/r/varbinary.result:
Bug 28127 (Some valid identifiers names are not parsed correctly)
mysql-test/t/comments.test:
Bug#25411 (trigger code truncated)
mysql-test/t/sp.test:
Bug#25411 (trigger code truncated)
Bug 26302 (MySQL server cuts off trailing "*/" from comments in SP/func)
mysql-test/t/trigger.test:
Bug#25411 (trigger code truncated)
mysql-test/t/varbinary.test:
Bug 28127 (Some valid identifiers names are not parsed correctly)
sql/sql_lex.cc:
Implemented comment pre-processing in Lex_input_stream,
major cleanup of the lex/yacc code to not use Lex_input_stream private members.
sql/sql_lex.h:
Implemented comment pre-processing in Lex_input_stream,
major cleanup of the lex/yacc code to not use Lex_input_stream private members.
sql/sql_yacc.yy:
post merge fix : view_check_options must be parsed before signaling the end of the query
2007-06-12 23:23:58 +02:00
|
|
|
|
|
|
|
#
|
|
|
|
# Bug#25411 (trigger code truncated)
|
|
|
|
#
|
|
|
|
|
|
|
|
--disable_warnings
|
|
|
|
drop table if exists table_25411_a;
|
|
|
|
drop table if exists table_25411_b;
|
|
|
|
--enable_warnings
|
|
|
|
|
|
|
|
create table table_25411_a(a int);
|
|
|
|
create table table_25411_b(b int);
|
|
|
|
|
|
|
|
create trigger trg_25411a_ai after insert on table_25411_a
|
|
|
|
for each row
|
|
|
|
insert into table_25411_b select new.*;
|
|
|
|
|
|
|
|
select * from table_25411_a;
|
|
|
|
|
|
|
|
--error ER_BAD_TABLE_ERROR
|
|
|
|
insert into table_25411_a values (1);
|
|
|
|
|
|
|
|
select * from table_25411_a;
|
|
|
|
|
|
|
|
drop table table_25411_a;
|
|
|
|
drop table table_25411_b;
|
|
|
|
|
2007-11-01 13:42:14 +01:00
|
|
|
#
|
|
|
|
# Bug #31866: MySQL Server crashes on SHOW CREATE TRIGGER statement
|
|
|
|
#
|
|
|
|
|
2007-11-16 18:05:30 +01:00
|
|
|
--disable_warnings
|
2007-11-01 13:42:14 +01:00
|
|
|
DROP TRIGGER IF EXISTS trg;
|
2007-11-16 18:05:30 +01:00
|
|
|
--enable_warnings
|
2007-11-01 13:42:14 +01:00
|
|
|
|
|
|
|
--error ER_TRG_DOES_NOT_EXIST
|
|
|
|
SHOW CREATE TRIGGER trg;
|
|
|
|
|
2007-11-29 12:42:26 +01:00
|
|
|
#
|
|
|
|
# Bug#23713 LOCK TABLES + CREATE TRIGGER + FLUSH TABLES WITH READ LOCK = deadlock
|
|
|
|
#
|
|
|
|
# Test of trigger creation and removal under LOCK TABLES
|
|
|
|
#
|
|
|
|
|
|
|
|
--disable_warnings
|
|
|
|
drop table if exists t1;
|
|
|
|
--enable_warnings
|
|
|
|
|
|
|
|
create table t1 (i int, j int);
|
|
|
|
|
|
|
|
create trigger t1_bi before insert on t1 for each row begin end;
|
2015-03-04 06:52:01 +01:00
|
|
|
--error ER_TRG_ALREADY_EXISTS
|
2007-11-29 12:42:26 +01:00
|
|
|
create trigger t1_bi before insert on t1 for each row begin end;
|
2015-03-04 06:52:01 +01:00
|
|
|
create trigger t1_bi2 before insert on t1 for each row begin end;
|
2007-11-29 12:42:26 +01:00
|
|
|
drop trigger t1_bi;
|
2016-10-02 14:35:08 +02:00
|
|
|
drop trigger t1_bi2;
|
2007-11-29 12:42:26 +01:00
|
|
|
--error ER_TRG_DOES_NOT_EXIST
|
|
|
|
drop trigger t1_bi;
|
|
|
|
|
|
|
|
lock tables t1 read;
|
|
|
|
--error ER_TABLE_NOT_LOCKED_FOR_WRITE
|
|
|
|
create trigger t1_bi before insert on t1 for each row begin end;
|
|
|
|
--error ER_TABLE_NOT_LOCKED_FOR_WRITE
|
|
|
|
create trigger t1_bi before insert on t1 for each row begin end;
|
|
|
|
--error ER_TRG_DOES_NOT_EXIST
|
|
|
|
drop trigger t1_bi;
|
|
|
|
unlock tables;
|
|
|
|
|
|
|
|
create trigger t1_bi before insert on t1 for each row begin end;
|
|
|
|
lock tables t1 read;
|
|
|
|
--error ER_TABLE_NOT_LOCKED_FOR_WRITE
|
|
|
|
create trigger t1_bi before insert on t1 for each row begin end;
|
|
|
|
--error ER_TABLE_NOT_LOCKED_FOR_WRITE
|
|
|
|
drop trigger t1_bi;
|
|
|
|
unlock tables;
|
|
|
|
drop trigger t1_bi;
|
|
|
|
|
|
|
|
lock tables t1 write;
|
|
|
|
create trigger b1_bi before insert on t1 for each row set new.i = new.i + 10;
|
|
|
|
insert into t1 values (10, 10);
|
|
|
|
drop trigger b1_bi;
|
|
|
|
insert into t1 values (10, 10);
|
|
|
|
select * from t1;
|
|
|
|
unlock tables;
|
|
|
|
|
|
|
|
drop table t1;
|
|
|
|
|
2008-02-12 12:44:27 +01:00
|
|
|
#
|
|
|
|
# Bug#23771 AFTER UPDATE trigger not invoked when there are no changes of the data
|
|
|
|
#
|
|
|
|
|
|
|
|
--disable_warnings
|
|
|
|
drop table if exists t1, t2;
|
|
|
|
drop trigger if exists trg1;
|
|
|
|
drop trigger if exists trg2;
|
|
|
|
--enable_warnings
|
|
|
|
create table t1 (a int);
|
|
|
|
create table t2 (b int);
|
|
|
|
create trigger trg1 after update on t1 for each row set @a= @a+1;
|
|
|
|
create trigger trg2 after update on t2 for each row set @b= @b+1;
|
|
|
|
insert into t1 values (1), (2), (3);
|
|
|
|
insert into t2 values (1), (2), (3);
|
|
|
|
set @a= 0;
|
|
|
|
set @b= 0;
|
|
|
|
update t1, t2 set t1.a= t1.a, t2.b= t2.b;
|
|
|
|
select @a, @b;
|
|
|
|
update t1, t2 set t1.a= t2.b, t2.b= t1.a;
|
|
|
|
select @a, @b;
|
|
|
|
update t1 set a= a;
|
|
|
|
select @a, @b;
|
|
|
|
update t2 set b= b;
|
|
|
|
select @a, @b;
|
|
|
|
update t1 set a= 1;
|
|
|
|
select @a, @b;
|
|
|
|
update t2 set b= 1;
|
|
|
|
select @a, @b;
|
|
|
|
drop trigger trg1;
|
|
|
|
drop trigger trg2;
|
|
|
|
drop table t1, t2;
|
|
|
|
|
2009-06-22 14:51:33 +02:00
|
|
|
#
|
|
|
|
# Bug#44653: Server crash noticed when executing random queries with partitions.
|
|
|
|
#
|
|
|
|
CREATE TABLE t1 ( a INT, b INT );
|
|
|
|
CREATE TABLE t2 ( a INT AUTO_INCREMENT KEY, b INT );
|
|
|
|
|
|
|
|
INSERT INTO t1 (a) VALUES (1);
|
|
|
|
|
|
|
|
delimiter //;
|
|
|
|
CREATE TRIGGER tr1
|
|
|
|
BEFORE INSERT ON t2
|
|
|
|
FOR EACH ROW
|
|
|
|
BEGIN
|
|
|
|
UPDATE a_nonextisting_table SET a = 1;
|
|
|
|
END//
|
|
|
|
delimiter ;//
|
|
|
|
|
|
|
|
--disable_abort_on_error
|
|
|
|
CREATE TABLE IF NOT EXISTS t2 ( a INT, b INT ) SELECT a, b FROM t1;
|
|
|
|
--enable_abort_on_error
|
|
|
|
|
|
|
|
# Caused failed assertion
|
|
|
|
SELECT * FROM t2;
|
|
|
|
|
|
|
|
DROP TABLE t1, t2;
|
|
|
|
|
2010-03-09 22:55:08 +01:00
|
|
|
--echo #
|
|
|
|
--echo # Bug#51650 crash with user variables and triggers
|
|
|
|
--echo #
|
|
|
|
|
|
|
|
--disable_warnings
|
|
|
|
DROP TRIGGER IF EXISTS trg1;
|
|
|
|
DROP TABLE IF EXISTS t1, t2;
|
|
|
|
--enable_warnings
|
|
|
|
|
|
|
|
CREATE TABLE t1 (b VARCHAR(50) NOT NULL);
|
|
|
|
CREATE TABLE t2 (a VARCHAR(10) NOT NULL DEFAULT '');
|
|
|
|
|
|
|
|
delimiter //;
|
|
|
|
CREATE TRIGGER trg1 AFTER INSERT ON t2
|
|
|
|
FOR EACH ROW BEGIN
|
|
|
|
SELECT 1 FROM t1 c WHERE
|
|
|
|
(@bug51650 IS NULL OR @bug51650 != c.b) AND c.b = NEW.a LIMIT 1 INTO @foo;
|
|
|
|
END//
|
|
|
|
delimiter ;//
|
|
|
|
|
|
|
|
SET @bug51650 = 1;
|
|
|
|
INSERT IGNORE INTO t2 VALUES();
|
|
|
|
INSERT IGNORE INTO t1 SET b = '777';
|
|
|
|
INSERT IGNORE INTO t2 SET a = '111';
|
|
|
|
SET @bug51650 = 1;
|
|
|
|
INSERT IGNORE INTO t2 SET a = '777';
|
|
|
|
|
|
|
|
DROP TRIGGER trg1;
|
|
|
|
DROP TABLE t1, t2;
|
|
|
|
|
2010-03-29 04:32:30 +02:00
|
|
|
#
|
|
|
|
# Bug #48525: trigger changes "Column 'id' cannot be null" behaviour
|
|
|
|
#
|
|
|
|
CREATE TABLE t1 (id INT NOT NULL);
|
|
|
|
CREATE TABLE t2 (id INT NOT NULL);
|
|
|
|
INSERT t1 VALUES (1),(2),(3);
|
2017-02-08 21:28:00 +01:00
|
|
|
UPDATE IGNORE t1 SET id=NULL;
|
2010-03-29 04:32:30 +02:00
|
|
|
CREATE TRIGGER t1_bu BEFORE UPDATE ON t1 FOR EACH ROW
|
|
|
|
INSERT INTO t2 VALUES (3);
|
|
|
|
UPDATE t1 SET id=NULL;
|
|
|
|
DROP TRIGGER t1_bu;
|
|
|
|
DROP TABLE t1,t2;
|
|
|
|
|
2010-04-01 15:15:22 +02:00
|
|
|
--echo #
|
|
|
|
--echo # Bug#50755: Crash if stored routine def contains version comments
|
|
|
|
--echo #
|
|
|
|
|
|
|
|
--disable_warnings
|
|
|
|
DROP DATABASE IF EXISTS db1;
|
|
|
|
DROP TRIGGER IF EXISTS trg1;
|
|
|
|
DROP TABLE IF EXISTS t1, t2;
|
|
|
|
--enable_warnings
|
|
|
|
|
|
|
|
CREATE DATABASE db1;
|
|
|
|
USE db1;
|
|
|
|
|
|
|
|
CREATE TABLE t1 (b INT);
|
|
|
|
CREATE TABLE t2 (a INT);
|
|
|
|
|
|
|
|
CREATE TRIGGER trg1 BEFORE INSERT ON t2 FOR EACH ROW INSERT/*!INTO*/t1 VALUES (1);
|
|
|
|
--echo # Used to crash
|
2016-10-02 14:35:08 +02:00
|
|
|
--replace_column 6 #
|
2010-04-01 15:15:22 +02:00
|
|
|
SHOW TRIGGERS IN db1;
|
|
|
|
--error ER_PARSE_ERROR
|
|
|
|
INSERT INTO t2 VALUES (1);
|
|
|
|
SELECT * FROM t1;
|
|
|
|
|
|
|
|
--echo # Work around Bug#45235
|
|
|
|
let $MYSQLD_DATADIR = `select @@datadir`;
|
|
|
|
--remove_file $MYSQLD_DATADIR/db1/t2.TRG
|
|
|
|
--remove_file $MYSQLD_DATADIR/db1/trg1.TRN
|
|
|
|
|
|
|
|
DROP DATABASE db1;
|
|
|
|
USE test;
|
|
|
|
|
2019-04-29 12:32:36 +02:00
|
|
|
--echo # End of 5.1 tests.
|
2009-10-12 12:59:55 +02:00
|
|
|
|
2011-10-06 15:56:59 +02:00
|
|
|
#
|
|
|
|
# Test that using a trigger will not open mysql.proc
|
|
|
|
#
|
|
|
|
create table t1 (i int);
|
|
|
|
create table t2 (i int);
|
|
|
|
flush tables;
|
|
|
|
flush status;
|
|
|
|
delimiter //;
|
|
|
|
CREATE DEFINER=`root`@`localhost` TRIGGER trg AFTER DELETE ON t1 FOR EACH ROW BEGIN DELETE FROM t2 WHERE t2.i = OLD.i; END //
|
|
|
|
delimiter ;//
|
|
|
|
insert into t1 values (1),(2);
|
|
|
|
insert into t2 values (1),(2);
|
|
|
|
delete from t1 where i=1;
|
|
|
|
#
|
|
|
|
# If mysql.proc would be used we would have 4 here. 3 is the correct number.
|
|
|
|
# (CREATE TRIGGER will open t1 and then flush it)
|
|
|
|
#
|
|
|
|
show status like 'Opened_tables';
|
|
|
|
select * from t1;
|
|
|
|
select * from t2;
|
|
|
|
drop table t1,t2;
|
|
|
|
|
2019-04-29 12:32:36 +02:00
|
|
|
--echo # End of 5.2 tests.
|
2009-10-12 12:59:55 +02:00
|
|
|
|
|
|
|
--echo #
|
|
|
|
--echo # Bug#34453 Can't change size of file (Errcode: 1224)
|
|
|
|
--echo #
|
|
|
|
|
|
|
|
--disable_warnings
|
|
|
|
DROP TRIGGER IF EXISTS t1_bi;
|
|
|
|
DROP TRIGGER IF EXISTS t1_bd;
|
|
|
|
DROP TABLE IF EXISTS t1;
|
|
|
|
DROP TEMPORARY TABLE IF EXISTS t2;
|
|
|
|
--enable_warnings
|
|
|
|
|
|
|
|
CREATE TABLE t1 (s1 INT);
|
|
|
|
CREATE TEMPORARY TABLE t2 (s1 INT);
|
|
|
|
CREATE TRIGGER t1_bi BEFORE INSERT ON t1 FOR EACH ROW INSERT INTO t2 VALUES (0);
|
|
|
|
CREATE TRIGGER t1_bd BEFORE DELETE ON t1 FOR EACH ROW DELETE FROM t2;
|
|
|
|
INSERT INTO t1 VALUES (0);
|
|
|
|
INSERT INTO t1 VALUES (0);
|
|
|
|
SELECT * FROM t1;
|
|
|
|
SELECT * FROM t2;
|
|
|
|
-- echo # Reported to give ERROR 14 (HY000):
|
|
|
|
-- echo # Can't change size of file (Errcode: 1224)
|
|
|
|
-- echo # on Windows
|
|
|
|
DELETE FROM t1;
|
|
|
|
|
|
|
|
DROP TABLE t1;
|
|
|
|
DROP TEMPORARY TABLE t2;
|
Backport of Bug#36649 to mysql-next-mr
------------------------------------------------------------
revno: 2630.39.3
revision-id: davi.arnaut@sun.com-20081210215359-i876m4zgc2d6rzs3
parent: kostja@sun.com-20081208222938-9es7wl61moli71ht
committer: Davi Arnaut <Davi.Arnaut@Sun.COM>
branch nick: 36649-6.0
timestamp: Wed 2008-12-10 19:53:59 -0200
message:
Bug#36649: Condition area is not properly cleaned up after stored routine invocation
The problem is that the diagnostics area of a trigger is not
isolated from the area of the statement that caused the trigger
invocation. In MySQL terms, it means that warnings generated
during the execution of the trigger are not removed from the
"warning area" at the end of the execution.
Before this fix, the rules for MySQL message list life cycle (see
manual entry for SHOW WARNINGS) did not apply to statements
inside stored programs:
- The manual says that the list of messages is cleared by a
statement that uses a table (any table). However, such
statement, if run inside a stored program did not clear the
message list.
- The manual says that the list is cleared by a statement that
generates a new error or a warning, but this was not the case
with stored program statements either and is changed to be the
case as well.
In other words, after this fix, a statement has the same effect
on the message list regardless of whether it's executed inside a
stored program/sub-statement or not.
This introduces an incompatible change:
- before this fix, a, e.g. statement inside a trigger could
never clear the global warning list
- after this fix, a trigger that generates a warning or uses a
table, clears the global warning list
- however, when we leave a trigger or a function, the caller's
warning information is restored (see more on this below).
This change is not backward compatible as it is intended to make
MySQL behavior similar to the SQL standard behavior:
A stored function or trigger will get its own "warning area" (or,
in standard terminology, diagnostics area). At the beginning of
the stored function or trigger, all messages from the caller area
will be copied to the area of the trigger. During execution, the
message list will be cleared according to the MySQL rules
described on the manual (SHOW WARNINGS entry). At the end of the
function/trigger, the "warning area" will be destroyed along with
all warnings it contains, except that if the last statement of
the function/trigger generated messages, these are copied into
the "warning area" of the caller.
Consequently, statements that use a table or generate a warning
*will* clear warnings inside the trigger, but that will have no
effect to the warning list of the calling (outer) statement.
mysql-test/r/sp.result:
Fix test case results.
mysql-test/r/trigger.result:
Fix test case results.
mysql-test/t/sp.test:
Add test case for Bug#36649
mysql-test/t/trigger.test:
Add test case for Bug#36649
sql/sp_head.cc:
Emulate multiple warning areas -- one per stored program instance.
sql/sql_parse.cc:
Message list reset rules are the same for statements inside
or outside compound statements.
2009-11-10 19:11:27 +01:00
|
|
|
|
|
|
|
#
|
|
|
|
# Bug#36649: Condition area is not properly cleaned up after stored routine invocation
|
|
|
|
#
|
|
|
|
|
2017-02-08 21:28:00 +01:00
|
|
|
SET sql_mode = 'NO_ENGINE_SUBSTITUTION';
|
Backport of Bug#36649 to mysql-next-mr
------------------------------------------------------------
revno: 2630.39.3
revision-id: davi.arnaut@sun.com-20081210215359-i876m4zgc2d6rzs3
parent: kostja@sun.com-20081208222938-9es7wl61moli71ht
committer: Davi Arnaut <Davi.Arnaut@Sun.COM>
branch nick: 36649-6.0
timestamp: Wed 2008-12-10 19:53:59 -0200
message:
Bug#36649: Condition area is not properly cleaned up after stored routine invocation
The problem is that the diagnostics area of a trigger is not
isolated from the area of the statement that caused the trigger
invocation. In MySQL terms, it means that warnings generated
during the execution of the trigger are not removed from the
"warning area" at the end of the execution.
Before this fix, the rules for MySQL message list life cycle (see
manual entry for SHOW WARNINGS) did not apply to statements
inside stored programs:
- The manual says that the list of messages is cleared by a
statement that uses a table (any table). However, such
statement, if run inside a stored program did not clear the
message list.
- The manual says that the list is cleared by a statement that
generates a new error or a warning, but this was not the case
with stored program statements either and is changed to be the
case as well.
In other words, after this fix, a statement has the same effect
on the message list regardless of whether it's executed inside a
stored program/sub-statement or not.
This introduces an incompatible change:
- before this fix, a, e.g. statement inside a trigger could
never clear the global warning list
- after this fix, a trigger that generates a warning or uses a
table, clears the global warning list
- however, when we leave a trigger or a function, the caller's
warning information is restored (see more on this below).
This change is not backward compatible as it is intended to make
MySQL behavior similar to the SQL standard behavior:
A stored function or trigger will get its own "warning area" (or,
in standard terminology, diagnostics area). At the beginning of
the stored function or trigger, all messages from the caller area
will be copied to the area of the trigger. During execution, the
message list will be cleared according to the MySQL rules
described on the manual (SHOW WARNINGS entry). At the end of the
function/trigger, the "warning area" will be destroyed along with
all warnings it contains, except that if the last statement of
the function/trigger generated messages, these are copied into
the "warning area" of the caller.
Consequently, statements that use a table or generate a warning
*will* clear warnings inside the trigger, but that will have no
effect to the warning list of the calling (outer) statement.
mysql-test/r/sp.result:
Fix test case results.
mysql-test/r/trigger.result:
Fix test case results.
mysql-test/t/sp.test:
Add test case for Bug#36649
mysql-test/t/trigger.test:
Add test case for Bug#36649
sql/sp_head.cc:
Emulate multiple warning areas -- one per stored program instance.
sql/sql_parse.cc:
Message list reset rules are the same for statements inside
or outside compound statements.
2009-11-10 19:11:27 +01:00
|
|
|
--disable_warnings
|
|
|
|
DROP TRIGGER IF EXISTS trg1;
|
|
|
|
DROP TABLE IF EXISTS t1;
|
|
|
|
--enable_warnings
|
|
|
|
|
|
|
|
CREATE TABLE t1 (a INT);
|
|
|
|
|
|
|
|
delimiter |;
|
|
|
|
CREATE TRIGGER trg1 BEFORE INSERT ON t1 FOR EACH ROW
|
|
|
|
BEGIN
|
|
|
|
DECLARE a CHAR;
|
|
|
|
SELECT 'ab' INTO a;
|
|
|
|
SELECT 'ab' INTO a;
|
|
|
|
SELECT 'a' INTO a;
|
|
|
|
END|
|
|
|
|
delimiter ;|
|
|
|
|
|
|
|
|
INSERT INTO t1 VALUES (1);
|
|
|
|
|
|
|
|
DROP TRIGGER trg1;
|
|
|
|
DROP TABLE t1;
|
|
|
|
|
|
|
|
#
|
|
|
|
# Successive trigger actuations
|
|
|
|
#
|
|
|
|
|
|
|
|
--disable_warnings
|
|
|
|
DROP TRIGGER IF EXISTS trg1;
|
|
|
|
DROP TRIGGER IF EXISTS trg2;
|
|
|
|
DROP TABLE IF EXISTS t1;
|
|
|
|
--enable_warnings
|
|
|
|
|
|
|
|
CREATE TABLE t1 (a INT);
|
|
|
|
|
|
|
|
delimiter |;
|
|
|
|
|
|
|
|
CREATE TRIGGER trg1 BEFORE INSERT ON t1 FOR EACH ROW
|
|
|
|
BEGIN
|
|
|
|
DECLARE trg1 CHAR;
|
|
|
|
SELECT 'ab' INTO trg1;
|
|
|
|
END|
|
|
|
|
|
|
|
|
CREATE TRIGGER trg2 AFTER INSERT ON t1 FOR EACH ROW
|
|
|
|
BEGIN
|
|
|
|
DECLARE trg2 CHAR;
|
|
|
|
SELECT 'ab' INTO trg2;
|
|
|
|
END|
|
|
|
|
|
|
|
|
delimiter ;|
|
2017-02-08 21:28:00 +01:00
|
|
|
SET sql_mode = DEFAULT;
|
Backport of Bug#36649 to mysql-next-mr
------------------------------------------------------------
revno: 2630.39.3
revision-id: davi.arnaut@sun.com-20081210215359-i876m4zgc2d6rzs3
parent: kostja@sun.com-20081208222938-9es7wl61moli71ht
committer: Davi Arnaut <Davi.Arnaut@Sun.COM>
branch nick: 36649-6.0
timestamp: Wed 2008-12-10 19:53:59 -0200
message:
Bug#36649: Condition area is not properly cleaned up after stored routine invocation
The problem is that the diagnostics area of a trigger is not
isolated from the area of the statement that caused the trigger
invocation. In MySQL terms, it means that warnings generated
during the execution of the trigger are not removed from the
"warning area" at the end of the execution.
Before this fix, the rules for MySQL message list life cycle (see
manual entry for SHOW WARNINGS) did not apply to statements
inside stored programs:
- The manual says that the list of messages is cleared by a
statement that uses a table (any table). However, such
statement, if run inside a stored program did not clear the
message list.
- The manual says that the list is cleared by a statement that
generates a new error or a warning, but this was not the case
with stored program statements either and is changed to be the
case as well.
In other words, after this fix, a statement has the same effect
on the message list regardless of whether it's executed inside a
stored program/sub-statement or not.
This introduces an incompatible change:
- before this fix, a, e.g. statement inside a trigger could
never clear the global warning list
- after this fix, a trigger that generates a warning or uses a
table, clears the global warning list
- however, when we leave a trigger or a function, the caller's
warning information is restored (see more on this below).
This change is not backward compatible as it is intended to make
MySQL behavior similar to the SQL standard behavior:
A stored function or trigger will get its own "warning area" (or,
in standard terminology, diagnostics area). At the beginning of
the stored function or trigger, all messages from the caller area
will be copied to the area of the trigger. During execution, the
message list will be cleared according to the MySQL rules
described on the manual (SHOW WARNINGS entry). At the end of the
function/trigger, the "warning area" will be destroyed along with
all warnings it contains, except that if the last statement of
the function/trigger generated messages, these are copied into
the "warning area" of the caller.
Consequently, statements that use a table or generate a warning
*will* clear warnings inside the trigger, but that will have no
effect to the warning list of the calling (outer) statement.
mysql-test/r/sp.result:
Fix test case results.
mysql-test/r/trigger.result:
Fix test case results.
mysql-test/t/sp.test:
Add test case for Bug#36649
mysql-test/t/trigger.test:
Add test case for Bug#36649
sql/sp_head.cc:
Emulate multiple warning areas -- one per stored program instance.
sql/sql_parse.cc:
Message list reset rules are the same for statements inside
or outside compound statements.
2009-11-10 19:11:27 +01:00
|
|
|
|
|
|
|
INSERT INTO t1 VALUES (0);
|
|
|
|
SELECT * FROM t1;
|
|
|
|
SHOW WARNINGS;
|
|
|
|
INSERT INTO t1 VALUES (1),(2);
|
|
|
|
|
|
|
|
DROP TRIGGER trg1;
|
|
|
|
DROP TRIGGER trg2;
|
|
|
|
DROP TABLE t1;
|
|
|
|
|
2009-12-09 10:37:54 +01:00
|
|
|
|
|
|
|
--echo #
|
|
|
|
--echo # Bug #46747 "Crash in MDL_ticket::upgrade_shared_lock_to_exclusive
|
|
|
|
--echo # on TRIGGER + TEMP table".
|
|
|
|
--echo #
|
|
|
|
|
|
|
|
--disable_warnings
|
|
|
|
drop trigger if exists t1_bi;
|
|
|
|
drop temporary table if exists t1;
|
|
|
|
drop table if exists t1;
|
|
|
|
--enable_warnings
|
|
|
|
|
|
|
|
create table t1 (i int);
|
|
|
|
create trigger t1_bi before insert on t1 for each row set @a:=1;
|
|
|
|
--echo # Create temporary table which shadows base table with trigger.
|
|
|
|
create temporary table t1 (j int);
|
|
|
|
--echo # Dropping of trigger should succeed.
|
|
|
|
drop trigger t1_bi;
|
|
|
|
select trigger_name from information_schema.triggers
|
|
|
|
where event_object_schema = 'test' and event_object_table = 't1';
|
|
|
|
--echo # Clean-up.
|
|
|
|
drop temporary table t1;
|
|
|
|
drop table t1;
|
|
|
|
|
2011-05-09 10:29:23 +02:00
|
|
|
--echo #
|
|
|
|
--echo # Bug #12362125: SP INOUT HANDLING IS BROKEN FOR TEXT TYPE.
|
|
|
|
--echo #
|
|
|
|
|
|
|
|
--disable_warnings
|
|
|
|
DROP TABLE IF EXISTS t1;
|
|
|
|
--enable_warnings
|
|
|
|
|
|
|
|
CREATE TABLE t1(c TEXT);
|
|
|
|
|
|
|
|
delimiter |;
|
|
|
|
CREATE TRIGGER t1_bi BEFORE INSERT ON t1 FOR EACH ROW
|
|
|
|
BEGIN
|
|
|
|
DECLARE v TEXT;
|
|
|
|
SET v = 'aaa';
|
|
|
|
SET NEW.c = v;
|
|
|
|
END|
|
|
|
|
delimiter ;|
|
|
|
|
|
|
|
|
INSERT INTO t1 VALUES('qazwsxedc');
|
|
|
|
|
|
|
|
SELECT c FROM t1;
|
|
|
|
|
|
|
|
DROP TABLE t1;
|
|
|
|
|
|
|
|
--echo
|
2019-04-29 12:32:36 +02:00
|
|
|
--echo # End of 5.5 tests.
|
2012-01-13 15:50:02 +01:00
|
|
|
|
2012-01-03 05:06:36 +01:00
|
|
|
--echo #
|
|
|
|
--echo # BUG #910083: materialized subquery in a trigger
|
|
|
|
--echo #
|
|
|
|
|
|
|
|
SET @save_optimizer_switch=@@optimizer_switch;
|
|
|
|
SET optimizer_switch='materialization=on';
|
|
|
|
|
|
|
|
CREATE TABLE t1 (a int);
|
|
|
|
CREATE TABLE t2 (b int);
|
|
|
|
|
|
|
|
CREATE TRIGGER tr AFTER UPDATE ON t1 FOR EACH ROW
|
|
|
|
UPDATE t2 SET b = (SELECT COUNT(a) FROM t1);
|
|
|
|
|
|
|
|
INSERT INTO t1
|
|
|
|
VALUES (1),(2),(3),(4),(5),(6),(7),(8),(9);
|
|
|
|
|
|
|
|
INSERT INTO t2
|
|
|
|
VALUES (0),(0),(0),(0),(0),(0),(0),(0),(0);
|
|
|
|
|
|
|
|
send
|
|
|
|
UPDATE t1 SET a = 3;
|
|
|
|
|
|
|
|
connect(con1,localhost,root,,);
|
|
|
|
SELECT COUNT(*) FROM t1;
|
|
|
|
disconnect con1;
|
|
|
|
|
|
|
|
connection default;
|
|
|
|
reap;
|
|
|
|
SELECT * FROM t2;
|
|
|
|
UPDATE t1 SET a = 2;
|
|
|
|
SELECT * FROM t2;
|
|
|
|
|
|
|
|
SET optimizer_switch=@save_optimizer_switch;
|
|
|
|
|
|
|
|
DROP TRIGGER tr;
|
|
|
|
DROP TABLE t1, t2;
|
|
|
|
|
2019-04-29 12:32:36 +02:00
|
|
|
--echo # End of 5.3 tests.
|
2012-01-03 05:06:36 +01:00
|
|
|
|
2015-11-16 21:42:18 +01:00
|
|
|
#
|
|
|
|
# MDEV-4829 BEFORE INSERT triggers dont issue 1406 error
|
2016-10-02 14:35:08 +02:00
|
|
|
# Also check timestamp for trigger
|
2015-11-16 21:42:18 +01:00
|
|
|
#
|
|
|
|
|
2016-10-02 14:35:08 +02:00
|
|
|
set time_zone="+00:00";
|
|
|
|
SET TIMESTAMP=UNIX_TIMESTAMP('2001-01-01 10:20:30');
|
2015-11-16 21:42:18 +01:00
|
|
|
SET @@session.sql_mode = 'STRICT_ALL_TABLES,STRICT_TRANS_TABLES';
|
|
|
|
CREATE TABLE t1 (c CHAR(1) NOT NULL);
|
|
|
|
DELIMITER |;
|
|
|
|
CREATE TRIGGER t1_bi
|
|
|
|
BEFORE INSERT
|
|
|
|
ON t1
|
|
|
|
FOR EACH ROW
|
|
|
|
BEGIN
|
|
|
|
SET NEW.c = 'www';
|
|
|
|
END;
|
|
|
|
|
|
|
|
|
DELIMITER ;|
|
|
|
|
SET @@session.sql_mode = default;
|
|
|
|
--error ER_DATA_TOO_LONG
|
|
|
|
INSERT INTO t1 VALUES ('a');
|
2016-10-02 14:35:08 +02:00
|
|
|
show create trigger t1_bi;
|
2015-11-16 21:42:18 +01:00
|
|
|
DROP TRIGGER t1_bi;
|
|
|
|
DROP TABLE t1;
|
2016-10-02 14:35:08 +02:00
|
|
|
SET TIMESTAMP=DEFAULT;
|
|
|
|
set time_zone= @@global.time_zone;
|
|
|
|
|
2017-11-06 14:35:58 +01:00
|
|
|
--echo #
|
|
|
|
--echo # MDEV-13936: Server crashes in Time_and_counter_tracker::incr_loops
|
|
|
|
--echo #
|
|
|
|
|
|
|
|
CREATE TABLE t1 (i INT);
|
|
|
|
CREATE VIEW v1 AS SELECT * FROM t1 WHERE RAND() > 0.5;
|
|
|
|
CREATE TABLE t2 (a int);
|
|
|
|
CREATE TABLE t3 (a int);
|
|
|
|
|
|
|
|
create trigger trg after insert on t2 for each row
|
|
|
|
INSERT INTO t3 SELECT MAX(i) FROM v1 UNION SELECT MAX(i) FROM v1;
|
|
|
|
|
|
|
|
drop table t1;
|
|
|
|
|
|
|
|
--error ER_NO_SUCH_TABLE
|
|
|
|
insert into t2 value (2);
|
|
|
|
CREATE TABLE t1 (i INT);
|
|
|
|
insert into t2 value (2);
|
|
|
|
|
|
|
|
DROP VIEW v1;
|
|
|
|
DROP TABLE t1,t2,t3;
|
|
|
|
|
2018-05-24 14:18:09 +02:00
|
|
|
--echo #
|
|
|
|
--echo # MDEV-16093
|
|
|
|
--echo # Assertion `global_status_var.global_memory_used == 0' failed or
|
|
|
|
--echo # bytes lost after inserting into table with non-null blob and trigger
|
|
|
|
--echo #
|
|
|
|
|
|
|
|
CREATE TABLE t1 (b BLOB NOT NULL);
|
|
|
|
CREATE TRIGGER tr BEFORE UPDATE ON t1 FOR EACH ROW BEGIN END;
|
|
|
|
INSERT INTO t1 VALUES ('foo');
|
|
|
|
DROP TABLE t1;
|
2017-11-06 14:35:58 +01:00
|
|
|
|
2018-05-24 14:18:09 +02:00
|
|
|
--echo #
|
|
|
|
--echo # End of 10.1 tests.
|
|
|
|
--echo #
|
2017-11-21 19:47:46 +01:00
|
|
|
|
2016-10-02 14:35:08 +02:00
|
|
|
#
|
2017-11-21 19:47:46 +01:00
|
|
|
# MDEV-10915 Count number of executed triggers
|
2016-10-02 14:35:08 +02:00
|
|
|
#
|
|
|
|
|
|
|
|
create table t1 (i int);
|
|
|
|
create trigger tr1 after insert on t1 for each row set @a=@a+1;
|
|
|
|
create trigger tr2 after insert on t1 for each row set @a=@a+1;
|
|
|
|
create trigger tr3 after insert on t1 for each row set @a=@a+1;
|
|
|
|
flush status;
|
|
|
|
show status like 'Executed_triggers';
|
|
|
|
set @a=0;
|
|
|
|
insert into t1 values (1);
|
|
|
|
show status like 'Executed_triggers';
|
|
|
|
select @a;
|
|
|
|
drop table t1;
|
|
|
|
|
|
|
|
#
|
|
|
|
# MDEV-10916 In trigger's CREATED time microseconds are misinterpreted
|
|
|
|
#
|
2015-11-16 21:42:18 +01:00
|
|
|
|
2016-10-02 14:35:08 +02:00
|
|
|
create table t1 (i int);
|
|
|
|
set time_zone="+0:00";
|
|
|
|
SET TIMESTAMP=UNIX_TIMESTAMP('2016-01-01 10:10:10.33');
|
|
|
|
select now(2);
|
|
|
|
create or replace trigger tr1 after insert on t1 for each row set @a=@a+1;
|
|
|
|
SET TIMESTAMP=UNIX_TIMESTAMP('2016-01-01 10:10:10.99');
|
|
|
|
select now(2);
|
|
|
|
create or replace trigger tr2 after insert on t1 for each row set @a=@a+1;
|
|
|
|
select now(2);
|
|
|
|
select trigger_name, action_order, created from information_schema.triggers
|
|
|
|
where event_object_table = 't1' and trigger_schema='test';
|
|
|
|
drop table t1;
|
|
|
|
set time_zone= @@global.time_zone;
|
2017-04-07 11:40:27 +02:00
|
|
|
|
2017-06-11 01:39:39 +02:00
|
|
|
--echo # MDEV-12992: Increasing memory consumption
|
|
|
|
--echo with each invocation of trigger
|
|
|
|
--echo #
|
|
|
|
|
|
|
|
--let $n= 20000
|
|
|
|
|
|
|
|
CREATE TABLE t1 (a INT);
|
|
|
|
INSERT INTO t1 VALUES (1);
|
|
|
|
CREATE TABLE t2 (b INT);
|
|
|
|
CREATE TRIGGER tr
|
|
|
|
AFTER UPDATE ON t1 FOR EACH ROW SELECT (SELECT b FROM t2) INTO @x;
|
|
|
|
|
|
|
|
--disable_query_log
|
|
|
|
--echo # Running $n queries
|
|
|
|
while ($n)
|
|
|
|
{
|
|
|
|
UPDATE t1 SET a = 2;
|
|
|
|
--dec $n
|
|
|
|
}
|
|
|
|
--enable_query_log
|
|
|
|
|
|
|
|
DROP TABLE t1,t2;
|
2017-06-15 13:27:11 +02:00
|
|
|
|
2019-04-29 12:32:36 +02:00
|
|
|
--echo #
|
|
|
|
--echo # MDEV-19188 Server Crash When Using a Trigger With A Number of Virtual Columns on INSERT/UPDATE
|
|
|
|
--echo #
|
|
|
|
|
|
|
|
CREATE TABLE t1 (
|
|
|
|
virt1 INT GENERATED ALWAYS AS (0) VIRTUAL,
|
|
|
|
virt2 INT GENERATED ALWAYS AS (0) VIRTUAL,
|
|
|
|
virt3 INT GENERATED ALWAYS AS (0) VIRTUAL,
|
|
|
|
virt4 INT GENERATED ALWAYS AS (0) VIRTUAL,
|
|
|
|
virt5 INT GENERATED ALWAYS AS (0) VIRTUAL,
|
|
|
|
virt6 INT GENERATED ALWAYS AS (0) VIRTUAL,
|
|
|
|
virt7 INT GENERATED ALWAYS AS (0) VIRTUAL,
|
|
|
|
virt8 INT GENERATED ALWAYS AS (0) VIRTUAL
|
|
|
|
);
|
|
|
|
INSERT INTO t1 () VALUES ();
|
|
|
|
CREATE TRIGGER t1_trigger BEFORE INSERT ON t1 FOR EACH ROW BEGIN END;
|
|
|
|
INSERT INTO t1 () VALUES ();
|
|
|
|
DROP TABLE t1;
|
2017-06-15 13:27:11 +02:00
|
|
|
|
2017-04-07 11:40:27 +02:00
|
|
|
--echo #
|
2019-04-29 12:32:36 +02:00
|
|
|
--echo # End of 10.2 tests
|
2017-04-07 11:40:27 +02:00
|
|
|
--echo #
|
|
|
|
|
|
|
|
--echo #
|
|
|
|
--echo # MDEV-12461 TYPE OF and ROW TYPE OF anchored data types
|
|
|
|
--echo #
|
|
|
|
|
|
|
|
CREATE TABLE t1 (a INT, b INT, total INT);
|
|
|
|
DELIMITER $$;
|
|
|
|
CREATE TRIGGER tr1 BEFORE INSERT ON t1
|
|
|
|
FOR EACH ROW
|
|
|
|
BEGIN
|
|
|
|
DECLARE va TYPE OF t1.a DEFAULT NEW.a;
|
|
|
|
DECLARE vb TYPE OF t1.b DEFAULT NEW.b;
|
|
|
|
SET NEW.total:= va + vb;
|
|
|
|
END;
|
|
|
|
$$
|
|
|
|
DELIMITER ;$$
|
|
|
|
INSERT INTO t1 (a,b) VALUES (10, 20);
|
|
|
|
SELECT * FROM t1;
|
|
|
|
DROP TABLE t1;
|
2019-05-02 20:43:24 +02:00
|
|
|
|
|
|
|
--echo #
|
|
|
|
--echo # End of 10.3 tests
|
|
|
|
--echo #
|