Advances in Object-Oriented Database Systems
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).
1008084740
Advances in Object-Oriented Database Systems
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).
54.99 In Stock
Advances in Object-Oriented Database Systems

Advances in Object-Oriented Database Systems

Advances in Object-Oriented Database Systems

Advances in Object-Oriented Database Systems

Overview

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).

Product Details

ISBN-13: 9783642634109
Publisher: Springer Berlin Heidelberg
Publication date: 10/29/2012
Series: NATO ASI Subseries F: , #130
Edition description: Softcover reprint of the original 1st ed. 1994
Pages: 515
Product dimensions: 6.10(w) x 9.25(h) x 0.04(d)

Table of Contents

Section 1: Introduction.- What Makes Object-Oriented Database Management Systems Different.- Section 2: Models and Formal Languages.- Object-Oriented Data Model Concepts.- Query Languages for Models with Object-Oriented Features.- Functional Programming Formalisms for OODBMS Methods.- A Formal Object-Oriented Query Model and an Algebra.- Section 3: System Implementation Issues.- Optimization of Object-Oriented Query Languages: Problems and Approaches.- Transaction Models and Transaction Management in Object-Oriented Database Management Systems.- Object Storage Management Architectures.- Active Object Systems.- Object-Oriented Rule Languages and Optimization Techniques.- The Promise of Distributed Computing and the Challenges of Legacy Information Systems.- Object-Orientation and Interoperability.- Section 4: Systems and Prototypes.- Open OODB: Architecture and Query Processing Overview.- METU Object-Oriented DBMS.- The Ode Object-Oriented Database Management System: An Overview.- Object-Oriented Modeling for Hypermedia Systems Using the VODAK Model Language.- Object Modeling Using Classification in CANDIDE and its Applications.- References.
From the B&N Reads Blog
Page 1 of

Customer Reviews