Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!aplcen!aplcomm!uunet!dlogics!dsa
From: dsa@dlogics.COM (David Angulo)
Newsgroups: comp.object
Subject: Re: Object-Oriented COBOL?
Summary: Your accusation is too harsh
Keywords: object-oriented, business applications
Message-ID: <678@dlogics.COM>
Date: 8 Nov 90 00:24:42 GMT
References: <0B010001.xkabkz@bse.com> <13921@neptune.inf.ethz.ch>
Organization: Datalogics Inc., Chicago
Lines: 41

In article <13921@neptune.inf.ethz.ch>, marti@mint.inf.ethz.ch (Robert Marti) writes:
| In article <0B010001.xkabkz@bse.com> eberard@bse.com writes in response
| to article <694@ghp.UUCP> by Tom Huras:
| 
| [...]
| 
| >>  A relational database will be used.
| 
| >Good luck, and welcome to the object-oriented vs. relational DBMS wars.
| >While a relational DBMS can be used with an object-oriented software
| >development effort, you will have to:
| >	a. write some additional software to interface with the relational
| >	   DBMS,
| >	b. very likely corrupt your design to accommodate the
| >	   relational DBMS
| 
| This sounds like a shot from the hip.
| 
| Do you have any evidence to substantiate your second claim?
| 

  Well, I have been doing exactly this (using a relational DBMS with an OOPL -
viz. c++) for over a year and I happen to agree with Mr. Berard.  I am also not
going to give "evidence" but I will relate my experiences a little.
The problems mainly arise from the fact that relationships are developed
via SQL queries.  So, if Class1 has a collection of Class2, those
instances of Class2 must be obtained with a query like "find Class2 where
owner=Class1_key".  Everytime a new relationship is established or a
specific result set is needed, one must establish a new method to perform
that query.  This gets to be burdensome.  The way I understand what OODBMS's
are, these relationships are inherent to the storage and are automatically
restored when the object is retrieved (I forgot the buzz word - was it
activated?) and vice-versa.  Another problem is that SQL is available from
anywhere (this is a somewhat lesser problem if you have good conscientious
programmers) so access to the stored "objects" is not confined to your
class methods.
-- 
David S. Angulo                  (312) 266-3134
Datalogics                       Internet: dsa@dlogics.com
441 W. Huron                     UUCP: ..!uunet!dlogics!dsa
Chicago, Il. 60610               FAX: (312) 266-4473