Developing Time-Oriented Database Applications in SQL
An enjoyable plunge into the how-to of time and data, with real-world situations and code.
TABLE OF CONTENTS Developing Time-Oriented Database Applications in SQL
Glossary
- A.D.
- anno Domini, "in the year of our Lord".
- after-image
- The new value of a modified row or column.
- A.H.
- anno Hegirae, the first year of the Hijri (Islamic) calendar
- A.M.
- (1) annus mundi, or "year of the world". 6000 A.M. started October 27, 1997. (2) ante meridiem, or "before noon."
- append-only
- A property of tables with transaction-time support, in which changes are implemented only as insertions, or changing the transaction-stop time to "now," so that the changes always accummulate in the table.
- archival store
- The component of a temporally partitioned transaction-time state table containing rows that have been corrected, that is, rows with a transaction-time stop date before "now".
- as-of date
- The (transaction-time) date for which a prior state of a monitored table is to be reconstructed.
- atom
- There are 22,500 atoms in an hour, so a second is exactly 6 1/4 atoms.
- atomic second
- 9,192,631,770 periods of the radiation emitted by the transtition between two particular hyperfine states of the cesium 133 atom in the ground state.
- A.U.C.
- ab urbe condita, or "from the foundation of the city". A.U.C. was the prevailing year numbering system before the use of B.C.-A.D. 1 A.D. is 754 A.U.C.
- backlog
- A tracking log with the modification operation explicitly identified.
- B.C.
- An acronym...
This glossary is an extension of the official one, which is in two parts, general concepts [49] and time granularity concepts [7].
The page in which the term is defined is indicated in parentheses.
Copyright Morgan Kaufmann Publishers, Inc. 2000 under license agreement with Books24x7
