CLASSIC: a structural data model for objects
SIGMOD '89 Proceedings of the 1989 ACM SIGMOD international conference on Management of data
A classification algorithm for supporting object-oriented views
CIKM '94 Proceedings of the third international conference on Information and knowledge management
A formal model of views for object-oriented database systems
Theory and Practice of Object Systems
The Unified Modeling Language user guide
The Unified Modeling Language user guide
A Transparent Object-Oriented Schema Change Approach Using View Evolution
ICDE '95 Proceedings of the Eleventh International Conference on Data Engineering
Multiview: A Methodology for Supporting Multiple Views in Object-Oriented Databases
VLDB '92 Proceedings of the 18th International Conference on Very Large Data Bases
Contribution to the evolution of information systems
Proceedings of the IFIP WG8.1 Working Conference on Methods and Associated Tools for the Information Systems Life Cycle
Context Versions in an Object-Oriented Model
DDEXA '93 Proceedings of the 4th International Conference on Database and Expert Systems Applications
Derived Types and Subschemas: Towards Better Support for Logical DataIndependence in Object-Oriented Data Models
| Hi-index | 0.00 |
View Mechanisms, widely used in the relational databases, pose new questions in the object model which captures much more semantics. In this paper, we will focus on inheritance and inter-objects relationships. two main semantic aspects of the object model. Like in the relational model, most of the current works about object-oriented views assume a fine granularity of the views. View classes are defined by the application of a query operator to one or two classes of the base schema. View schemas are defined as sets of view classes. These sets are explicitly chosen by the database administrator. We present the solutions produced by the application of our CROME model. In CROME, view classes extend the descriptions of the domain objects supplied by the base schema. The relationships introduced in the base schema are shared and preserved in view schemas. By adapting them locally, each view schema contextualize these relationships. We will show that this contextualization of the base schema gives it generic properties which enforce a stronger coherence of the view schemas.