lotus

previous page: 9.3) ConceptBase - A Deductive Object Manager for Meta Data Bases (Research Systems - OO Data Model - Object-oriented Databases And Vendors)
  
page up: Object-Oriented Technology FAQ
  
next page: 9.3) Encore (Brown University) (Research Systems - OO Data Model - Object-oriented Databases And Vendors)

9.3) COOL/COCOON (Ulm Universitaet) (Research Systems - OO Data Model - Object-oriented Databases And Vendors)




Description

This article is from the Object-Oriented Technology FAQ, by Bob Hathaway rjh@geodesic.com with numerous contributions by others.

9.3) COOL/COCOON (Ulm Universitaet) (Research Systems - OO Data Model - Object-oriented Databases And Vendors)

The COCOON project was intended to extend the concepts and the
architecture of relational database management systems (DBMSs) beyond
nested relational to object-oriented ones. Based upon the nested
relational DBMS kernel DASDBS, we have built a prototype implementation
of the COCOON model. Key characteristics of COCOON are: generic,
set-oriented query and update operators similar to relational algebra
and SQL updates, respectively; object-preserving semantics of query
operators, which allows for the definition of updatable views; a
separation of the two aspects of programming language "classes": type
vs. collection; predicative description of collections, similar to
"defined concepts" in KL-One--like knowledge representation
languages; automatic classification of objects and views (positioning
in the class hierarchy); physical clustering of subobjects via the use
of nested relations as the internal storage structures; support for the
optimization of both, the physical DB design and query transformation,
by corresponding optimizers.

Project goals are:

- to develop a general formal framework for investigations of all
kinds of schema changes in object-oriented database systems
(including schema design, schema modification, schema tailoring, and
schema integration);
- to find implementation techniques for evolving database schemas,
such that changes on the logical level propagate automatically to
adaptations of the physical level (without the need to modify all
instances, if possible).

In their current paper [see below], schema evolution is used as
example of a general framework for change in OODBs, supporting change
on three levels of database objects: data objects, schema objects, and
meta-schema objects.

Contact: Markus Tresch <tresch@informatik.uni-ulm.de>

REFERENCES:
M. Tresch and M.H. Scholl. "Meta Object Management
and its Application to Database Evolution." In
_Proceedings of the Eleventh International
Conference on the Entity-Relationship Approach",
Karlsruhe, Germany, Oct 1992. Springer Verlag (to
appear).

 

Continue to:













TOP
previous page: 9.3) ConceptBase - A Deductive Object Manager for Meta Data Bases (Research Systems - OO Data Model - Object-oriented Databases And Vendors)
  
page up: Object-Oriented Technology FAQ
  
next page: 9.3) Encore (Brown University) (Research Systems - OO Data Model - Object-oriented Databases And Vendors)