Path: utzoo!utgpu!watserv1!watmath!att!rutgers!cs.utexas.edu!uunet!sps!wwb
From: wwb@sps.com (Bud Bach)
Newsgroups: comp.object
Subject: Re: the need for classes as objects
Message-ID: <268@sps.com>
Date: 31 Aug 90 13:27:27 GMT
References: <2259@esquire.UUCP> <55679@iuvax.cs.indiana.edu>
Organization: SPS - Indialantic, FL
Lines: 20

In article <55679@iuvax.cs.indiana.edu>, kitchel@iuvax.cs.indiana.edu (Sid Kitchel) writes:

> 	I'd say that runtime creation of classes is absolutely
> imperative for database applications. By definition the OODBS will be
> running when the end user invents new classes.
 
This depends on your DBMS Model.  We have developed an extensible DBMS
for an information processing system using Classic-Ada, an OOPL with
static classes.  Our approach was to have user definable class
descriptions represented as objects and then construct the instances
of user data from the class description object.  Both the class description 
and the instances are implemented using persistent objects making the
implementation rather straight forward.  Of course the disadvantage is
that there is an extra layer in the system.  The point is that database 
applications may be developed with statically classed languages.
-- 
Bud Bach   					Voice:  407 984-3370
Software Productivity Solutions, Inc.		FAX:    407 728-3957
122 4th Avenue					email:  wwb@sps.com
Indialantic, FL  32903				or:     ...!uunet!sps!wwb