Schema Updates and Database Restructuring
Identifieur interne : 001F66 ( Crin/Curation ); précédent : 001F65; suivant : 001F67Schema Updates and Database Restructuring
Auteurs : Nacer Boudjlida ; Olivier PerrinSource :
English descriptors
- KwdEn :
Abstract
Changing a database schema may affect existing data instances and programs. To deal with the side effects of schema changes on both data and programs, data must migrate to the modified schema and programs must be adapted to the modified data structures. Indeed, due to the long duration of some activities using databases, like software engineering, it is a critical need to manage several versions of a database schema. So, a piece of data must be viewed as an instance of more than one data schema. Most of the current approaches related to this research area only deal with atomic changes and do not provide a real help to achieve program adaptation follow up complex changes.
Links toward previous steps (curation, corpus...)
- to stream Crin, to step Corpus: Pour aller vers cette notice dans l'étape Curation :001F66
Links to Exploration step
CRIN:boudjlida97aLe document en format XML
<record><TEI><teiHeader><fileDesc><titleStmt><title xml:lang="fr" wicri:score="-52">Schema Updates and Database Restructuring</title></titleStmt><publicationStmt><idno type="RBID">CRIN:boudjlida97a</idno><date when="1997" year="1997">1997</date><idno type="wicri:Area/Crin/Corpus">001F66</idno><idno type="wicri:Area/Crin/Curation">001F66</idno><idno type="wicri:explorRef" wicri:stream="Crin" wicri:step="Curation">001F66</idno></publicationStmt><sourceDesc><biblStruct><analytic><title xml:lang="fr">Schema Updates and Database Restructuring</title><author><name sortKey="Boudjlida, Nacer" sort="Boudjlida, Nacer" uniqKey="Boudjlida N" first="Nacer" last="Boudjlida">Nacer Boudjlida</name></author><author><name sortKey="Perrin, Olivier" sort="Perrin, Olivier" uniqKey="Perrin O" first="Olivier" last="Perrin">Olivier Perrin</name></author></analytic></biblStruct></sourceDesc></fileDesc><profileDesc><textClass><keywords scheme="KwdEn" xml:lang="en"><term>Data migration</term><term>Mapping functions</term><term>Object-Relationship Data Model</term><term>Programs adaptation</term><term>Schema evolution</term><term>Schema homomorphisms</term></keywords></textClass></profileDesc></teiHeader><front><div type="abstract" xml:lang="en" wicri:score="1701">Changing a database schema may affect existing data instances and programs. To deal with the side effects of schema changes on both data and programs, data must migrate to the modified schema and programs must be adapted to the modified data structures. Indeed, due to the long duration of some activities using databases, like software engineering, it is a critical need to manage several versions of a database schema. So, a piece of data must be viewed as an instance of more than one data schema. Most of the current approaches related to this research area only deal with atomic changes and do not provide a real help to achieve program adaptation follow up complex changes.</div></front></TEI><BibTex type="inproceedings"><ref>boudjlida97a</ref><crinnumber>97-R-267</crinnumber><category>3</category><equipe>OCEAN</equipe><author><e>Boudjlida, Nacer</e><e>Perrin, Olivier</e></author><title>Schema Updates and Database Restructuring</title><booktitle>{XII Brazilian Symposium on Database Systems, SBBD'97, Fortaleza, CE, Brazil}</booktitle><year>1997</year><keywords><e>Schema evolution</e><e>Data migration</e><e>Programs adaptation</e><e>Mapping functions</e><e>Object-Relationship Data Model</e><e>Schema homomorphisms</e></keywords><abstract>Changing a database schema may affect existing data instances and programs. To deal with the side effects of schema changes on both data and programs, data must migrate to the modified schema and programs must be adapted to the modified data structures. Indeed, due to the long duration of some activities using databases, like software engineering, it is a critical need to manage several versions of a database schema. So, a piece of data must be viewed as an instance of more than one data schema. Most of the current approaches related to this research area only deal with atomic changes and do not provide a real help to achieve program adaptation follow up complex changes.</abstract></BibTex></record>Pour manipuler ce document sous Unix (Dilib)
EXPLOR_STEP=$WICRI_ROOT/Wicri/Lorraine/explor/InforLorV4/Data/Crin/Curation
HfdSelect -h $EXPLOR_STEP/biblio.hfd -nk 001F66 | SxmlIndent | more
Ou
HfdSelect -h $EXPLOR_AREA/Data/Crin/Curation/biblio.hfd -nk 001F66 | SxmlIndent | more
Pour mettre un lien sur cette page dans le réseau Wicri
{{Explor lien
|wiki= Wicri/Lorraine
|area= InforLorV4
|flux= Crin
|étape= Curation
|type= RBID
|clé= CRIN:boudjlida97a
|texte= Schema Updates and Database Restructuring
}}
| This area was generated with Dilib version V0.6.33. |  |