An object-relational database, in simple terms, is it?

Question

Database

In simple terms, we talk about a relational database, then this is data that is interconnected by sets of tables. Tables consist of cells where keys (links), values ​​(strings, numbers, booleans, etc.) are stored. (If I understand correctly)
But the object-relational database is all the same, just the data here is connected by objects?

Answer 1

so the net is full of descriptions
for you, no offense, you shouldn’t bother with it at all - it’s enough to take into work what your older brother or experience advises and not bother with the exact classification: there are many types of bases, some bases are at the junction: on Wiki , for example, ORDBMS is called Postgre - just remember that in such databases there are much more internal procedures, while in classic it is enough to write a structure

Answer 2

There is a lot of speculation around this term. For a database, in general, objectivity is not needed. basic SQL Ansi-92 does not support objectivity and therefore there is no sense from objectivity at the query level. In general, objectivity is a metaphor. It is very often tied to a language and a framework and a development environment (for example, Java-Spring). By itself, inheritance of tables or types, for example, in Oracle is supported (CREATE TYPE .. UNDER), but the percentage of using this option in production is numerically equal to zero. And generally speaking. For inheritance to be complete, RTTI and reflection are needed, and for relational databases this means that each data-row must carry information about the type. It is too expensive in general. And for the classic line of RDBMS, no one did it.