Newsgroups: comp.object
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!ira.uka.de!fauern!forwiss.uni-passau.de!jeusfeld
From: jeusfeld@forwiss.uni-passau.de (Manfred Jeusfeld)
Subject: Re: Looking for explanation of OODB problem
Message-ID: <1991Jun8.082807.26343@forwiss.uni-passau.de>
Sender: usenet@forwiss.uni-passau.de (USENET News System)
Nntp-Posting-Host: forwiss.uni-passau.de
Organization: University of Passau, Germany
References: <1991Jun6.194440.2879@apd.mentorg.com>
Date: Sat, 8 Jun 91 08:28:07 GMT
Lines: 23

In article <1991Jun6.194440.2879@apd.mentorg.com> plogan@apd.mentorg.com (Patrick Logan) writes:
>    are not very well developed," he [Gerson] says.
>
>    "The basic problem in an OODBMS is in the user I/O inside of a
>    transaction," Gerson adds. "Programs in an RDBMS have a looser
>    connection to the data. Users issue an SQL query, the data base
>    gets a table, makes a copy of it, and the user looks at it on his
>    screen."
>    Gerson syas he believes few people are aware of this fundamental
>    flaw in OODBMS technology because so few systems are out there.

Alright. I think the problem is that some implementations of
OODBMSs have occupied the label "object-oriented database" by
"object-oriented programming language with some kind of
persistency".

There is no doubt that oo abstraction principles can be incorporated
into a DBMS that does follow oldfashioned traditions like
declarative query language, view abstractions (aka deduction rules),
and global integrity constraints.

.-- Manfred Jeusfeld, Universitaet Passau