mariadb/mysql-test/suite/vcol/r/vcol_trigger_sp_innodb.result

317 lines
6.6 KiB
Text
Raw Normal View History

SET @@session.default_storage_engine = 'InnoDB';
create table t1 (a int,
b int as (a/10),
c int as (a/10) persistent);
create table t2 (a timestamp);
create trigger trg1 before insert on t1 for each row
begin
if (new.b < 10) then
set new.a:= 100;
set new.b:= 9;
set new.c:= 9;
end if;
if (new.c > 50) then
set new.a:= 500;
end if;
end|
create trigger trg2 after insert on t1 for each row
begin
if (new.b >= 60) then
insert into t2 values (now());
end if;
end|
create function f1()
returns int
begin
declare sum1 int default '0';
declare cur1 cursor for select sum(b) from t1;
open cur1;
fetch cur1 into sum1;
close cur1;
return sum1;
end|
set sql_warnings = 1;
insert into t1 (a) values (200);
select * from t1;
a b c
200 20 20
select * from t2;
a
insert into t1 (a) values (10);
select * from t1;
a b c
200 20 20
100 10 10
select * from t2;
a
insert into t1 (a) values (600);
select * from t1;
a b c
200 20 20
100 10 10
500 50 50
select * from t2;
a
select f1();
f1()
80
set sql_warnings = 0;
drop trigger trg1;
drop trigger trg2;
drop table t2;
create procedure p1()
begin
declare i int default '0';
create table t2 like t1;
insert into t2 (a) values (100), (200);
begin
declare cur1 cursor for select sum(c) from t2;
open cur1;
fetch cur1 into i;
close cur1;
if (i=30) then
insert into t1 values (300,default,default);
end if;
end;
end|
delete from t1;
call p1();
select * from t2;
a b c
100 10 10
200 20 20
select * from t1;
a b c
300 30 30
drop table t1,t2;
drop procedure p1;
#
# MDEV-3845 values of virtual columns are not computed for triggers
#
CREATE TABLE t1 (
a INTEGER UNSIGNED NULL DEFAULT NULL,
b INTEGER UNSIGNED GENERATED ALWAYS AS (a) VIRTUAL
);
CREATE TABLE t2 (c INTEGER UNSIGNED NOT NULL);
CREATE TRIGGER t1_ins_aft
AFTER INSERT
ON t1
FOR EACH ROW
BEGIN
INSERT INTO t2 (c) VALUES (NEW.b);
END |
CREATE TRIGGER t1_del_bef
BEFORE DELETE
ON t1
FOR EACH ROW
BEGIN
INSERT INTO t2 (c) VALUES (OLD.b);
END |
INSERT INTO t1 (a) VALUES (1), (2), (3);
SELECT * FROM t2;
c
1
2
3
DELETE FROM t1;
SELECT * FROM t2;
c
1
2
3
1
2
3
DROP TRIGGER t1_ins_aft;
DROP TRIGGER t1_del_bef;
DROP TABLE t1,t2;
create table t1 (i int, t time not null, vt time(4) as (t) virtual);
create trigger trg before update on t1 for each row set @a = 1;
insert ignore into t1 (i) values (1);
Warnings:
Warning 1364 Field 't' doesn't have a default value
drop table t1;
New simpler bugfix for UPDATE and virtual BLOBs When updating a table with virtual BLOB columns, the following might happen: - an old record is read from the table, it has no virtual blob values - update_virtual_fields() is run, vcol blob gets its value into the record. But only a pointer to the value is in the table->record[0], the value is in Field_blob::value String (but it doesn't have to be! it can be in the record, if the column is just a copy of another columns: ... b VARCHAR, c BLOB AS (b) ...) - store_record(table,record[1]), old record now is in record[1] - fill_record() prepares new values in record[0], vcol blob is updated, new value replaces the old one in the Field_blob::value - now both record[1] and record[0] have a pointer that points to the *new* vcol blob value. Or record[1] has a pointer to nowhere if Field_blob::value had to realloc. To fix this I have introduced a new String object 'read_value' in Field_blob. When updating virtual columns when a row has been read, the allocated value is stored in 'read_value' instead of 'value'. The allocated blobs for the new row is stored in 'value' as before. I also made, as a safety precaution, the insert delayed handling of blobs more general by using value to store strings instead of the record. This ensures that virtual functions on delayed insert should work in as in the case of normal insert. Triggers are now properly updating the read, write and vcol maps for used fields. This means that we don't need VCOL_UPDATE_FOR_READ_WRITE anymore and there is no need for any other special handling of triggers in update_virtual_fields(). To be able to test how many times virtual fields are invoked, I also relaxed rules that one can use local (@) variables in DEFAULT and non persistent virtual field expressions.
2016-12-30 11:07:44 +02:00
#
# Examine the number of times triggers are recalculated for updates
#
SET sql_mode = 'NO_ENGINE_SUBSTITUTION';
New simpler bugfix for UPDATE and virtual BLOBs When updating a table with virtual BLOB columns, the following might happen: - an old record is read from the table, it has no virtual blob values - update_virtual_fields() is run, vcol blob gets its value into the record. But only a pointer to the value is in the table->record[0], the value is in Field_blob::value String (but it doesn't have to be! it can be in the record, if the column is just a copy of another columns: ... b VARCHAR, c BLOB AS (b) ...) - store_record(table,record[1]), old record now is in record[1] - fill_record() prepares new values in record[0], vcol blob is updated, new value replaces the old one in the Field_blob::value - now both record[1] and record[0] have a pointer that points to the *new* vcol blob value. Or record[1] has a pointer to nowhere if Field_blob::value had to realloc. To fix this I have introduced a new String object 'read_value' in Field_blob. When updating virtual columns when a row has been read, the allocated value is stored in 'read_value' instead of 'value'. The allocated blobs for the new row is stored in 'value' as before. I also made, as a safety precaution, the insert delayed handling of blobs more general by using value to store strings instead of the record. This ensures that virtual functions on delayed insert should work in as in the case of normal insert. Triggers are now properly updating the read, write and vcol maps for used fields. This means that we don't need VCOL_UPDATE_FOR_READ_WRITE anymore and there is no need for any other special handling of triggers in update_virtual_fields(). To be able to test how many times virtual fields are invoked, I also relaxed rules that one can use local (@) variables in DEFAULT and non persistent virtual field expressions.
2016-12-30 11:07:44 +02:00
CREATE TABLE t1 (
a INTEGER UNSIGNED NULL DEFAULT NULL,
b CHAR(10) NULL DEFAULT NULL,
c blob NULL DEFAULT NULL,
blob_a blob GENERATED ALWAYS AS (last_value(@a:=@a+1,a)) VIRTUAL,
blob_b blob GENERATED ALWAYS AS (last_value(@b:=@b+1,b)) VIRTUAL,
blob_c blob GENERATED ALWAYS AS (last_value(@c:=@c+1,c)) VIRTUAL
);
CREATE TRIGGER t1_ins
BEFORE INSERT
ON t1
FOR EACH ROW
BEGIN
IF NEW.b IS NULL THEN
SET NEW.b="generated before insert";
END IF;
END |
CREATE TRIGGER t1_update
BEFORE UPDATE
ON t1
FOR EACH ROW
BEGIN
IF NEW.b IS NULL or NEW.c IS NULL THEN
SET NEW.b="generated before update";
SET NEW.c="generated before update";
END IF;
END |
# Inserts
set @a=0,@b=0,@c=0;
insert into t1 (a) values(1);
insert into t1 (a,b) values(2, "*2*");
insert into t1 (a,b,c) values(3, "*3*", "**3**");
insert into t1 (a,c) values(4, "**4**");
select * from t1;
a b c blob_a blob_b blob_c
1 generated NULL 1 generated NULL
2 *2* NULL 2 *2* NULL
3 *3* **3** 3 *3* **3**
4 generated **4** 4 generated **4**
select @a,@b,@c;
@a @b @c
4 4 4
select * from t1;
a b c blob_a blob_b blob_c
1 generated NULL 1 generated NULL
2 *2* NULL 2 *2* NULL
3 *3* **3** 3 *3* **3**
4 generated **4** 4 generated **4**
select @a,@b,@c;
@a @b @c
8 8 8
select a,b,c from t1;
a b c
1 generated NULL
2 *2* NULL
3 *3* **3**
4 generated **4**
select @a,@b,@c;
@a @b @c
8 8 8
select a,b,c,blob_a from t1;
a b c blob_a
1 generated NULL 1
2 *2* NULL 2
3 *3* **3** 3
4 generated **4** 4
select @a,@b,@c;
@a @b @c
12 8 8
# updates
set @a=0,@b=0,@c=0;
update t1 set a=a+100 where a=1;
update t1 set a=a+100, b="*102*" where a=2;
update t1 set a=a+100, b=NULL where a=3;
update t1 set a=a+100, b="invisible", c=NULL where a=4;
select @a,@b,@c;
@a @b @c
0 0 0
select * from t1;
a b c blob_a blob_b blob_c
101 generated generated before update 101 generated generated before update
102 generated generated before update 102 generated generated before update
103 generated generated before update 103 generated generated before update
104 generated generated before update 104 generated generated before update
drop trigger t1_ins;
drop trigger t1_update;
drop table t1;
SET sql_mode = DEFAULT;
New simpler bugfix for UPDATE and virtual BLOBs When updating a table with virtual BLOB columns, the following might happen: - an old record is read from the table, it has no virtual blob values - update_virtual_fields() is run, vcol blob gets its value into the record. But only a pointer to the value is in the table->record[0], the value is in Field_blob::value String (but it doesn't have to be! it can be in the record, if the column is just a copy of another columns: ... b VARCHAR, c BLOB AS (b) ...) - store_record(table,record[1]), old record now is in record[1] - fill_record() prepares new values in record[0], vcol blob is updated, new value replaces the old one in the Field_blob::value - now both record[1] and record[0] have a pointer that points to the *new* vcol blob value. Or record[1] has a pointer to nowhere if Field_blob::value had to realloc. To fix this I have introduced a new String object 'read_value' in Field_blob. When updating virtual columns when a row has been read, the allocated value is stored in 'read_value' instead of 'value'. The allocated blobs for the new row is stored in 'value' as before. I also made, as a safety precaution, the insert delayed handling of blobs more general by using value to store strings instead of the record. This ensures that virtual functions on delayed insert should work in as in the case of normal insert. Triggers are now properly updating the read, write and vcol maps for used fields. This means that we don't need VCOL_UPDATE_FOR_READ_WRITE anymore and there is no need for any other special handling of triggers in update_virtual_fields(). To be able to test how many times virtual fields are invoked, I also relaxed rules that one can use local (@) variables in DEFAULT and non persistent virtual field expressions.
2016-12-30 11:07:44 +02:00
#
# Same test, but with virtual keys
#
SET sql_mode = 'NO_ENGINE_SUBSTITUTION';
New simpler bugfix for UPDATE and virtual BLOBs When updating a table with virtual BLOB columns, the following might happen: - an old record is read from the table, it has no virtual blob values - update_virtual_fields() is run, vcol blob gets its value into the record. But only a pointer to the value is in the table->record[0], the value is in Field_blob::value String (but it doesn't have to be! it can be in the record, if the column is just a copy of another columns: ... b VARCHAR, c BLOB AS (b) ...) - store_record(table,record[1]), old record now is in record[1] - fill_record() prepares new values in record[0], vcol blob is updated, new value replaces the old one in the Field_blob::value - now both record[1] and record[0] have a pointer that points to the *new* vcol blob value. Or record[1] has a pointer to nowhere if Field_blob::value had to realloc. To fix this I have introduced a new String object 'read_value' in Field_blob. When updating virtual columns when a row has been read, the allocated value is stored in 'read_value' instead of 'value'. The allocated blobs for the new row is stored in 'value' as before. I also made, as a safety precaution, the insert delayed handling of blobs more general by using value to store strings instead of the record. This ensures that virtual functions on delayed insert should work in as in the case of normal insert. Triggers are now properly updating the read, write and vcol maps for used fields. This means that we don't need VCOL_UPDATE_FOR_READ_WRITE anymore and there is no need for any other special handling of triggers in update_virtual_fields(). To be able to test how many times virtual fields are invoked, I also relaxed rules that one can use local (@) variables in DEFAULT and non persistent virtual field expressions.
2016-12-30 11:07:44 +02:00
CREATE TABLE t1 (
a INTEGER UNSIGNED NULL DEFAULT NULL,
b CHAR(10) NULL DEFAULT NULL,
c blob NULL DEFAULT NULL,
blob_a blob GENERATED ALWAYS AS (a) VIRTUAL,
blob_b blob GENERATED ALWAYS AS (RTRIM(b)) VIRTUAL,
New simpler bugfix for UPDATE and virtual BLOBs When updating a table with virtual BLOB columns, the following might happen: - an old record is read from the table, it has no virtual blob values - update_virtual_fields() is run, vcol blob gets its value into the record. But only a pointer to the value is in the table->record[0], the value is in Field_blob::value String (but it doesn't have to be! it can be in the record, if the column is just a copy of another columns: ... b VARCHAR, c BLOB AS (b) ...) - store_record(table,record[1]), old record now is in record[1] - fill_record() prepares new values in record[0], vcol blob is updated, new value replaces the old one in the Field_blob::value - now both record[1] and record[0] have a pointer that points to the *new* vcol blob value. Or record[1] has a pointer to nowhere if Field_blob::value had to realloc. To fix this I have introduced a new String object 'read_value' in Field_blob. When updating virtual columns when a row has been read, the allocated value is stored in 'read_value' instead of 'value'. The allocated blobs for the new row is stored in 'value' as before. I also made, as a safety precaution, the insert delayed handling of blobs more general by using value to store strings instead of the record. This ensures that virtual functions on delayed insert should work in as in the case of normal insert. Triggers are now properly updating the read, write and vcol maps for used fields. This means that we don't need VCOL_UPDATE_FOR_READ_WRITE anymore and there is no need for any other special handling of triggers in update_virtual_fields(). To be able to test how many times virtual fields are invoked, I also relaxed rules that one can use local (@) variables in DEFAULT and non persistent virtual field expressions.
2016-12-30 11:07:44 +02:00
blob_c blob GENERATED ALWAYS AS (c) VIRTUAL,
key (a),
key (blob_a(10)),
key (blob_b(10)),
key (blob_c(10))
);
CREATE TRIGGER t1_ins
BEFORE INSERT
ON t1
FOR EACH ROW
BEGIN
IF NEW.b IS NULL THEN
SET NEW.b="generated before insert";
END IF;
END |
CREATE TRIGGER t1_update
BEFORE UPDATE
ON t1
FOR EACH ROW
BEGIN
IF NEW.b IS NULL or NEW.c IS NULL THEN
SET NEW.b="generated before update";
SET NEW.c="generated before update";
END IF;
END |
# Inserts
insert into t1 (a) values(1);
insert into t1 (a,b) values(2, "*2*");
insert into t1 (a,b,c) values(3, "*3*", "**3**");
insert into t1 (a,c) values(4, "**4**");
select * from t1;
a b c blob_a blob_b blob_c
1 generated NULL 1 generated NULL
2 *2* NULL 2 *2* NULL
3 *3* **3** 3 *3* **3**
4 generated **4** 4 generated **4**
select @a,@b,@c;
@a @b @c
4 4 4
select * from t1;
a b c blob_a blob_b blob_c
1 generated NULL 1 generated NULL
2 *2* NULL 2 *2* NULL
3 *3* **3** 3 *3* **3**
4 generated **4** 4 generated **4**
select @a,@b,@c;
@a @b @c
4 4 4
select a,b,c from t1;
a b c
1 generated NULL
2 *2* NULL
3 *3* **3**
4 generated **4**
select @a,@b,@c;
@a @b @c
4 4 4
select a,b,c,blob_a from t1;
a b c blob_a
1 generated NULL 1
2 *2* NULL 2
3 *3* **3** 3
4 generated **4** 4
select @a,@b,@c;
@a @b @c
4 4 4
# updates
update t1 set a=a+100 where a=1;
update t1 set a=a+100, b="*102*" where a=2;
update t1 set a=a+100, b=NULL where a=3;
update t1 set a=a+100, b="invisible", c=NULL where a=4;
select * from t1;
a b c blob_a blob_b blob_c
101 generated generated before update 101 generated generated before update
102 generated generated before update 102 generated generated before update
103 generated generated before update 103 generated generated before update
104 generated generated before update 104 generated generated before update
drop trigger t1_ins;
drop trigger t1_update;
drop table t1;
SET sql_mode = DEFAULT;