Once considered a novelty, object oriented systems have now entered the mainstream. Their impressive performance and rich type systems have created a demand for object oriented features in other areas, such as relational database systems. We believe the current efforts to combine object oriented and relational features into a single hybrid system will fall short of the mark, whereas our approach, the co-existence approach, has the distinction of requiring far less work, but at the same time promising both the desired functionality and performance. We describe the attributes of our co-existing systems, an object oriented system (C++) and a relational system (Starburst), and show how this combination supports the desired features of both object-oriented and relational systems.

The authors present a version model for CAD purposes and its implementation on the basis of a complex-object database management system. The functionality of the model is illustrated with the help of a VLSI design example. In contrast to similar solutions based on the relational data model, this approach allows for a simple and efficient implementation of the version model, allowing for powerful retrieval operations. Sharing of data, which occurs necessarily among versions, is system controlled. This prohibits redundant storage of data. It is concluded that implementing a complex-object database system supporting versions is not more complicated than implementing a complex-object database system without version support.>

PRIMA is a non-standard database system developed at the University Kaiserslautern. Its major purpose is the support of engineering design applications, such as VLSI design and software engineering. The applications require tailored application-dependent interfaces which, however, all share basic notions like that of a composite object. Hence, the approach of PRIMA is to offer an application-independent complex-object interface (the moleculeatom data model, shortly called MAD model) and to provide means to easily augment this interface by application-dependent functionality. In the following, we will concentrate on the MAD model and its implementation.

Support for temporal data continues to be a requirement posed by many applications such as VLSI design and CAD, but also in conventional applications like banking and sales. Furthermore, the strong demand for complex-object support is known as an inherent fact in design applications, and also emerges for advance “conventional” applications. Thus, new advanced database management systems should include both features, i.e. should support temporal complex-objects. In this paper, we present such a temporal complex-object data model. The central notion of our temporal complex-object data model is a time slice, representing one state of a complex object. We explain the mapping of time slices onto the complex objects supported by the MAD model (which we use for an example of a non-temporal complex-object data model) as well as the transformation process of operations on temporal complex-objects into MAD model operations. Thereby, the basic properties of the MAD model are a prerequisite for our approach. For example, time slices can only be directly stored, if non-disjunct (i.e. over-lapping) complex objects are easily handled in the underlying complex-object data model.