Talk:Object–relational database
![]() | Computing Unassessed | |||||||||
|
ordbms is an object relatio
Small change
The object-relational model can offer another advantage in that the database can make use of the relationships between data to easily collect related records. In an address book application, an additional table would be added to the ones above to hold zero or more addresses for each user. Using a traditional RDBMS, collecting information for both the user and their address requires a "join": If I'm not mistaken, this paragraph means that one would need an additional table in a traditional RDBMS and only one table that also stores the adresses for the users in a ORDBMS. It should be made more clear if I am right or one would need two tables in an ORD, too. Subwy (talk) 21:51, 26 August 2008 (UTC)
Removed link still of value
The following external link was removed in an edit:
- RDBMS != Object Store — an explanation of differences between relational databases and object stores.
It still is of value, however, even if it was posted on a not-necessarily-reputable site (Slashdot) so I thought I would leave it here on the Talk page for the curious. -- 192.115.133.116 (talk) 20:40, 28 October 2008 (UTC)
Raise level of abstraction?
"Overview" para 3, sentence 2:
- ORDBMS technology aims to allow developers to raise the level of abstraction at which they view the problem domain.
Is too vague, unless ORDBMS is defined exactly this way. (It also sounds too much like advertizing). I would guess that the API call requires less conversions and setups, and the language and DBS interact more by objects that are mutually recognized as belonging to both "system" more naturally, but that is just my dream system. How? ... said: Rursus (bork²) 17:06, 15 February 2009 (UTC)