A 2-dimensional temporal relational database model for querying errors and updates, and for achieving zero information-loss

An XML-based implementation of the parametric model for ad-hoc query of temporal and spatiotemporal data

“…A temporal database is capable of storing evolution of data, thereby allowing users to examine complete object histories [7]. Applications of temporal databases include financial, record-keeping, and scientific applications [29].…”

“…ParaSQL simply expresses the query by restricting the tuple of the fire to the starting time instant using the function StartTime. The domain of the fire is restricted to a 7 The original query in [25] assumes that a fire can start at different time with different initial regions. However, SQL st query introduced in [9] implicitly assumes that a fire started at a single time instant.…”

“…Since a tuplet is the part of a parametric tuple, it is not necessary to evaluate the tuplet if the previous tuplet has been already qualified. If this is not the case, the second step is to check whether the expression node is a unary node (line [5][6][7][8][9][10][11][12]. If this is the case, the expression node is a terminal node.…”

An XML-based implementation of the parametric model for ad-hoc query of temporal and spatiotemporal data

“…Finding the minimum valid time instant can be expressed as a nested query in the WHERE clause. 7 The STSQL query consists of three parts. First, it extracts all extents of the fire.…”

A relational model for incomplete information in temporal databases

“…We note that the fact that the £ values (and the u values) are the same for each attribute in a tuple allows us to simplify the syntax of these operations as well as the description of the semantics. Our update operations generalize the update operations in [Bh89] for temporal databases with complete information.…”