[comp.databases] object-oriented DBMS's

werner@tnoibbc.UUCP (Werner de Bruijn) (05/09/89)

We at IBBC-TNO are investigating what benefits/penalties might be expected from
the use of object-oriented DBMS's. I know of the existance of several products
in the US (Vbase, Ontos, GemStone, Gbase, IRIS, Postgres, ...).
I studied some material of Vbase and Postgres and they look very promising.
Does anyone have any pointers-to/comments-on/experience-with (these)
object-oriented DBMS products?

Currently, to get some experience, we are building a very simple system
in 'C'. In order to gather some momentum in this project any comments
or suggestions are welcome.
-- 
Werner de Bruijn                              TEL    : (31) 15-606448
IBBC-TNO                                      FAX    : (31) 15-620304
P.O. Box 49                                   UUCP   : ..!hp4nl!tnoibbc!werner
2600 AA  Delft, the Netherlands               USENET : werner@tnoibbc

DMasterson@cup.portal.com (David Scott Masterson) (05/16/89)

I'm looking for some basic information on object-oriented databases and how
they can be of benefit OVER relational databases.  It seems to me that an
object-oriented interface to a database is just another layer on top of a
database system (say, relational).  Also, it would seem that access of data
from the database would be at a very fundamental level (the object) and
thus would not be able to take advantage of the set processing capabilities
of the database system.  Can OODBMSs really implement methods against
objects at all levels or are objects that are stored in an OODBMS kept at a
general level with general methods?  I think I'm opening up a can of worms,
but what the h***.  I have a few ideas on this, but I'm interested getting
a better handle on the state of the art first.

What do you think?   ;-)

David Masterson
DMasterson@cup.portal.com