1992
DOI: 10.1093/comjnl/35.4.332
|View full text |Cite
|
Sign up to set email alerts
|

Modelling and Managing Time in Database Systems

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...

Citation Types

0
1
0

Year Published

1994
1994
1999
1999

Publication Types

Select...
4
1

Relationship

0
5

Authors

Journals

citations
Cited by 5 publications
(1 citation statement)
references
References 8 publications
0
1
0
Order By: Relevance
“…This evolution takes place both at tuple level and schema level. Generally, database systems support the notion of non-temporal evolution of tuples and schema to accommodate changes in the state and structure of an object using the concept of "current view" only (Hurson, 1993;Ling, 1992;Pissinou, 1993;Shoshani, 1984). In these databases, only existing data values are kept using the available schema definitions, and therefore, direct access to past information is not available.…”
mentioning
confidence: 99%
“…This evolution takes place both at tuple level and schema level. Generally, database systems support the notion of non-temporal evolution of tuples and schema to accommodate changes in the state and structure of an object using the concept of "current view" only (Hurson, 1993;Ling, 1992;Pissinou, 1993;Shoshani, 1984). In these databases, only existing data values are kept using the available schema definitions, and therefore, direct access to past information is not available.…”
mentioning
confidence: 99%