Encyclopedia of Database Systems

2018 Edition
| Editors: Ling Liu, M. Tamer Özsu

Schema Versioning

  • John F. RoddickEmail author
Reference work entry
DOI: https://doi.org/10.1007/978-1-4614-8265-9_323


Schema versioning deals with the need to retain current data, and the ability to query and update it, through alternate database structures. (The structure of a database is held in a schema (pl. schemata or schemas). Commonly, particularly in temporal databases, these schemata represent the historical structure of a database but this may not always be the case.) Schema Versioning requires not only that data are not lost in schema transformation but also requires that all data are able to be queried, both retrospectively and prospectively, through user-definable version interfaces. Partial schema versioning is supported when data stored under any historical schema may be viewed through any other schema but may only be updated through one specified schema version – normally the current or active schema. (Schema evolution and schema versioning has been conflated in the literature with the two terms occasionally being used interchangeably.)

Historical Background


This is a preview of subscription content, log in to check access.

Recommended Reading

  1. 1.
    Kim W, Ballou N, Chou HT, Garza JF, Woelk D. Features of the orion object-oriented database system. In: Kim W, Lochovsky F, editors. Object-oriented concepts, databases and applications. New York: ACM Press; 1989. p. 251–82.Google Scholar
  2. 2.
    Madhavan J, Halevy AY. Composing mappings among data sources. In: Proceedings of the 29th International Conference on Very Large Data Bases; 2003; p. 572–83.CrossRefGoogle Scholar
  3. 3.
    McKenzie L, Snodgrass R. Schema evolution and the relational algebra. Inf Syst. 1990;15(2):207–32.CrossRefGoogle Scholar
  4. 4.
    Melnik S, Rahm E, Bernstein PA. Rondo: a programming platform for generic model management. In: Proceedings of the ACM SIGMOD International Conference on Management of Data; 2003. p. 193–204.Google Scholar
  5. 5.
    Miller R, Ioannidis Y, Ramakrishnan R. The use of information capacity in schema integration and translation. In: Proceedings of the 29th International Conference on Very Large Data Bases; 1993. p. 120–33.Google Scholar
  6. 6.
    Osborn S. The role of polymorphism in schema evolution in an object-oriented database. IEEE Trans Knowl Data Eng. 1989;1(3):310–7.CrossRefGoogle Scholar
  7. 7.
    Penney D, Stein J. Class modification in the gemstone object-oriented DBMS. In: Proceedings of the 1987 Conference on Object-Oriented Programming Systems, Languages, and Applications; 1987. p. 111–17.Google Scholar
  8. 8.
    Roddick JF. SQL/SE – a query language extension for databases supporting schema evolution. ACM SIGMOD Rec. 1992;21(3):10–6.CrossRefGoogle Scholar
  9. 9.
    Roddick JF, Snodgrass R. Schema versioning support, chapter 22. In: Snodgrass R, editor. The TSQL2 temporal query language. Boston: Kluwer; 1995. p. 427–49.zbMATHCrossRefGoogle Scholar
  10. 10.
    Roddick JF, Grandi F, Mandreoli F, Scalas MR. Beyond schema versioning: a flexible model for spatio-temporal schema selection. Geoinformatica. 2001;5(1):33–50.zbMATHCrossRefGoogle Scholar
  11. 11.
    Skyt J, Jensen CS, Mark L. A foundation for vacuuming temporal databases. Data Knowl Eng. 2003;44(1):1–29.zbMATHCrossRefGoogle Scholar
  12. 12.
    Zdonik S. Version management in an object-oriented database. In: Proceedings of the International Workshop on Advanced Programming Environments; 1986. p. 405–22.CrossRefGoogle Scholar

Copyright information

© Springer Science+Business Media, LLC, part of Springer Nature 2018

Authors and Affiliations

  1. 1.Flinders UniversityAdelaideAustralia

Section editors and affiliations

  • Richard T. Snodgrass
    • 1
  • Christian S. Jensen
    • 2
  1. 1.University of ArizonaTucsonUSA
  2. 2.Aalborg UniversityAalborg ØstDenmark