Valid time: Difference between revisions
Appearance
Content deleted Content added
No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
{{unreferenced|date=November 2008}} |
{{unreferenced|date=November 2008}} |
||
'''Valid time''' (VT), a concept originated by [[Richard T. Snodgrass]] and his doctoral student, is used in [[temporal database]]s.<ref> Richard T. Snodgrass and Ilsoo Ahn, "Temporal Databases," IEEE Computer 19(9), September, 1986, pp. 35–42.</ref> It denotes the time period during which a database fact was, is, or will be valid in the modeled reality. |
'''Valid time''' (VT), a concept originated by [[Richard T. Snodgrass]] and his doctoral student, is used in [[temporal database]]s. |
||
<ref> Richard T. Snodgrass and Ilsoo Ahn, "Temporal Databases," IEEE Computer 19(9), September, 1986, pp. 35–42.</ref> It denotes the time period during which a database fact was, is, or will be valid in the modeled reality. |
|||
In a database table valid time is often represented by two extra table-columns ''StartVT'' and ''EndVT''. The time interval is closed at its [[lower bound]] and open at its [[upper bound]]. |
In a database table valid time is often represented by two extra table-columns ''StartVT'' and ''EndVT''. The time interval is closed at its [[lower bound]] and open at its [[upper bound]]. |
Revision as of 00:02, 29 April 2010
Valid time (VT), a concept originated by Richard T. Snodgrass and his doctoral student, is used in temporal databases. [1] It denotes the time period during which a database fact was, is, or will be valid in the modeled reality.
In a database table valid time is often represented by two extra table-columns StartVT and EndVT. The time interval is closed at its lower bound and open at its upper bound.
See also
References
valid time and transaction time are two different apspects in designing a database
- ^ Richard T. Snodgrass and Ilsoo Ahn, "Temporal Databases," IEEE Computer 19(9), September, 1986, pp. 35–42.