Design of an Integrated DBMS to Support Advanced Applications

Lum, Vincent Y.; Dadam, Peter; Erbe, Rossin; Günauer, Jürgen; Pistor, Peter; Walch, Georg; Werner, H.; Woodfill, John

doi:10.1007/978-1-4613-1881-1_3

Cited by 9 publications

(5 citation statements)

References 2 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…entities, attributes and relationships [CHEN76] classes [HAMM81] roles [BACH77] objects with no fixed type or composition [COPE84] set valued attributes (repeating groups) [ZANI83] unnormalized relations [LUM85] class variables (aggregation) [SMIT77] category attributes and summary tables [OZSO85] molecular objects [BAT O85]…”

Section: Enriched Collection Of Objectsmentioning

confidence: 99%

Object Management in Postgres using Procedures

Stonebraker

1991

Topics in Information Systems

View full text Add to dashboard Cite

This paper presents the object management facilities being designed into a next-generation data manager, POSTGRES. This system is unique in that it does not invent a new data model for support of objects but chooses instead to extend the relational model with a powerful abstract data typing capability and procedures as full-fledged data base objects. The reasons to remain with the relational model are indicated in this paper along with the POSTGRES relational extensions.

show abstract

Section: Enriched Collection Of Objectsmentioning

confidence: 99%

Object Management in Postgres using Procedures

Stonebraker

1991

Topics in Information Systems

View full text Add to dashboard Cite

show abstract

“…Historical databases are static databases, extended to maintain information about the time during which the stored information is assumed to be valid [9]. Finally, there are hybrid temporal databases that encode both transaction time and valid time in order to support the functionality of static rollback databases and historical databases; TQUEL [42] and the work described in [30] are databases of this type.…”

Section: Related Workmentioning

confidence: 99%

Using temporal hierarchies to efficiently maintain large temporal databases

Dean

1989

J. ACM

View full text Add to dashboard Cite

Abstract. Many real-world applications involve the management of large amounts of time-dependent information. Temporal database systems maintain this information in order to support various sorts of inference (e.g., answering questions involving propositions that are true over some intervals and false over others). For any given proposition, there are typically many different occasions on which that proposition becomes true and persists for some length of time. In this paper, these occasions are referred to as time tokens. Many routine database operations must search through the database for time tokens satisfying certain temporal constraints. To expedite these operations, this paper describes a set of techniques for organizing temporal information by exploiting the local and global structure inherent in a wide class of temporal reasoning problems. The global structure of time is exemplified in conventions for partitioning time according to the calendar and the clock. This global structure is used to partition the set of time tokens to facilitate retrieval. The local structure of time;is exemplified in the causal relationships between events and the dependencies between planned activities. This local structure is used as part of a strategy for reducing the computation required during constraint propagation. The organizational techniques described in this paper are quite general, and have been used to support a variety of powerful inference mechanisms. Integrating these techniques into an existing temporal database system has increased, by an order of magnitude or more in most applications, the number of time tokens that can be efficiently handled.

show abstract

“…The valid time, for example, of an event is the clock time at which the event occurred in the real world, independent of the recording of that event in some database. Other terms found in the literature with similar meaning include intrinsic time [Bubenko, 1977], effective time [Ben-Zvi, 1982] and logical time [Dadam et al, 1984;Lum et al, 1984]. Transaction time, on the other hand, concerns the storage of information in the database.…”

Section: V) Valid Transaction and User-defined Timementioning

confidence: 99%

“…Other terms that have been used with similar meaning are extrinsic time [Bubenko, 1977], registration time [Ben-Zvi, 1982] and physical time [Dadam et al, 1984;Lum et al, 1984]. User-defined time is an uninterpreted domain for which the data model supports the operations of input, output, and perhaps comparison.…”

Section: V) Valid Transaction and User-defined Timementioning

confidence: 99%

Conceptual Modelling for Temporal Information Systems

Πετρουνιασ¹

View full text Add to dashboard Cite

Recent years have witnessed a growing realisation that the development of information systems is becoming increasingly more difficult as user requirements become broader and more sophisticated. Most of the errors that are detected in information systems can be traced to the early stages of development. Functional requirements specification formalisms require formality and rigour in order to lead to improved information systems and to describe reality in a way that is close to users' perceptions. At the same time they should include the concepts for achieving such a purpose.To this end, this thesis develops a formalism for specifying requirements for temporal information systems. The formalisms has three interrelated components: a model based on facts for defining the structural components of an application domain and which supports the explicit modelling of time and the definition of calendar systems, an algebra for that model in order to provide the ability for writing expressions about the concepts of the model and a rule language for defining the rules and constraints of the application domain and also the reaction of the information system when certain situation occur.

show abstract

Design of an Integrated DBMS to Support Advanced Applications

Cited by 9 publications

References 2 publications

Object Management in Postgres using Procedures

Object Management in Postgres using Procedures

Using temporal hierarchies to efficiently maintain large temporal databases

Conceptual Modelling for Temporal Information Systems

Contact Info

Product

Resources

About