2009•Unpublished venueRequires access

On implementing temporal coalescing in temporal databases implemented on top of relational database systems

K. Unnikrishnan, K Varshney Pramod

Open publisher page 2 citations

Abstract

A feasible way of implementing a temporal database is by mapping temporal features onto a conventional commercial database management system. In this paper an analysis of different possible ways of implementing coalescing operator of temporal databases by mapping the temporal data model into the underlying relational model followed by Oracle is done. The temporal time-stamps, implicit in the temporal database, are represented as explicit attributes. The advantages of the two methods of implementing coalescing operator in this work are they are based on currently available standards and there is no requirements for making any extensions to the existing standards other than adding explicit attributes for the implicit attributes of the temporal data model. One strategy is based on SQL: 92 standards and another one is based on functions provided by SQL 2003 approach. A comparative study shows the method based on SQL 2003 approach is better in performance than the other method.

About this research paper

What this paper is about

A feasible way of implementing a temporal database is by mapping temporal features onto a conventional commercial database management system. In this paper an analysis of different possible ways of implementing coalescing operator of temporal databases by mapping the temporal data model into the underlying relational model followed by Oracle is done. The temporal time-stamps, implicit in the temporal database, are represented as explicit attributes. The advantages of the two methods of implementing coalescing operator in this work are they are based on currently available standards and there is no requirements for making any extensions to the existing standards other than adding explicit attributes for the implicit attributes of the temporal data model. One strategy is based on SQL: 92 standards and another one is based on functions provided by SQL 2003 approach. A comparative study shows the method based on SQL 2003 approach is better in performance than the other method.

Why it matters

OpenAlex reports 2 citations for this work. Citation counts describe recorded attention and do not establish research quality.

Key contribution

A contribution statement is not available in the OpenAlex record.

Method / approach

Method details are not available in the OpenAlex metadata.

Main findings

Findings are not separately available in the OpenAlex metadata.

Limitations

Limitations are not available in the OpenAlex metadata.

Applications

Application details are not available in the OpenAlex metadata.

Available abstract

A feasible way of implementing a temporal database is by mapping temporal features onto a conventional commercial database management system. In this paper an analysis of different possible ways of implementing coalescing operator of temporal databases by mapping the temporal data model into the underlying relational model followed by Oracle is done. The temporal time-stamps, implicit in the temporal database, are represented as explicit attributes. The advantages of the two methods of implementing coalescing operator in this work are they are based on currently available standards and there is no requirements for making any extensions to the existing standards other than adding explicit attributes for the implicit attributes of the temporal data model. One strategy is based on SQL: 92 standards and another one is based on functions provided by SQL 2003 approach. A comparative study shows the method based on SQL 2003 approach is better in performance than the other method.

Key concepts: Computer science, Temporal database, SQL, Database, Relational database, Oracle, Database model, Data modeling

Related papers

Back to paper searchBrowse research topicsOriginal source
On implementing temporal coalescing in temporal databases implemented on top of relational database systems — Research Paper | ScholarLens