What is the difference between oodbms and ordbms

If we sum up the merit, it is the its robustness that has stood the test of time. However, down the years its upkeep has significantly increased both its size and complexity.

The addition and modification of feature as well as the tools built to support changing needs, often had the challenge to coerce different technologies.

This is a clear call for unavoidable complexity. Even having to deal with many of its pros and cons, relational database management systems RDBMS are here to stay. This is true even in the day and age of big data, No SQL and what not. Professionals have devoted a lot of their expertise to improving and assimilating it with many of new technological system. When the wave of object-oriented technology became the forefront of the application development, RDBMS seemed too incompatible.

But miscible components were conjugated with techniques like Hibernate, JTA and the like. These techniques became so popular and effective that RDBMS may not seem like a system of yore and can be quite a reliable backend companion in many projects. The fact is, there are many old systems still available today and many new systems thriving on the relational model. The object-relational database systems are an attempt to merge the two different kind of system. It is an object database enhancement of a relational model, a hybrid in design.

Perhaps, the most visible aspect that we might observe is in the addition of object database features in the SQL revision for this hybrid model. One of the pitfalls of relation model was in describing complex objects. The vibe of object-oriented mechanisms was brought into the play with the introduction of type constructors to describe row type that corresponds to the tuple constructor, array type for specifying collections, sets, list, mechanism for specifying object identity, encapsulation, inheritance, and more.

The commercial implementations simply added a layer of some of the object-oriented principle on top of the relational database management system. Since this system is based on relational model, there is one more problem added to it: translating object-oriented concept to relational mechanism.

However, this problem is extenuated by an object-oriented application that helps in the communication between the object-oriented application with the underlying relational databases.

Understand that relational and object-oriented principle do not go well together, because they work on different principle. Therefore, it may seem that this model somehow tries to coerce them into a truce for the sake of developer's convenience. The real reason is to permit storage and retrieval of objects in an RDBMS way by providing extension to the query language to work on the object-oriented principle. The object-oriented database systems are of different genre.

OODBMSes attempt to imbibe the object-oriented principle to database functionality right from its core implementation. RDBMS support a small, fixed collection of data types eg. Integers, dates, strings which has proven adequate for traditional application domains such as administrative data processing. Supports Structured Query Language. RDBMS products :. Object-oriented model products:. Supports Standard data types and additional data types. Supports standard data types and new richer data types.

As we all know a relational database is made up of relations, who are sets of tuples, while an object-oriented database is made up of classes, which are sets of classes.

Thus, a relational database will contain a re-lation called STUDENT, with tuples contain-ing information about each student, while a relational database will contain a class called. It is to be noted that there is the possibility of converting the object model into a relational mode.

In such a situation each class corresponds to a relation, the attributes of a particular class will become attributes corresponding to a re-lation and the same time, each object in-stance in a class will have a corresponding tuple in a relation.

While in a relational database the compo-nents of a tuple must be primitive types strings, integer, real, etc. Table 1 presents a comparison of the main concepts used in object and rela-tional modeling of data. Table 1. Object oriented model Relational. Object identifier OID Primary key In the relational model if the primary key is not identified the system gener-ates an identifier automatically Inheritance There is none.

Certain opera-tions, which are limited, can be automatically brought into use when the data are used. The Join Operator refers data from separate tables. Inheritance helps to reduce the re-dundancy of methods.

It is used in the stage of designing the database and not in the stage of developing the applications. Some ORDBMSs are beginning to support addi-tional index types, such as generic B-trees, R-trees region trees for fast access to two — and three dimensional data, and the ability to index on the output of a function.

Nor-malized data are separated from processing and the processing corresponding to satisfy-ing informational requirements need not be totally pdefined, thus accepting ad-hoc re-quirements too. They are inseparable.

It is said that we have to do with an independence of classes and not with an independence of data. Atkinson M. In Proc.