Scribd
Upload
197 views

Seminar Dbms

A temporal database stores data related to time, including valid time (when facts are true), transaction time (when facts were known), and decision time (when facts were decided). Temporal databases can be uni-temporal (one time axis), bi-temporal (valid and transaction times), or tri-temporal (all three times). They allow querying of data at past/future times and over durations, unlike non-temporal databases that only store current data.

Uploaded by

Aishu elango
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
197 views

Seminar Dbms

A temporal database stores data related to time, including valid time (when facts are true), transaction time (when facts were known), and decision time (when facts were decided). Temporal databases can be uni-temporal (one time axis), bi-temporal (valid and transaction times), or tri-temporal (all three times). They allow querying of data at past/future times and over durations, unlike non-temporal databases that only store current data.

Uploaded by

Aishu elango
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 5

INTRODUCTION:

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 could 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 which a fact is true in the real world.
 Transaction time is the time period during which a fact stored in the database
was known.
 Decision time is the time period during which a fact stored in the database was
decided to be valid.

Uni-Temporal
A uni-temporal database has one axis of time, either the validity range or the
system time range.

Bi-Temporal

A bi-temporal database has two axis of time.


 valid time.
 transaction time or decision time.

Tri-Temporal
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.
TYPES :
 Non-Temporal Databases
 Temporal Databases
 Different Forms of Temporal Databases

Non-Temporal Databases:

Commercial database management systems (DBMS) such as Oracle, Sybase,


Informix and O2 allow the storage of huge amounts of data. This data is usually
considered to be valid now. Past or future data is not stored. Past data refers to
data which was stored in the database at an earlier time instant and which might
has been modified or deleted in the meantime. Past data usually is overwritten
with new (updated) data. Future data refers to data which is considered to be
valid at a future time instant

A DBMS stores the data in a well-defined format. A relational DBMS, for


example, stores data in tables (also called relations). Thus, a relational database
actually contains a set of tables. Each table contains rows (tuples) and columns
(attributes). A row contains data about a specific entity, for example, an
employee. Each column specifies a certain property of these entities, for
example, the employee's name, salary etc. The following table stores data about
employees:

EmpID Name Department Salary


10 John Sales 12000
12 George Research 10500
13 Ringo Sales 15500

Object-oriented DBMS store data about entities in objects. So each employee is


actually an object. The type of an object specifies the properties the object has.
An employee object thus has properties such as a name, a salary etc. Sets of
objects of the same type are called collections. Thus - in an object-oriented DBMS
- a database contains a set of collections.
Different Forms of Temporal Databases

The two different notions of time - valid time and transaction time - allow the
distinction of different forms of temporal databases. A historical database stores
data with respect to valid time, a rollback database stores data with respect to
transaction time. A bitemporal database stores data with respect to both valid
time and transaction time.

As we mentioned above, commercial DBMS are said to store only a single state
of the real world, usually the most recent state. Such databases usually are
called snapshot databases. A snapshot database in the context of valid time and
transaction time is depicted in the following picture:

On the other hand, a bitemporal DBMS such as TimeDB stores the history of
data with respect to both valid time and transaction time. Note that the history of
when data was stored in the database (transaction time) is limited to past and
present database states, since it is managed by the system directly which does not
know anything about future states.

A table in the bitemporal relational DBMS TimeDB may either be a snapshot


table (storing only current data), a valid-time table (storing when the data is valid
wrt. the real world), a transaction-time table (storing when the data was recorded
in the database) or a bitemporal table (storing both valid time and transaction
time). An extended version of SQL allows to specify which kind of table is
needed when the table is created. Existing tables may also be altered (schema
versioning). Additionally, it supports temporal queries, temporal modification
statements and temporal constraints.

The states stored in a bitemporal database are sketched in the picture below. Of
course, a temporal DBMS such as TimeDB does not store each database state
separately as depicted in the picture below. It stores valid time and/or transaction
time for each tuple, as described above.
Features
Temporal databases support managing and accessing temporal data by providing
one or more of the following features:[1][2]
 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

You might also like