Relational database systems with zero information loss

Bhargava, Gautam; Gadia, Shashi K.

doi:10.1109/69.204093

Cited by 34 publications

(28 citation statements)

References 9 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Buna rağmen gereksiz veri tekrarı kaçınılmazdır. Birinci normal form'da (N1NF) [10] olmayan veri tabanlarında kullanılan sütun zaman etiketleme yaklaşımı daha karmaşık olmasına karşın veri tekrarlanmasını engeller, nesneye ait bütün geçmişi pek çok satıra bölmektense bir tek satırda tutarak [11,12,13,14,15,16] satır zaman etiketleme yönteminde olan yatay ve dikey veri tekrarını engeller [11]. Ben-Zvi, çift zamanlı veri tabanları için ilk veri modelini, zamansal sorgulama dilini, depolama mimarisini, indeksleme, kurtarma, eşzamanlılık, eşleme ve uygulanmasını önermiştir [8].…”

Section: Literatüre Taramasıunclassified

An Implementation of Bitemporal Relational Database Management Systems

Atay¹

2014

Pamukkale J Eng Sci

View full text Add to dashboard Cite

Section: Literatüre Taramasıunclassified

An Implementation of Bitemporal Relational Database Management Systems

Atay¹

2014

Pamukkale J Eng Sci

View full text Add to dashboard Cite

“…Since we have a zero-information-Ioss model (i.e. no information about an object's history is deleted) (Bhargava and Gadia 1993) and the lifespans of our objects cannot have gaps, the end-time of a version of an object equals the start-time of the next version of this object minus one chronon. A chronon (Jensen et al 1994) is the shortest duration of time supported by a temporal database.…”

Section: Related Workmentioning

confidence: 99%

Modeling and Implementation of Temporal Aspects of Objects in Commercial Information Systems

Gruhn

Fegert²,

Schneider³

1998

Data Mining and Reverse Engineering

View full text Add to dashboard Cite

In this article, we discuss how temporal aspects of information systems can be modeled and implemented. We introduce extensions of an entity-relationship model which allow us to model temporal aspects. Moreover, we describe how these extended entity-relationship models are used to generate an application database which supports objects with temporarily restricted validity. We support historical objects (i.e. objects which are not valid any longer) and future objects (i.e. objects which will be valid in the future). Our approach is driven by requirements from a real-world project. In this project we had to support temporal aspects of objects in an information system supporting business processes from the area of housing construction and administration.

show abstract

“…Snodgrass proposed a temporal model that supports valid and transaction times, where tuples are time-stamped with either time instants or time intervals [6]. Bhargava and Gadia attached transaction and valid timestamps to attribute values [9]. They gave a relational algebra for their model and defined new operators to capture and update the data.…”

Section: Related Workmentioning

confidence: 99%

BtSQL: nested bitemporal relational database query language

Atay¹,

Tansel²

2014

Turk J Elec Eng & Comp Sci

View full text Add to dashboard Cite

Abstract:A nested bitemporal relational data model and its query language are implemented. The bitemporal atom (BTA) is the fundamental construct to represent temporal data and it contains 5 components: a value, the lower and upper bounds of valid time, and the lower and upper bounds of the recoding time. We consider 2 types of data structures for storing BTAs: 1) string representation and 2) abstract data-type representation. We also develop a preprocessor for translating a bitemporal structured query language (BtSQL) statement into standard SQL statements. The BtSQL includes the select, insert, delete, and update statements of the SQL, extended for bitemporal relational databases. It supports bitemporal, historical, and current context. Bitemporal context is for auditing purposes, historical context is for querying past states of a bitemporal database, and current context is for querying the snapshot state of a bitemporal database. We also evaluate the performance of the 2 alternative implementation methods by considering retrieval, insertion, and update queries.

show abstract

Relational database systems with zero information loss

Cited by 34 publications

References 9 publications

An Implementation of Bitemporal Relational Database Management Systems

An Implementation of Bitemporal Relational Database Management Systems

Modeling and Implementation of Temporal Aspects of Objects in Commercial Information Systems

BtSQL: nested bitemporal relational database query language

Contact Info

Product

Resources

About