Details

    • 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.

      Attachments

        Issue Links

          Activity

            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
            serg Sergei Golubchik added a comment - 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

            People

              serg Sergei Golubchik
              serg Sergei Golubchik
              Votes:
              1 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.