A formal mapping of an object-oriented conceptual model to a relational implementation model
This research explores an approach of integrating the strengths of two known technologies in the database design process: the relational and object-oriented technologies.In this approach, an object-oriented data model is used in the design of the conceptual schema, while a relational model is adopte...
Saved in:
Main Author: | |
---|---|
Format: | text |
Language: | English |
Published: |
Animo Repository
1999
|
Subjects: | |
Online Access: | https://animorepository.dlsu.edu.ph/etd_masteral/2037 |
Tags: |
Add Tag
No Tags, Be the first to tag this record!
|
Institution: | De La Salle University |
Language: | English |
Summary: | This research explores an approach of integrating the strengths of two known technologies in the database design process: the relational and object-oriented technologies.In this approach, an object-oriented data model is used in the design of the conceptual schema, while a relational model is adopted for the implementation schema. A mapping scheme to transform the object-oriented database model to its relational model is defined. This mapping scheme is based on set theory definitions of the constructs of the two data models.
The object-oriented and relational technologies are based on different paradigms. Object-orientation is based on the concept that systems should be built from interacting components called objects, while relational technology is based on the concept that data for an application can be stored in one or more rows within tables. Because of this difference, difficulties arise when one tries to use them together. One cannot truly store an object in a relational database for objects have both data and functionality, while relational databases store only data.
This research shows that it is possible to map objects to relations and still retain their structure. However, it also shows that in the process of conversion, certain drawbacks are encountered. To achieve success in combining the object-oriented and relational technologies, we must understand both paradigms and their differences, as well as make intelligent tradeoffs based on that knowledge. |
---|