[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

OODBMS status...

I've had a few requests to relay whatever information I found about persistent
object OO databases.  I have had only a limited response so far, which I
extracted below.  The one reply referencing the ROSE database bears looking
into, if I can find a way to establish communication with that group.
Meanwhile, I may just do a little research into the subject.  The company that
pays for my time (Rational - an Ada environment vendor) already uses a
commercial 3rd party OODBMS in house.  If I can get good quality information
about current OODBMS technology, I may just write my own.
For my current application, I just create persistent objects by writing and
reading text files.  CAR/CDR links are handled by creating global persistent
unique ids (also derived from a network wide text file service).  So, unique
ids are assigned for every object; when the object is read from the text file,
I enter it's unique id in a table and fix up all its extra-object references
via this same table.
My database needs are probably a lot smaller than most, and given my prolific
output I can probably craft all the code I need in a small number of days.  My
problem is just finding that small number of days and deciding what to craft.
If, however, something results, I'll post it here.  Comments and suggestions
are welcome so that what I post ends up being useful to others.
Exerpts of replies received follow:
Since my off-handed comment, "There are a number of object-oriented
databases implemented in CLOS." generated a fair amount of interest,
I'll be more specific.  A number of people in image understanding,
including myself, have developed rather narrow home grown CLOS
databases (with facilities for writing data to files and retrieving
it).  These are probably marginal interesting to people with other
However, a group at RPI has developed a reasonably sophisticated CLOS
based database called ROSE. There are 2 problems with it for the MCL
community. The native language for ROSE is C++.  As a result, the CLOS
version carries extra baggage from the translation and is missing
useful features that could easily be included in LISP.  The other
problem is that it is designed for Unix workstations. I got it to run
under MCL1.3.2, after fairly extensive modifications to the interface
file. I still haven't gotten it to work under MCL2.0b1.(Some
tricks required get around the included CLOS.)  If there are still
interested parties, the person to contact is harrisr@cs.rpi.edu
                                Jim Eilbert
I looked for OODBs accessible from MCL about 1/2 a year ago and I
failed to find anything. If you discover something would you please
tell me? This is an area that is ripe for products but there are few
I've seen... Thank you.
I too am looking for persistent OO databases that can be accessed from
  Please (!) send me any information you might have on such beasts.
  -- Luke
I won't repeat the message from 76326.1723@COMPUSERVE.COM@INTERNET# regarding
Statice under MacIvory as I believe everyone got to read it.
I also got two or three other replies which I don't have handy, but the were
mostly requests for whatever information I find.
Michael Wimble