Advances in Object-Oriented Database Systems

  • Asuman Dogac
  • M. Tamer Özsu
  • Alexandros Biliris
  • Timos Sellis
Conference proceedings

Part of the NATO ASI Series book series (volume 130)

Table of contents

  1. Front Matter
    Pages i-xi
  2. Introduction

    1. Front Matter
      Pages 1-1
  3. Models and Formal Languages

    1. Front Matter
      Pages 27-27
    2. Klaus R. Dittrich
      Pages 29-45
    3. Gerd Hillebrand, Paris Kanellakis, Sridhar Ramaswamy
      Pages 73-99
    4. Reda Alhajj, M. Erol Arkun
      Pages 101-116
  4. System Implementation Issues

    1. Front Matter
      Pages 117-117
    2. Gail Mitchell, Stanley B. Zdonik, Umeshwar Dayal
      Pages 119-146
    3. Alexandros Biliris, Jack Orenstein
      Pages 185-200
    4. Alejandro P. Buchmann
      Pages 201-224
    5. William Kent
      Pages 287-305
  5. Systems and Prototypes

    1. Front Matter
      Pages 307-307
    2. Asuman Dogac, Cetin Ozkan, Budak Arpinar, Tansel Okay, Cem Evrendilek
      Pages 327-354
    3. Wolfgang Klas, Karl Aberer, Erich Neuhold
      Pages 389-433
    4. Shamkant Navathe, Ashoka Savasere, Tarek Anwar, Howard Beck, Sunit Gala
      Pages 435-476
  6. Back Matter
    Pages 477-523

About these proceedings


Object-oriented database management systems (OODBMSs) have generated significant excitement in the database community in the last decade. This interest stems from a real need for data management support for what are called "advanced application areas" that are not well-served by relational technology. The case for object-oriented technology has been made on three fronts. First is the data modeling requirements of the new applications. Some of the more important shortcomings of the relational systems in meeting the requirements of these applications include: 1. Relational systems deal with a single object type: a relation. A relation is used to model different real-world objects, but the semantics of this association is not part of the database. Furthermore, the attributes of a relation may come only from simple and fixed data type domains (numeric, character, and, sometimes, date types). Advanced applications require explicit storage and manipulation of more abstract types (e.g., images, design documents) and the ability for the users to define their own application-specific types. Therefore, a rich type system supporting user­ defined abstract types is required. 2. The relational model structures data in a relatively simple and flat manner. Non­ traditional applications require more complex object structures with nested objects (e.g., a vehicle object containing an engine object).


Anfrageoptimierung CAD/CAM Database systems Datenbanksysteme Engineering databases Object orientation Object-Oriented Database System Objektorientierung Query optimization Storage systems Technische Datenbanken data model database database management database system DBMS distributed computing formal language functional programming modeling object-oriented database optimization programming language semantics SQL

Editors and affiliations

  • Asuman Dogac
    • 1
  • M. Tamer Özsu
    • 2
  • Alexandros Biliris
    • 3
  • Timos Sellis
    • 4
  1. 1.Software Research and Development CenterMiddle East Technical UniversityAnkaraTurkey
  2. 2.Department of Computing ScienceUniversity of AlbertaEdmontonCanada
  3. 3.AT&T Bell LaboratoriesMurray HillUSA
  4. 4.Department of Electrical and Computer EngineeringNational Technical University of Athens, ZographouAthensGreece

Bibliographic information

  • DOI
  • Copyright Information Springer-Verlag Berlin Heidelberg 1994
  • Publisher Name Springer, Berlin, Heidelberg
  • eBook Packages Springer Book Archive
  • Print ISBN 978-3-642-63410-9
  • Online ISBN 978-3-642-57939-4
  • Buy this book on publisher's site