Comparison of Post-Relational and Object-Relational modelling for real-world database applications

Abstract

Purpose – The purpose of this paper is to compare the use of two Object-Relational models against the use of a post-Relational model for a realistic application. Although real-world applications, in most cases, can be adequately modeled by the Entity-Relationship (ER) model, the transformation to the popular Relational model alters the representation of structures common in reality, like multi-valued and composite fields. Alternative database models have been developed to overcome these shortcomings. Design/methodology/approach – Based on the ER model of a medical application, this paper compares the information representation, manipulation and enforcement of integrity constraints through PostgreSQL and Oracle, against the use of a post-Relational model composed of the Conceptual Universal Database Language (CUDL) and the Conceptual Universal Database Language Abstraction Level (CAL). Findings – The CAL/CUDL pair, although more periphrastic for data definition, is simpler for data insertions, does not require the use of procedural code for data updates, produces clearer output for retrieval of attributes, can accomplish retrieval of rows based on conditions that address composite data with declarative statements and supports data validation for relationships between composite data without the need for procedural code. Research limitations/implications – To verify, in practice, the conclusions of the paper, complete implementation of a CAL/CUDL system is needed. Practical implications – The use of the CAL/CUDL pair would advance the productivity of database application development. Originality/value – This paper highlights the properties of realistic database-applications modelling and management that are desirable by developers and shows that these properties are better satisfied by the CAL/CUDL pair.

Object-Relational Database Structure Model and Structure Optimisation

“…New stereotypes are defined for UML class diagram, which would correspond more precisely to possible structures of object-relational database. It is frequently noted in publications that object-relational database is suitable for the creation of spatial data, scientific research data and technical equipment databases [12], [13]. Due to this reason, two approaches for the construction of object-relational databases have been proposed: 1) General approach.…”

“…Due to this reason, two approaches for the construction of object-relational databases have been proposed: 1) General approach. In this case, the transformation of conceptual model is discussed: a) SQL:1999 or SQL:2003 standard data storage in structures [12], [13]; b) specific object-relational database systems in data structures (in most cases, in the structures of company Oracle database systems) have been selected. The second option is better because each object-relational database system has its own specific structure and their implementation.…”