Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!odi!jack
From: jack@odi.com (Jack Orenstein)
Newsgroups: comp.databases
Subject: Re: Extended RDB vs OODB
Message-ID: <1989Aug11.181138.14565@odi.com>
Date: 11 Aug 89 18:11:38 GMT
References: <3560052@wdl1.UUCP> <411@odi.ODI.COM> <458@cimshop.UUCP>
Reply-To: jack@odi.com (Jack Orenstein)
Organization: Object Design Inc., Burlington, MA
Lines: 22

In article <458@cimshop.UUCP> davidm@cimshop.UUCP (David Masterson)
writes (quoting a posting of mine):

>>On the other hand, many CAD/CAM and CASE developers have bypassed
>>relational DBMSs due to performance problems.
>>
>Could you elaborate on the performance problems in this case?  I mean is it
>inherit in what the CAD/CAM or CASE developers are doing that leads to
>performance problems with relational databases or is it just they chose the
>wrong (aka. slow) relational database system?  Perhaps there are things that
>OODBMSs can be optimized to do better than a relational database system, but I
>still think that a relational database can provide a strong foundation for an
>object-oriented database.  I'd like to hear why that can't be true.
>
>David Masterson
>uunet!cimshop!davidm

Dan Weinreb, a co-worker of mine, has just posted a very thorough
discussion of this point, so I'll refer you to his article.

Jack Orenstein
Object Design, Inc.