Framework for a complete migration of relational databases to other types of databases(object oriented OO, object-relational OR, XML)

2016 ◽  
Author(s):  
Alae El Alami ◽  
Mohamed Bahaj
Keyword(s):  
Relational Databases ◽  
Object Oriented ◽  
Object Relational

Object-Relational Modeling

2009 ◽  
pp. 162-170
Author(s):  
Jaroslav Zendulka
Keyword(s):  
Relational Database ◽  
Relational Databases ◽  
Conceptual Modeling ◽  
Object Oriented ◽  
Database Systems ◽  
Object Relational ◽  
The Difference ◽  
Object Oriented Approach ◽  
Entity Relationship ◽  
Oriented Approach

Modeling techniques play an important role in the development of database applications. Well-known entity-relationship modeling and its extensions have become a widely-accepted approach for relational database conceptual design. An object-oriented approach has brought a new view of conceptual modeling. A class as a fundamental concept of the object-oriented approach encapsulates both data and behavior, whereas traditional relational databases are able to store only data. In the early 1990s, the difference between the relational and object-oriented (OO) technologies, which were, and are still used together to build complex software systems, was labeled the object-relational impedance mismatch (Ambler, 2003). The object-oriented approach and the need of new application areas to store complex data have greatly influenced database technology since that time. Besides appearance of object-oriented database systems, which fully implement objectoriented paradigm in a database environment (Catell et al., 2003), traditional relational database management systems become object-relational (Stonebraker & Brown, 1999). The most recent versions of the SQL standard, SQL: 1999 (Melton & Simon (2001) and SQL: 2003 (Eisenberg et al., 2004), introduced object-relational features to the standard and leading database producers have already released packages which incorporate them.

Using Object-Oriented Features

2011 ◽  
pp. 51-88
Author(s):  
Johanna Wenny Rahayu ◽  
David Tanier ◽  
Eric Pardede
Keyword(s):  
Relational Databases ◽  
Object Oriented ◽  
Relationship Types ◽  
Object Relational ◽  
The Relationship

In Chapter II, we discussed the different features available in Oracle™ that can be used to implement an object-oriented model. We will use those features in this chapter. The discussion in this chapter will be categorized based on the relationship types. There are three distinct relationship types that we have to consider in object-oriented modeling for implementation in object-relational databases: inheritance, association, and aggregation. Some manipulations will be needed in order to accommodate the features of these relationships.

A Literature Overview of Fuzzy Database Modeling

2008 ◽  
pp. 187-207 ◽  
Author(s):  
Z.. M. Ma
Keyword(s):  
Relational Databases ◽  
Object Oriented ◽  
Data Models ◽  
Relational Model ◽  
Complex Objects ◽  
Database Modeling ◽  
Database Models ◽  
Fuzzy Database ◽  
Conceptual Data ◽  
Object Oriented Databases

Fuzzy set theory has been extensively applied to extend various data models and resulted in numerous contributions, mainly with respect to the popular relational model or to some related form of it. To satisfy the need of modeling complex objects with imprecision and uncertainty, recently many researches have been concentrated on fuzzy semantic (conceptual) and object-oriented data models. This chapter reviews fuzzy database modeling technologies, including fuzzy conceptual data models and database models. Concerning fuzzy database models, fuzzy relational databases, fuzzy nested relational databases, and fuzzy object-oriented databases are discussed, respectively.

Enriched Conceptualization of Subtyping

2010 ◽  
pp. 1-16 ◽  
Author(s):  
Terry Halpin
Keyword(s):  
Information Systems ◽  
Open Source ◽  
Relational Databases ◽  
Second Generation ◽  
Object Oriented ◽  
Role Modeling ◽  
Graphic Notation ◽  
Open Source Tool ◽  
Main Ideas ◽  
Object Role Modeling

When modeling information systems, one often encounters subtyping aspects of the business domain that can prove challenging to implement in either relational databases or object-oriented code. In practice, some of these aspects are often handled incorrectly. This chapter examines a number of subtyping issues that require special attention (e.g. derivation options, subtype rigidity, subtype migration), and discusses how to model them conceptually. Because of its richer semantics, the main graphic notation used is that of second generation Object-Role Modeling (ORM 2). However, the main ideas could be adapted for UML and ER, so these are also included in the discussion. A basic implementation of the proposed approach has been prototyped in Neumont ORM Architect (NORMA), an open-source tool supporting ORM 2.

Rough Sets

2009 ◽  
pp. 1127-1150
Author(s):  
Theresa Beaubouef ◽  
Frederick E. Petry
Keyword(s):  
Set Theory ◽  
Rough Set ◽  
Rough Sets ◽  
Relational Databases ◽  
Rough Set Theory ◽  
Object Oriented ◽  
Uncertainty Management ◽  
Database Model ◽  
Management Of Uncertainty ◽  
Object Oriented Database

This chapter discusses ways in which rough-set theory can enhance databases by allowing for the management of uncertainty. Rough sets can be integrated into an underlying database model, relational or object oriented, and also used in the design and uerying of databases, because roughsets are a versatile theory, theories. The authors discuss the rough relational databases model, the rough object-oriented database model, and fuzzy set and intuitionistic set extensions to each of these models. Comparisons and benefits of the various approaches are discussed, illustrating the usefulness and versatility of rough sets for uncertainty management in databases.

Sign in / Sign up

Export Citation Format

Share Document