We argue for avoiding database reorganizations due to schema modification in object-oriented systems, since these are expensive operations and they conflict with reusing existing software components. We show that data independence, which is a neglected concept in object databases, helps to avoid reorganizations in case of capacity preserving and reducing schema transformations. We informally present a couple of examples to illustrate the idea of a schema transformation methodology that avoids database reorganization
This paper describes a novel mechanism for upgrading objects in an object-oriented database. Unlike ...
Changes in the real world may require both the database population and the database schema to evolve...
A traditional database management system generally supports applications that consist of a large num...
We argue for avoiding database reorganizations due to schema modification in object-oriented systems...
Changing a database schema may affect the preexistent data instances and programs. Two major strateg...
While the c.ontents of databases can be easily changed, their organization is typically extremely ri...
It is a well-known fact that a significant share of the cost of information systems is spent on mai...
Reorganization of objects in an object databases is an important component of several operations lik...
A seamless approach to the incremental design and reuse of object-oriented methods and query specifi...
In this paper, we have benefited from having an object algebra maintaining closure that makes it pos...
Powerful solutions enabling interoperability must allow applications to evolve and requirements of s...
Abstract. Providing support for schema evolution allows existing databases to be adjusted for varyin...
AbstractCoupled transformation occurs when multiple software artifacts must be transformed in such a...
AbstractData schema transformations occur in the context of software evolution, refactoring, and cro...
To safely update industrially critical software interoperating on a shared Object-Oriented Database ...
This paper describes a novel mechanism for upgrading objects in an object-oriented database. Unlike ...
Changes in the real world may require both the database population and the database schema to evolve...
A traditional database management system generally supports applications that consist of a large num...
We argue for avoiding database reorganizations due to schema modification in object-oriented systems...
Changing a database schema may affect the preexistent data instances and programs. Two major strateg...
While the c.ontents of databases can be easily changed, their organization is typically extremely ri...
It is a well-known fact that a significant share of the cost of information systems is spent on mai...
Reorganization of objects in an object databases is an important component of several operations lik...
A seamless approach to the incremental design and reuse of object-oriented methods and query specifi...
In this paper, we have benefited from having an object algebra maintaining closure that makes it pos...
Powerful solutions enabling interoperability must allow applications to evolve and requirements of s...
Abstract. Providing support for schema evolution allows existing databases to be adjusted for varyin...
AbstractCoupled transformation occurs when multiple software artifacts must be transformed in such a...
AbstractData schema transformations occur in the context of software evolution, refactoring, and cro...
To safely update industrially critical software interoperating on a shared Object-Oriented Database ...
This paper describes a novel mechanism for upgrading objects in an object-oriented database. Unlike ...
Changes in the real world may require both the database population and the database schema to evolve...
A traditional database management system generally supports applications that consist of a large num...