Among other issues, database evolution includes the necessity of propagating the changes inside and between abstraction levels.There exist several mechanisms in order to carry out propagations from one level to another, that are distinguished on thebasis of when and how the changes are performed. The strict mechanism, which implies the immediate realization of modifications,is a time–consuming process. In this paper we propose a solution that is closer to the lazy and logical mechanisms, in whichchanges are delayed or not finally realized, respectively. This solution makes use of the notion of view. The use of viewsallows the data not to be changed if it is not necessary and facilitates carrying out changes when required.
%0 Journal Article
%1 dominiguez08evolution
%A Domínguez, Eladio
%A Lloret, Jorge
%A �?ngel Rubio,
%A Zapata, María
%D 2008
%J Database and Expert Systems Applications
%K tech.versioning research.db
%P 822--836
%T Model–Driven, View–Based Evolution of Relational Databases
%U http://dx.doi.org/10.1007/978-3-540-85654-2_74
%X Among other issues, database evolution includes the necessity of propagating the changes inside and between abstraction levels.There exist several mechanisms in order to carry out propagations from one level to another, that are distinguished on thebasis of when and how the changes are performed. The strict mechanism, which implies the immediate realization of modifications,is a time–consuming process. In this paper we propose a solution that is closer to the lazy and logical mechanisms, in whichchanges are delayed or not finally realized, respectively. This solution makes use of the notion of view. The use of viewsallows the data not to be changed if it is not necessary and facilitates carrying out changes when required.
@article{dominiguez08evolution,
abstract = {Among other issues, database evolution includes the necessity of propagating the changes inside and between abstraction levels.There exist several mechanisms in order to carry out propagations from one level to another, that are distinguished on thebasis of when and how the changes are performed. The strict mechanism, which implies the immediate realization of modifications,is a time–consuming process. In this paper we propose a solution that is closer to the lazy and logical mechanisms, in whichchanges are delayed or not finally realized, respectively. This solution makes use of the notion of view. The use of viewsallows the data not to be changed if it is not necessary and facilitates carrying out changes when required.},
added-at = {2010-10-07T11:05:54.000+0200},
author = {Domínguez, Eladio and Lloret, Jorge and �?ngel Rubio and Zapata, María},
biburl = {https://www.bibsonomy.org/bibtex/2f9bdb21f8113ee78a686d3342c90fc23/msn},
description = {SpringerLink - Book Chapter},
interhash = {31c012aff63b59e117ecdf1b1c54de7c},
intrahash = {f9bdb21f8113ee78a686d3342c90fc23},
journal = {Database and Expert Systems Applications},
keywords = {tech.versioning research.db},
pages = {822--836},
timestamp = {2010-10-07T11:05:54.000+0200},
title = {Model–Driven, View–Based Evolution of Relational Databases},
url = {http://dx.doi.org/10.1007/978-3-540-85654-2_74},
year = 2008
}