John F. Roddick
Lina Al-Jadir
Marlon Dumas
Abstract
One of the fundamental aspects of information and database systems is that they change. Moreover, in so doing they evolve, although the manner and quality of this evolution is highly dependent on the mechanisms in place to handle it. While changes in data are handled well, changes in other aspects, such as structure, rules, constraints, the model, etc., are handled to varying levels of sophistication and completeness.
In order to study this in more detail a workshop on Evolution and Change in Data Management was held in Paris in November 1999. It brought together researchers from a wide range of disciplines with a common interest in handling the fundamental characteristics and the conceptual modelling of change in information and database systems. This short report of the workshop concentrates on some of the general lessons that emerged during the four days.
Index Terms
- Evolution and change in data management — issues and directions
Recommendations
Optimising schema evolution operation sequences in object databases for data evolution
ER'12: Proceedings of the 31st international conference on Conceptual ModelingWe propose an approach to optimising schema evolution operation sequences in object databases. The approach separates operations that add structures from those that remove structures so that all additions are performed before any removals. This ...
Efficient and scalable data evolution with column oriented databases
EDBT/ICDT '11: Proceedings of the 14th International Conference on Extending Database TechnologyDatabase evolution is the process of updating the schema of a database or data warehouse (schema evolution) and evolving the data to the updated schema (data evolution). It is often desired or necessitated when changes occur to the data or the query ...
Collateral evolution of applications and databases
IWPSE-Evol '09: Proceedings of the joint international and annual ERCIM workshops on Principles of software evolution (IWPSE) and software evolution (Evol) workshopsSeparating the evolution of an application from the evolution of its persistent data, or from the evolution of the database system used to store the data can have collateral effects, such as data loss, program failure, or decreased performance. In this ...
Comments