TSQL2 language specification

Snodgrass, Richard T.; Ahn, Ilsoo; Ariav, G.; Batory, Don; Clifford, James; Dyreson, Curtis E.; Elmasri, Ramez; Grandi, Fábio; Jensen, Christian S.; Käfer, Wolfgang; Kline, Nick; Kulkarni, Krishna; Leung, T. Y. Cliff; Lorentzos, Nikos A.; Roddick, John F.; Segev, Arie; Soo, Michael D.; Sripada, Suryanarayana M.

doi:10.1145/181550.181562

Cited by 124 publications

(60 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…In accordance with a common syntax adopted for temporal query languages (e.g. TSQL2 [35]), each elementary predicate has the form "dimension [NOT] op VALUE", where NOT is an optional keyword negating the meaning of the comparison operator op, and dimension can be PUBLICATION, VALIDITY, EFFICACY or TRANSACTION, in order to specify a selection condition on the corresponding time pertinence of versions in a normative text. The kind of the operator op and the type of VALUE which can be used depends on the involved temporal dimension.…”

Section: Querying Normative Documentsmentioning

confidence: 99%

See 1 more Smart Citation

Temporal modelling and management of normative documents in XML format

Grandi

Mandreoli

Tiberio

2005

Data & Knowledge Engineering

Self Cite

View full text Add to dashboard Cite

In this paper, we present the results of a research project concerning the temporal management of normative texts in XML format. In particular, four temporal dimensions (publication, validity, efficacy and transaction times) are used to correctly represent the evolution of norms in time and their resulting versioning. Hence, we introduce a multiversion data model based on XML schema and define basic mechanisms for the maintenance and retrieval of multiversion norm texts. Finally, we describe a prototype management system which has been implemented and evaluated.

show abstract

Section: Querying Normative Documentsmentioning

confidence: 99%

“…The semantics of the operators introduced above is the standard one (i.e. the same as defined for the TSQL2 language [35]). Finally, we do not require the "temporal specs" expression to contain a temporal condition for each of the four dimensions.…”

Section: Querying Normative Documentsmentioning

confidence: 99%

Temporal modelling and management of normative documents in XML format

Grandi

Mandreoli

Tiberio

2005

Data & Knowledge Engineering

Self Cite

View full text Add to dashboard Cite

show abstract

“…In this research, we cover the modelling of both concepts to present a model which is able to store current, historical and even future data. The concepts of valid time, transaction time and bitemporal data were introduced as a part of TSQL2, a language specification, developed for temporal extensions to SQL [29]. Date [5] stated that "valid times are kept in the database, while transaction times are kept in the log" (p. 302).…”

Section: Introductionmentioning

confidence: 99%

Relational model of temporal data based on 6th normal form

Golec

Mahnič²,

Kovač

2017

Teh. vjesn.

View full text Add to dashboard Cite

Original scientific paper This paper brings together two different research areas, i.e. Temporal Data and Relational Modelling. Temporal data is data that represents a state in time while temporal database is a database with built-in support for handling data involving time. Most of temporal systems provide sufficient temporal features, but the relational models are improperly normalized, and modelling approaches are missing or unconvincing. This proposal offers advantages for a temporal database modelling, primarily used in analytics and reporting, where typical queries involve a small subset of attributes and a big amount of records. The paper defines a distinctive logical model, which supports temporal data and consistency, based on vertical decomposition and sixth normal form (6NF). The use of 6NF allows attribute values to change independently of each other, thus preventing redundancy and anomalies. Our proposal is evaluated against other temporal models and super-fast querying is demonstrated, achieved by database join elimination. The paper is intended to help database professionals in practice of temporal modelling. Keywords: logical model; relation; relational modelling; 6 th Normal Form; temporal dataRelacijski model vremenskih podataka zasnovan na 6. normalnoj formi Izvorni znanstveni članak Ovaj rad povezuje dva različita područja istraživanja, tj. Temporalne podatke i Relacijsko modeliranje. Temporalni podaci su podaci koji predstavljaju stanje u vremenu, a temporalna baza podataka je baza podataka s ugrađenom podrškom za baratanje s podacima koji uključuju vrijeme. Većina temporalnih sustava pruža dovoljno temporalnih karakteristika, ali su relacijski modeli nepravilno normalizirani, a pristupi modeliranju nedostaju ili nisu uvjerljivi. Ovim se prijedlogom daju prednosti modeliranja temporalne baze podataka, prvenstveno korištene u analitici i izvještavanju, gdje tipična pretraživanja uključuju mali podniz atributa i veliku količinu zapisa. U radu se definira posebni logički model koji podržava temporalne podatke i konzistenciju, zasnovan na vertikalnoj dekompoziciji i šestoj normalnoj formi (6NF). Primjena 6NF omogućuje neovisnost u promjeni atributnih vrijednosti i tako sprečava redundanciju i anomalije. Naš je model uspoređen s drugim temporalnim modelima i demonstrirano je super brzo pretraživanje postignuto eliminacijom spajanja baze podataka (database join elimination). Svrha je rada pomoći stručnjacima koji se bave bazama podataka u primjeni temporalnog modeliranja.

show abstract

“…A standardization effort led by Snodgrass yielded a proposal, TSQL2 [14], for a core set of additions to structured query language (SQL, the data manipulation language of RDBMSs). In 1995, efforts were made to amalgamate TSQL2's features into the forthcoming version of SQL, by adding a new component called SQL/ Temporal [15,16].…”

Section: Introductionmentioning

confidence: 99%

Temporal query of attribute-value patient data: utilizing the constraints of clinical studies

Deshpande

Brandt

Nadkarni

2003

International Journal of Medical Informatics

View full text Add to dashboard Cite

SummaryWe describe an interface and architecture for ad hoc temporal query of TrialDB, a clinical study data management system (CSDMS). A clinical study focuses primarily on the effect of therapy on a group of patients, who have individually enrolled in a study at different times. Relative times (chronological offsets from the time of enrollment) are therefore more useful than absolute times when collectively describing therapeutic or adverse events. For logistic reasons, study parameter values are typically recorded at fixed relative times ('study events'), which serve as timestamps and can be used by CSDMS temporal query algorithms to simplify temporal computations. The entity-attribute-value model of clinical data storage, used by both CSDMSs and clinical patient record systems, complicates temporal query. To apply temporal operators, data for parameters of interest must first be transiently converted into conventional relational form, with one column per parameter.

show abstract

TSQL2 language specification

Abstract: The affiliations and e-mail addresses of the TSQL2 Language Design Committee members may be found i n a seg arate section at the end of the document.

Cited by 124 publications

References 0 publications

Temporal modelling and management of normative documents in XML format

Temporal modelling and management of normative documents in XML format

Relational model of temporal data based on 6th normal form

Temporal query of attribute-value patient data: utilizing the constraints of clinical studies

Contact Info

Product

Resources

About