Hi, Aleksey! On Feb 25, Aleksey Midenkov wrote: > > On Nov 24, Aleksey Midenkov wrote: > > > 1. Add server variable system_versioning_insert_history which will > > > allow INSERT history rows. > > > 2. If secure_timestamp is YES or REPLICATION, > > > system_versioning_insert_history does not have effect. If > > > secure_timestamp is SUPER, system_versioning_insert_history > > > requires special privilege (same as for setting current > > > timestamp). > > > > Yes. It is correct, but could be expressed simpler: > > > > when @@system_versioning_insert_history=TRUE, one can directly insert > > into row_start/row_end columns iff one can set @@timestamp variable. > > > > In other words, if one can create an arbitrary history by > > manipulating @@timestamp variable, > > @@system_versioning_insert_history allows to do it more > > conveniently. But if one cannot - he cannot. > > Then do we need additional setting @@system_versioning_insert_history? > Iff one can manipulate history via @@timestamp variable let him set > row_start/row_end columns.
Sure, that's possible. I just thought @@system_versioning_insert_history could be like an extra safety (not security) measure. To prevent history from being modified unintentionally. Regards, Sergei VP of MariaDB Server Engineering and secur...@mariadb.org _______________________________________________ Mailing list: https://launchpad.net/~maria-developers Post to : maria-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-developers More help : https://help.launchpad.net/ListHelp