[MDEV-12894] System-versioned tables Created: 2017-05-24  Updated: 2021-10-29  Resolved: 2018-01-17

Status: Closed
Project: MariaDB Server
Component/s: Versioned Tables
Fix Version/s: 10.3.4

Type: Task Priority: Critical
Reporter: Sergei Golubchik Assignee: Sergei Golubchik
Resolution: Fixed Votes: 1
Labels: 10.3-beta

Issue Links:
Blocks
is blocked by MDEV-10177 Invisible columns Closed
Duplicate
duplicates MDEV-12739 Preserve data in a non-rewriteable an... Closed
PartOf
includes MDEV-14556 inconsistent NOW behavior DEFAULT/ASOF Open
Problem/Incident
causes MDEV-26928 Column-inclusive WITH SYSTEM VERSIONI... Closed
causes MDEV-26934 ADD SYSTEM VERSIONING and modify colu... Open
causes MDEV-26993 Add system versioning via modify colu... Open
causes MDEV-26994 Transaction-precise tables ignore mos... Stalled
Relates
relates to MDEV-14660 Assertion failure in lock_move_rec_li... Closed
relates to MDEV-14825 Assertion `col->ord_part' in row_buil... Closed
Sprint: 10.3.1-1, 10.3.1-2, 10.1.30

 Description   

Implement support for "System-versioned tables" as in SQL:2016.

Clauses PERIOD SYSTEM_TIME, WITH SYSTEM VERSIONING, FOR SYSTEM_TIME AS OF, FOR SYSTEM_TIME BETWEEN ... AND, FOR SYSTEM_TIME FROM ... TO.

 Comments   
Comment by Sergei Golubchik [ 2017-12-04 ]

Assorted notes:

  • SQL Standard only has FOR SYSTEM_TIME with AS OF ...| FROM ... TO ...| BETWEEN ... AND ... and it can only directly follow a table name in the FROM clause. Does not apply to a view, does not apply to a query as a whole. Whenever FOR SYSTEM_TIME is missing, FOR SYSTEM_TIME AS OF CURRENT_TIMESTAMP is implied.
  • SQL Server has FOR SYSTEM_TIME ALL
  • DB2 supports FOR SYSTEM_TIME for views, if these views use system-versioned tables and do not use FOR SYSTEM_TIME inside.
  • DB2 has a session setting like SET CURRENT TEMPORAL SYSTEM_TIME = current timestamp – 1 MONTH
Generated at Thu Feb 08 08:01:19 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.