CUDL language semantics: Updating FDB data

Karanikolas, Nikitas N.; Nitsiou, Maria; Yannakoudakis, E. J.; Skourlas, Christos

doi:10.1016/j.jss.2008.12.031

Cited by 5 publications

(20 citation statements)

References 13 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…We preferred the FDB model [10], since it is more compact and well defined than the other models and also supports schema evolution. Karanikolas et al [9,11], introduced the syntax and semantics of the CUDL, a database language (both DDL and DML for the FDB model) that supports composite data types, i.e. attributes (tags in CUDL terminology) that combine more than one other sub-attributes (subfields in CUDL terminology).…”

Section: The Conceptual Universal Database Languagementioning

confidence: 99%

“…That means that the users can express retrieval restrictions over a specific subfield or can express the modification of a specific subfield in a specific repetition of some tag, etc. In [9], the authors focused mainly in presenting and analyzing the statement of value retrieval (in the schema and the data). More recently [11], they focused mainly in presenting and analyzing the CUDL statement of value modifications in the schema (schema changes) and the data.…”

Section: The Conceptual Universal Database Languagementioning

confidence: 99%

“…In [9], the authors focused mainly in presenting and analyzing the statement of value retrieval (in the schema and the data). More recently [11], they focused mainly in presenting and analyzing the CUDL statement of value modifications in the schema (schema changes) and the data. They also have undertaken the need for relationship declarations [10].…”

Section: The Conceptual Universal Database Languagementioning

confidence: 99%

“…However, having more powerful database models, but still using data manipulation languages designed only for fundamental data attributes, is a waste of time and resources. Therefore, in Section 3, we present the basic ideas related to CUDL and its abstraction level, CAL [9,10,11,22]. The transformation from CAL to FDB (meta-model, [21,23]) has been studied in [9,11].…”

Section: Introductionmentioning

confidence: 99%

“…Therefore, in Section 3, we present the basic ideas related to CUDL and its abstraction level, CAL [9,10,11,22]. The transformation from CAL to FDB (meta-model, [21,23]) has been studied in [9,11]. In Section 4, we present the 5 Rule Set for Transformation from ER to CAL [12] (dealing with the most common cases that appear in real life applications, for the transformation from ER diagrams to CAL), while in Section 5, we present the addition of an extra rule that is needed for the transformation of a relation between a weak and a strong (not identifying) entity that also has attributes.…”

Section: Introductionmentioning

confidence: 99%

See 4 more Smart Citations

Database Design Revisited

Karanikolas,

Vassilakopoulos

2114

IJIIM

View full text Add to dashboard Cite

Information Systems design is affected by the simplicity of the relational model types, though these types do not correspond directly to entities of real applications. In this paper, we present another approach, where the Information System designers would be able to directly represent the real world in a database model, very close to the Entity-Relationship (ER) model. A query and manipulation language that can handle composite data types, close to ER diagrams, is the Conceptual Universal Database Language (CUDL). We demonstrate that a database modelled by ER diagrams can be directly expressed to the CUDL Abstraction Level (CAL), the data model corresponding to CUDL, by a set of rules for direct transformation of ER diagrams to CAL. This set consists of a basic set of five rules, which is extended with an extra rule that deals with specific situations appearing in practical applications. Consequently, the resulting more powerful and composite data can be directly maintained with the CUDL. In this way, the development process consisting in conceptual design (ER), transformation to Logical Relational Schema, usage of SQL for data manipulation/retrieval and the reverse steps to present the results in the conceptual level is simplified by conceptual design (ER), transformation to CAL and the usage of CUDL for direct manipulation/retrieval of real world (conceptual) structures.

show abstract

Section: The Conceptual Universal Database Languagementioning

confidence: 99%

Section: The Conceptual Universal Database Languagementioning

confidence: 99%

Section: The Conceptual Universal Database Languagementioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

Database Design Revisited

Karanikolas,

Vassilakopoulos

2114

IJIIM

View full text Add to dashboard Cite

show abstract

Conceptual Universal Database Language: Moving Up the Database Design Levels

Karanikolas

Vassilakopoulos

2009

Advances in Databases and Information Systems

View full text Add to dashboard Cite

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

Karanikolas

Vassilakopoulos

2014

Journal of Systems and Information Technology

View full text Add to dashboard Cite

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.

show abstract

CUDL language semantics: Updating FDB data

Cited by 5 publications

References 13 publications

Database Design Revisited

Database Design Revisited

Conceptual Universal Database Language: Moving Up the Database Design Levels

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

Contact Info

Product

Resources

About