Abstract
AbstractA temporal database stores time‐varying data and has the capabilities to manipulate it. Two commonly used time dimensions for maintaining temporal data are valid time and transaction time. Temporal databases are classified as valid time, transaction time, or bitmeporal databases. Temporality in databases involve subtle issues like comparing database states at different times, temporal grouping, different ways to represent the same temporal data, consistency of the timestamps of different attributes, temporal integrity constraints, and designing temporal databases. A temporal atom is a timestamp and value pair in which The timestamp is valid and/or transaction time and value are the time‐varying data. For representing and manipulating temporal data, data models handle temporal atoms differently. In relational data model, which is the focus of this entry, attribute or tuple time stamping may be used. Temporal algebra and temporal calculus languages are defined accordingly. Proposals for extending SQL2 for temporal data manipulation exist, and SQl3 supports user‐defined data types that can be used for defining and manipulating temporal data. This entry covers temporal query languages and the temporal issues mentioned above.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
