Smalltalk-80: the language and its implementation
Smalltalk-80: the language and its implementation
Distrbution and Abstract Types in Emerald
IEEE Transactions on Software Engineering - Special issue on distributed systems
Query processing in a multimedia document system
ACM Transactions on Information Systems (TOIS)
Features of the ORION object-oriented database system
Object-oriented concepts, databases, and applications
Persistent and shared objects in Trellis/Owl
OODS '86 Proceedings on the 1986 international workshop on Object-oriented database systems
Modeling concepts for VLSI CAD objects (abstract only)
SIGMOD '85 Proceedings of the 1985 ACM SIGMOD international conference on Management of data
COL: A Logic-Based Language for Complex Objects
EDBT '88 Proceedings of the International Conference on Extending Database Technology: Advances in Database Technology
Toward a General Spatial Data Model for an Object-Oriented DBMS
VLDB '86 Proceedings of the 12th International Conference on Very Large Data Bases
Method precomputation in object-oriented databases
COCS '91 Proceedings of the conference on Organizational computing systems
On formal models for object-oriented databases
ACM SIGPLAN OOPS Messenger
Distributed multimedia applications: A review
Computer Communications
Hi-index | 0.00 |
The object-oriented paradigm is becoming very popular for database applications and several object-oriented DBMSs have been developed. A basic notion in this paradigm is the inheritance hierarchy that allows the users to define objects and the associated operations starting from already defined objects. However, in database applications the inheritance hierarchy must provide a conceptual modeling function, in addition to the re-usability function. Another important requirement is to provide support for data distribution in (possibly) heterogeneous environments. This means that object implementation may differ depending on the object location. This paper presents a model that decouples these two aspects, modeling vs implementation, by using the concept of abstract and implementation classes. An abstract class specifies properties and methods for a set of similar objects, like in other object-oriented data models. An abstract class is however independent of the object implementation and location. An implementation class defines the implementation of an abstract class. In our model an abstract class may have several implementations. This allows the user to provide different implementations for the same set of objects, without requiring the objects to change class.