[MDEV-29750] Triggers can modify history Created: 2022-10-08  Updated: 2022-12-27  Resolved: 2022-12-27

Status: Closed
Project: MariaDB Server
Component/s: Triggers, Versioned Tables
Affects Version/s: 10.3, 10.4, 10.5, 10.6, 10.7, 10.8, 10.9, 10.10
Fix Version/s: 10.3.37, 10.4.27, 10.5.18, 10.6.11, 10.7.7, 10.8.6, 10.9.4, 10.10.2

Type: Bug Priority: Critical
Reporter: Elena Stepanova Assignee: Sergei Golubchik
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Problem/Incident
is caused by MDEV-16546 System versioning setting to allow hi... Closed
Relates
relates to MDEV-16029 mysqldump: dump and restore historica... Closed

 Description   

create table t (a int, s timestamp(6) as row start, e timestamp(6) as row end, period for system_time(s,e)) with system versioning;
insert into t values (1,'2022-01-01','2023-01-01');
create trigger tr before insert on t for each row set new.s = '2022-01-01', new.e = '2023-01-01';
insert into t (a) values (1);
select * from t for system_time all;
 
# Cleanup
drop table t;

bb-10.11-MDEV-16546 2b1d32429

create table t (a int, s timestamp(6) as row start, e timestamp(6) as row end, period for system_time(s,e)) with system versioning;
create trigger tr before insert on t for each row set new.s = '2022-01-01', new.e = '2023-01-01';
insert into t (a) values (1);
select * from t for system_time all;
a	s	e
1	2022-01-01 00:00:00.000000	2023-01-01 00:00:00.000000
drop table t;


Generated at Thu Feb 08 10:11:01 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.