Incomplete information in object-oriented databases
- 1 September 1990
- journal article
- Published by Association for Computing Machinery (ACM) in ACM SIGMOD Record
- Vol. 19 (3) , 5-16
- https://doi.org/10.1145/101077.101079
Abstract
We present a way to handle incomplete information both at schema and object instance level in an object-oriented database. Incremental schema design becomes possible with the introduction of generic classes. Incomplete data in an object instance is handled with the introduction of explicit null values in a similar way as in the relational and nested relations data models.Keywords
This publication has 14 references indexed in Scilit:
- Algres: an advanced database system for complex applicationsIEEE Software, 1990
- An algebra for structured office documentsACM Transactions on Information Systems, 1989
- Object identity as a query language primitivePublished by Association for Computing Machinery (ACM) ,1989
- Type theories and object-oriented programmimgACM Computing Surveys, 1988
- A semantics of multiple inheritanceInformation and Computation, 1988
- Class modification in the GemStone object-oriented DBMSPublished by Association for Computing Machinery (ACM) ,1987
- Types and persistence in database programming languagesACM Computing Surveys, 1987
- Data model issues for object-oriented applicationsACM Transactions on Information Systems, 1987
- Semantics and implementation of schema evolution in object-oriented databasesPublished by Association for Computing Machinery (ACM) ,1987
- Missing information (applicable and inapplicable) in relational databasesACM SIGMOD Record, 1986