Are you an EPFL student looking for a semester project?
Work with us on data science and visualisation projects, and deploy your project as an app on top of Graph Search.
Concept
Temporal database
Summary
A temporal database stores data relating to time instances. It offers temporal data types and stores information relating to past, present and future time.
Temporal databases can be uni-temporal, bi-temporal or tri-temporal.
More specifically the temporal aspects usually include valid time, transaction time or decision time.
Valid time is the time period during or event time at which a fact is true in the real world.
Transaction time is the time at which a fact was recorded in the database.
Decision time is the time at which the decision was made about the fact.
A uni-temporal database has one axis of time, either the validity range or the system time range.
A bi-temporal database has two axes of time:
valid time
transaction time or decision time
A tri-temporal database has three axes of time:
valid time
transaction time
decision time
This approach introduces additional complexities.
Temporal databases are in contrast to current databases (not to be confused with currently available databases), which store only facts which are believed to be true at the current time.
Temporal databases support managing and accessing temporal data by providing one or more of the following features:
A time period datatype, including the ability to represent time periods with no end (infinity or forever)
The ability to define valid and transaction time period attributes and bitemporal relations
System-maintained transaction time
Temporal primary keys, including non-overlapping period constraints
Temporal constraints, including non-overlapping uniqueness and referential integrity
Update and deletion of temporal records with automatic splitting and coalescing of time periods
Temporal queries at current time, time points in the past or future, or over durations
Predicates for querying time periods, often based on Allen's interval relations
With the development of SQL and its attendant use in real-life applications, database users realized that when they added date columns to key fields, some issues arose.
Official source
About this result
This page is automatically generated and may contain information that is not correct, complete, up-to-date, or relevant to your search query. The same applies to every other page on this website. Please make sure to verify the information with EPFL's official sources.
Ontological neighbourhood