A survey of schema versioning issues for database systems
J. Roddick. Information and Software Technology, 37 (7):
383--393(1995)
Abstract
Schema versioning is one of a number of related areas dealing with the same general problem - that of using multiple heterogeneous schemata for various database related tasks. In particular, schema versioning, and its weaker companion, schema evolution, deal with the need to retain current data and software system functionality in the face of changing database structure. Schema versioning and schema evolution offer a solution to the problem by enabling intelligent handling of any temporal...
- GS:112 cites
- good overview
- the distinctions between syntax/business rules (e.g. only use 4 numbers to represent unique ID), data model (schema) (employees are related to address),
- hoch's idea on inconsistency might be of interest
- replace the notions of 'semantic heterogeneity' with 'syntactic heterogeneity' and use the semantics (what are we trying to store) to drive evolution
- Zaniolo's three-valued model for interpreting null-values e.g. never known, known once, now unknown, etc.
- key problems: relation of db evolution to software; how to query evolved schemas
%0 Journal Article
%1 roddick95
%A Roddick, John F.
%D 1995
%J Information and Software Technology
%K survey evolution database
%N 7
%P 383--393
%T A survey of schema versioning issues for database systems
%U http://citeseer.ist.psu.edu/roddick95survey.html
%V 37
%X Schema versioning is one of a number of related areas dealing with the same general problem - that of using multiple heterogeneous schemata for various database related tasks. In particular, schema versioning, and its weaker companion, schema evolution, deal with the need to retain current data and software system functionality in the face of changing database structure. Schema versioning and schema evolution offer a solution to the problem by enabling intelligent handling of any temporal...
@article{roddick95,
abstract = {Schema versioning is one of a number of related areas dealing with the same general problem - that of using multiple heterogeneous schemata for various database related tasks. In particular, schema versioning, and its weaker companion, schema evolution, deal with the need to retain current data and software system functionality in the face of changing database structure. Schema versioning and schema evolution offer a solution to the problem by enabling intelligent handling of any temporal...},
added-at = {2006-03-24T16:34:33.000+0100},
author = {Roddick, John F.},
biburl = {https://www.bibsonomy.org/bibtex/275adc67acf66c67c305f59b9c31d5b05/neilernst},
citeulike-article-id = {559599},
comment = {- GS:112 cites
- good overview
- the distinctions between syntax/business rules (e.g. only use 4 numbers to represent unique ID), data model (schema) (employees are related to address),
- hoch's idea on inconsistency might be of interest
- replace the notions of 'semantic heterogeneity' with 'syntactic heterogeneity' and use the semantics (what are we trying to store) to drive evolution
- Zaniolo's three-valued model for interpreting null-values e.g. never known, known once, now unknown, etc.
- key problems: relation of db evolution to software; how to query evolved schemas},
description = {sdasda},
interhash = {33c6f9510ae649d09d29123b4111bcf6},
intrahash = {75adc67acf66c67c305f59b9c31d5b05},
journal = {Information and Software Technology},
keywords = {survey evolution database},
number = 7,
pages = {383--393},
priority = {0},
timestamp = {2006-03-24T16:34:33.000+0100},
title = {A survey of schema versioning issues for database systems},
url = {http://citeseer.ist.psu.edu/roddick95survey.html},
volume = 37,
year = 1995
}