A temporal database is a database with built-in time aspects, for example a temporal data model and a temporal version of Structured Query Language (SQL).
More specifically the temporal aspects usually include valid-time and transaction-time. These attributes go together to form bitemporal data.
- Valid time denotes the time period during which a fact is true with respect to the real world.
- Transaction time is the time period during which a fact is stored in the database.
- Bitemporal data combines both Valid and Transaction Time.
Note that these two time periods do not have to be the same for a single fact. Imagine that we come up with a temporal database storing data about the 18th century. The valid time of these facts is somewhere between 1701 and 1800, whereas the transaction time starts when we insert the facts into the database, for example, January 21, 1998.
It is possible to have timelines other than Valid Time and Transaction Time, such as Decision Time, in the database. In that case the database would be called a multitemporal database as opposed to a bitemporal database. However, this approach introduces additional complexities such as dealing with the validity of (foreign) keys.
Read more about Temporal Database: History, Example, Implementations in Databases
Famous quotes containing the word temporal:
“When once a certain class of people has been placed by the temporal and spiritual authorities outside the ranks of those whose life has value, then nothing comes more naturally to men than murder.”
—Simone Weil (1909–1943)