New SQL Standard in Database Modeling

Author(s):  
Eric Pardede ◽  
J. Wenny Rahayu ◽  
David Taniar

Relational Database (RDB) is arguably the most widely used repository for database applications. Since the 1970s, we have witnessed the relational data model, from which the RDB is originated, evolving. The progress aims to answer the increasing requirement in database applications. One of them is the requirement to deal with complex structure of real world problems. Unlike its Object-Oriented Database (OODB) counterpart, the RDB, for example, does not have facilities to store large structured objects, semi-structured data, and so forth.

2009 ◽  
Vol 160 (15) ◽  
pp. 2253-2274 ◽  
Author(s):  
Nezihe Burcu Ozgur ◽  
Murat Koyuncu ◽  
Adnan Yazici

Author(s):  
JOSEPH FONG ◽  
SAN KUEN CHEUNG

A methodology is introduced for translating from methods in an object-oriented database to routines in a relational database. The approach consists of three steps. The first step is to translate method signature to Persistent Stored Modules signature. The second step is to translate method source language to (function/procedure) routine. The process includes Host Language, OSQL's Qualification, Query Translation, Update Transaction Translation, and Objects inside Object. The third step is to translate method invocation to routine invocation. According to this approach, object-oriented database methods can be translated to relational database routines that can be executed in the relational database environment assisted by a frame model and case statements listing all possible cases of binding conditions and actions. The significance of the finding is adding an open object-oriented interface on top of relational database system for database interoperability and in the development of an object-relational database management system.


Author(s):  
Z. M. Ma

Computer applications in non-traditional areas have put requirements on conceptual data modeling. Some conceptual data models, being the tool of design databases, have been proposed. However, information in real-world applications is often vague or ambiguous. Currently, less research has been done in modeling imprecision and uncertainty in conceptual data models and the design of databases with imprecision and uncertainty. In this chapter, a different level of fuzziness based on fuzzy set and possibility distribution theory will be introduced into the IFO data model and the corresponding graphical representations will be given. The IFO data model is then extended to a fuzzy IFO data model, denoted IF2O. In particular, we provide the approach to mapping an IF2O model to a fuzzy relational database schema.


Author(s):  
Marek Krótkiewicz

This paper provides a comparison between methods used to represent unary, binary and n-ary relations in the relational database (RDB) and object-oriented database (OODB) models and the association-oriented database (AODB) model proposed in terms of their unambiguity. We have elaborated upon the RDB, OODB and AODB models perceived from the perspective of the categories applied to define them. What has been discussed is a number of solutions assuming the form of schemes for the AODB model. We substantiate that those solutions have unequivocally met the conditions of relations of any chosen arity and multiplicity, at the same time keeping the notation concise, unambiguous and considerably expressive.


Author(s):  
Reda Alhajj ◽  
Faruk Polat

We present an approach to transfer content of an existing conventional relational database to a corresponding existing object-oriented database. The major motivation is having organizations with two generations of information systems; the first is based on the relational model, and the second is based on the object-oriented model. This has several drawbacks. First, it is impossible to get unified global reports that involve information from the two databases without providing a wrapper that facilitates accessing one of the databases within the realm of the other. Second, organizations should keep professional staff familiar with the system. Finally, most of the people familiar with the conventional relational technology are willing to learn and move to the emerging object-oriented technology. Therefore, one appropriate solution is to transfer content of conventional relational databases into object-oriented databases; the latter are extensible by nature, hence, are more flexible to maintain. However, it is very difficult to extend and maintain a conventional relational database.


Sign in / Sign up

Export Citation Format

Share Document