Get 20M+ Full-Text Papers For Less Than $1.50/day. Subscribe now for You or Your Team.

Learn More →

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

Comparison of Post-Relational and Object-Relational modelling for real-world database applications 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. http://www.deepdyve.com/assets/images/DeepDyve-Logo-lg.png Journal of Systems and Information Technology Emerald Publishing

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

Loading next page...
 
/lp/emerald-publishing/comparison-of-post-relational-and-object-relational-modelling-for-real-vnmlyr0RPg

References (30)

Publisher
Emerald Publishing
Copyright
Copyright © Emerald Group Publishing Limited
ISSN
1328-7265
DOI
10.1108/JSIT-05-2014-0034
Publisher site
See Article on Publisher Site

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.

Journal

Journal of Systems and Information TechnologyEmerald Publishing

Published: Nov 4, 2014

There are no references for this article.