mfidelma@bbn.COM (Miles Fidelman) (11/09/87)
Can anyone point me to work in the area of applying database technology to supporting object oriented environments? 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. Has anyone been working on making a production object oriented environment? Thanks much, Miles Fidelman email to: mfidelman@bbn.com
UH2@PSUVM.BITNET (Lee Sailer) (11/10/87)
The ACM journals and SIG newsletters on Data Base and Office Info Systems
often have stuff about Object Oriented Database management.
Typically, the O approach is most useful when the world be
modeled is object like. For example, consider building a database to
manage geographic info for a city the size of New York. Support
queries like "What offices are within 15 minutes of the UN building?"
or "Whose view will be blocked by a 200 stofry building at 5th and
Broadway?"
Likewise, systems for managing blueprints, specifications, and
change requests in a manufacturing environment profit immensly
from Object orientations.
lee
merlin@hqda-ai.UUCP (David S. Hayes) (11/10/87)
A very nice object-oriented database is produced by Graphael
(a French company). This system supports text, and numbers, and
mouse-sensitive graphics, and sound, and digitized pictures as
part of the database. IE, your entry for Company X can include a
streetmap of their area. Alternatively, a floorplan of your
building can be mouse-sensitive. Mouse on some office, and the DB
can tell you who works there.
This software runs on Symbolics Lisp Machines, and some
others I can't recall right now. Their US contact is:
Eric Sansonetti, National Sales Manager
Graphael, Inc.
255 Bear Hill Road
Waltham, MA 02154
Phone: 617-890-7055
--
David S. Hayes, The Merlin of Avalon PhoneNet: (202) 694-6900
UUCP: *!uunet!cos!hqda-ai!merlin ARPA: ai01@hios-pent.arpashapiro@wdl1.UUCP (David Shapiro) (11/11/87)
>Can anyone point me to work in the area of applying database technology >to supporting object oriented environments? ---------- For those in the bay area, I recieved an anouncement of a seminar on object orented databases, offered through Santa Clara University. It will be 4 days long and costs $525/person. It appears to address several issues of applications in computer aided engineering and knowledge based systems. Also offers a day and a half of hands on using some object-oriented database management systems (OODBMS?) Call (408) 554-4929. Dave Shapiro Ford Aerospace & Communications Corp.
peterson@.UUCP (11/14/87)
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)