Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!ucbvax!agate!eos!shelby!polya!quass From: quass@polya.Stanford.EDU (Dallan W. Quass) Newsgroups: comp.databases Subject: Re: Seamless integration with an OODB Message-ID: <11436@polya.Stanford.EDU> Date: 21 Aug 89 17:31:58 GMT Sender: Dallan W. Quass Reply-To: quass@Polya.Stanford.EDU (Dallan W. Quass) Organization: Stanford University Lines: 29 David C. Martin writes >One language >I have not seen discussed here is Common LISP and CLOS. With the introduction >of the meta-object protocol appendix, it seems that this language environment >would be most suitable for an OODBMS front-end to a robust storage manager. Check out PCLOS, by Andreas Paepcke. It makes use of the meta-object protocol to provide persistent storage for CLOS objects. One of the goals is to interface to a variety of storage managers, so that you can choose based upon functionality vs. performance. (Currently a main-memory database and IRIS are used as storage managers.) References: PCLOS: A Flexible Implementation of CLOS Persistence 1988 ECOOP PCLOS: A Critical Review 1989 OOPSLA (to appear) Also, someone mentioned how widely differing DBMS's were are being called 'OODBMS's. I agree. However, there is work in progress to try to work out a standard. See "Why Isn't There an Object-Oriented Data Model" by David Maier, to appear in the IFIP 11'th World Computer Congress. In it he summarizes a working paper by Malcolm Atkinson, Francois Bancilhon, David DeWitt, Klaus Dittrich, David Maier, and Stanley Zdonik, called "The Object-Oriented Database System Manifesto," which represents a step in the standardization direction. Dallan Quass quass@eclipse.stanford.edu