Difference between RDBMS and ORDBMS

entity-framework ordbms postgresql rdbms sql-server


When I was reading about PostgreSQL on its wiki page, where it describes itself as an ORDBMS, it occurred to me. I've always been aware of the RDBM system Microsoft SQL Server. Could someone please explain to me the fundamental distinctions between the Relational Database Management System (RDBMS) and the Object Relational Database Management System (ORDBMS) and when I should use either of them?

My main concern also relates to the fact that Entity Framework (EF) is often used in the Microsoft SQL Server environment to do object relational mapping on the application side. So, in the realm of ORDBMS, do all the functions of an ORM already fall within the purview of the database itself, or might there be use cases or situations where I would also wind up utilising an ORM like Entity Framework on top of ORDBMS? Do individuals really use ORMs on top of ORDBMS platforms?

1/11/2019 11:57:18 AM

Accepted Answer

The majority of database players either don't support it or just partially support it. It is intricate and seldom used. Although "data" is OO by nature, databases that date back decades do not support ORDBMS (or OODBMS). The learning curve offers additional issues.

The virtual registry view you see in Registry Editor is similar to an ORDBMS/OODBMS. Zzz-9-Zzz in a tree-style format. However, they could be kept internally in a relational, flat, or hierarchical form. You actually don't care since the APIs provide you the registry information you need.

Similar to this, large players could provide certain extensions even if they don't support (and won't support) the OO nature of databases. Or you may need to create your own OO data framework from scratch. Use relations to represent actors and directors in a movie database (tables). Tables and the referential integrity requirements enforced by database/DB designer may easily represent actors, directors, and shooting locations as classes or objects.

As a developer, you would convert this relational data structure into an object-oriented form usingMovie referencing actors/directors as a group (1:1 or 1:N). I have no idea how or whatEE supports this, but only in this method would mapping be performed.

Databases that are Object-Relational

  • Object-oriented technology built on top of and inside a relational environment.
  • Rather than in tables of rows, items are kept in tables of objects.
  • Support of major object oriented features: complex types, inheritance, aggregation, methods
  • Advantage: Extension of a well-known technology
  • Drawbacks: Combining both technologies might lead to schemas that are difficult to grasp.
  • possesses performance issues
  • Complex object extensibility, encapsulation, inheritance, and improved interfaces to OO languages are aspects of object-relational systems.
  • Developers may include new types of data objects into the relational data model abstraction using ORDBMSs (and on top of SQL).

The graphic below demonstrates how data may be accessed.

enter image description here

8/23/2016 7:49:13 AM

Popular Answer

adapted from zzzz-5 zzzz:


The main elements of RDBMS are based on Ted Codd’s 13 rules for a relational system, the concept of relational integrity, and normalization. The three fundamentals of a relational database are that all information must be held in the form of a table, where all data are described using data values. The second fundamental is that each value found in the table columns does not repeat. The final fundamental is the use of Standard Query Language (SQL).

Benefits of RDBMS are that the system is simple, flexible, and productive. Because the tables are simple, data is easier to understand and communicate with others. RDBMS are flexible because users do not have to use predefined keys to input information. Also, RDBMS are more productive because SQL is easier to learn. This allows users to spend more time inputting instead of learning. More importantly, RDBMS’s biggest advantage is the ease with which users can create and access data and extend it if needed. After the original database is created, new data categories can be added without the existing application being changed.

There are limitations to the relational database management system. First, relational databases do not have enough storage area to handle data such as images, digital and audio/video. The system was originally created to handle the integration of media, traditional fielded data, and templates. Another limitation of the relational database is its inadequacy to operate with languages outside of SQL. After its original development, languages such as C++ and JavaScript were formed. However, relational databases do not work efficiently with these languages. A third limitation is the requirement that information must be in tables where relationships between entities are defined by values.


Object-Relational database (ORDBMS) is the third type of database common today. ORDBMS are systems that “attempt to extend relational database systems with the functionality necessary to support a broader class of applications and, in many ways, provide a bridge between the relational and object-oriented paradigms.”

ORDBMS was created to handle new types of data such as audio, video, and image files that relational databases were not equipped to handle. In addition, its development was the result of increased usage of object-oriented programming languages, and a large mismatch between these and the DBMS software.

One advantage of ORDBMS is that it allows organizations to continue using their existing systems, without having to make major changes. A second advantage is that it allows users and programmers to start using object-oriented systems in parallel.

There are challenges in implementing an ORDBMS. The first is storage and access methods. The second is query processing, and the third is query optimization.

Related Questions


Licensed under: CC-BY-SA with attribution
Not affiliated with Stack Overflow
Licensed under: CC-BY-SA with attribution
Not affiliated with Stack Overflow