Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!utgpu!water!watmath!clyde!burl!codas!killer!pollux!ti-csl!!peterson From: peterson@.UUCP Newsgroups: comp.ai,comp.databases Subject: Re: object oriented database query Message-ID: <36479@ti-csl.CSNET> Date: Fri, 13-Nov-87 17:11:40 EST Article-I.D.: ti-csl.36479 Posted: Fri Nov 13 17:11:40 1987 Date-Received: Sun, 15-Nov-87 15:02:00 EST References: <4528@cc5.bbn.COM> Sender: news@ti-csl.CSNET Reply-To: peterson@csc.ti.com (Bob Peterson) Organization: TI Computer Science Center, Dallas Lines: 135 Keywords: object oriented, database Xref: utgpu comp.ai:1050 comp.databases:514 In article <4528@cc5.bbn.COM> mfidelma@bbn.COM (Miles Fidelman) writes: >Can anyone point me to work in the area of applying database technology >to supporting object oriented environments? Sure. See the short bibliography attached to the end of this message. It is about two pages in length. Several publications are of special interest: Proceedings of OOPSLA '86 and '87, and the Proceedings of the OODB Workshop held in '86 in Pacific Grove, CA. In each of these you'll find interesting articles addressing OODB issues, as well as many additional references following each article. >It strikes me that database technology tends to focus on supporting large >production databases, with attention to fast processing speeds, maintaining >database integrity, journalizing/checkpointing, etc.; while object oriented >environments are basically prototyping environments. I don't believe OODB's are, as you put it, "...basically prototyping environments." Indeed, there are applications, such as VLSI CAD and hypertext, that are not well-supported by conventional databases. When implemented using an object-oriented style, these applications use many objects with rather complex and dynamic interconnections. Conventional data models, i.e., hierarchical, network, and relational, don't handle the complex, dynamic interconnected objects very well. At least that's my opinion. >Has anyone been working on making a production object oriented environment? Yes, we at Texas Instruments are working on just such an effort. In addition there are at least three companies now offering for sale object-oriented database systems. Hardcopy and Electronic Addresses: Bob Peterson Compuserve: 76703,532 P.O. Box 1686 Usenet: peterson@csc.ti.com Plano, Tx USA 75074 (214) 995-6080 (Skip the rest of this message if you aren't interested in two pages of bibliographic references.) OBJECT-ORIENTED DATABASE SYSTEMS BIBLIOGRAPHY [BCG*87]J. Bannerjee, H.T. Chou, J.F. Garza, W. Kim, D. Woelk, N. Ballou, and H.J. Kim. Data Model Issues For Object-Oriented Applications. ACM Transactions on Office Information Systems, January 1987. [BD81] A. J. Baroody and D. J. DeWitt. An Object- Oriented Approach to Database System Implementation. ACM Transactions on Database Systems, 6(4):576-601, December 1981. [bFL85] Edited by F. Lochovsky. IEEE Database Engineering. December 1985. A quarterly bulletin of the IEEE Computer Society Technical Committee on Database Engineering, Special Issue on Object-Oriented Systems. [But86] M. H. Butler. An Approach to Persistent LISP Objects. In Proc. COMPCON, pages 324-329, IEEE, San Fransisco, CA, March 1986. [CAC*84]W. Cockshott, M. Atkinson, K. Chisholm, P. Bailey, and R. Morrison. Persistent Object Management System. Software Practice and Experience, 14:49-71, 1984. [Mis84] N. Mishkin. Managing Permanent Objects. Technical Report YALEU/DCS/RR-338, Department of Computer Science, Yale University, New Haven, CT, November 1984. [ML87] T. Merrow and J. Laursen. A Pragmatic System for Shared Persistent Objects. In N. Meyrowitz, editor, OOPSLA '87 Conference Proceedings, pages 103-110, ACM, ACM, New York, NY, Oct 4-8 1987. [Nie85] O. M. Nierstrasz. Hybrid: A Unified Object-Oriented System. IEEE Database Engineering, 8(4):49-57, December 1985. [OBS86] P. O'Brien, B. Bullis, and C. Schaffert. Persistent and Shared Objects in Trellis/Owl. In Proceedings of the 1986 International Workshop on Object-Oriented Database Systems, pages 113-123, ACM, Pacific Grove, CA, September 1986. [OOD86] Proceedings of the International Workshop on Object Oriented Database Systems, Pacific Grove, CA, September 1986. ACM. [OOP86] ACM. Conference Proceedings for the Object-Oriented Programming Systems, Languages and Applications '86 Conference (OOPSLA '86), Portland, OR, Sept 29-Oct 2 1986 Panel Discussion. [Pet87] R. W. Peterson. Object-Oriented Database Design. AI Expert, 2(3):27-31, March 1987. [SR86] M. Stonebraker and L. Rowe. The Design of POSTGRES. In Proceedings of SIGMOD, pages 340-355, Washington D.C., December 1986. [SZ86] A. Skarra and S. Zdonik. The Management of Changing Types in an Object-Oriented Database. In Norman Meyrowitz, editor, OOPSLA '86 Conference Proceedings, pages 483-495, ACM, ACM, Portland, OR, September 1986. [SZ87] K. Smith and S.B. Zdonik. Intermedia: A Case Study of the Differences Between Relational and Object-Oriented Database Systems. In N. Meyrowitz, editor, OOPSLA '87 Conference Proceedings, pages 452-465, ACM, ACM, New York, NY, Oct 4-8 1987. [SZR86] A. S. Skarra, S. Zdonik, and S. Reiss. An Object Server for an Object Oriented Database System. In International Workshop on Object Oriented Database Systems, pages 196-205, Pacific Grove, CA, September 1986. [Tho86] C. Thompson. Object-oriented databases. Texas In- struments Engineering Journal, 3(1):169-175, Jan. 1986. [TMT86] C.W. Thompson, S. Martin, and S. Thatte. Real-Time Object-Oriented Manufacturing Databases. In AAAI 1986 Workshop on AI in Manufacturing, Aug 1986. [Wie86] G. Wiederhold. Views, Objects, and Databases. IEEE Computer, ():37-44, December 1986. Hardcopy and Electronic Addresses: Office: Bob Peterson Compuserve: 76703,532 NB 2nd Floor CSC Aisle C3 P.O. Box 1686 Usenet: peterson@csc.ti.com Plano, Tx USA 75074 (214) 995-6080 (work) or (214) 596-3720 (ans. machine)