Today’s question: can I design a table that takes advantage of the new Temporal Validity feature in Oracle Database 12c?

Today’s answer: ‘Yes.’

In a nutshell:

Temporal Validity Support lets you associate one or more valid time dimensions with a table and have data be visible depending on its time-based validity, as determined by the start and end dates or time stamps of the period for which a given record is considered valid. Examples of time-based validity are the hire and termination dates of an employee in a Human Resources application, the effective date of coverage for an insurance policy, and the effective date of a change of address for a customer or client. [DOCS]

There’s a property in the Table editor that allows you to define the start and end times required to specify the ‘temporal validity’ of your data.

You can find better examples and sample SQL to play with this in the aforementioned DOCS link.
You can find better examples and sample SQL to play with this in the aforementioned DOCS link.

Note that I’m running SQL Developer v4.1 connected to a 12.1.0.2 Oracle Database.

New SQL syntax to learn, VERSIONS PERIOD FOR user_valid_time BETWEEN
New SQL syntax to learn, VERSIONS PERIOD FOR user_valid_time BETWEEN

Next question?

Author

I'm a Distinguished Product Manager at Oracle. My mission is to help you and your company be more efficient with our database tools.

3 Comments

    • hachemi.z

      the simple point is that the ‘temporal validity’ is more “visible” in sqldeveloper data modeler than in sqldeveloper;

      … and it’s like ‘a litte nudge’ to enjoy reading the next post about it !

Write A Comment