ABSTRACT
Schema evolution poses serious challenges in historical data management. Traditionally, historical data have been archived either by (i) migrating them into the current schema version that is well-understood by users but compromising archival quality, or (ii) by maintaining them under the original schema version in which the data was originally created, leading to perfect archival quality, but forcing users to formulate queries against complex histories of evolving schemas. In the PRIMA system, we achieve the best of both approaches, by (i) archiving historical data under the schema version under which they were originally created, and (ii) letting users express temporal queries using the current schema version. Thus, in PRIMA, the system rewrites the queries to the (potentially many) pertinent versions of the evolving schema. Moreover, the system o ers automatic documentation of the schema history, and allows the users to pose temporal queries over the metadata history itself. The proposed demonstration highlights the system features exploiting both a synthetic-educational running example and the real-life evolution histories (schemas and data), which include hundreds of schema versions from Wikipedia and Ensembl. The demonstration off ers a thorough walk-through of the system features and a hands-on system testing phase, where the audiences are invited to directly interact with the advanced query interface of PRIMA.
- Schema evolution benchmark {on-line}: http://yellowstone.cs.ucla.edu/schema--evolution/index.php/Benchmark_ExtensionGoogle Scholar
- J. Clifford, A. Croker, F. Grandi, and A. Tuzhilin. On Temporal Grouping. In Recent Advances in Temporal Databases, pages 194--213. Springer Verlag, 1995. Google ScholarDigital Library
- C. A. Curino, H. J. Moon, L. Tanca, and C. Zaniolo. Schema evolution in wikipedia: toward a web information system benchmark. International Conference on Enterprise Information Systems (ICEIS), 2008.Google Scholar
- C. A. Curino, H. J. Moon, and C. Zaniolo. Graceful database schema evolution: the prism workbench. Proc. of VLDB, 1(1), 2008. Google ScholarDigital Library
- C. A. Curino, H. J. Moon, and C. Zaniolo. Managing the history of metadata in support for db archiving and schema evolution. ECDM 2008. Google ScholarDigital Library
- A. Deutsch and V. Tannen. Mars: A system for publishing XML from mixed and redundant storage. VLDB 2003. Google ScholarDigital Library
- S. Marche. Measuring the stability of data models. European Journal of Information Systems, 2(1):37--47, 1993.Google ScholarCross Ref
- H. J. Moon, C. A. Curino, A. Deutsch, C.-Y. Hou, and C. Zaniolo. Managing and querying transaction-time databases under schema evolution. Proc. of VLDB, 1(1), 2008. Google ScholarDigital Library
- G. Ozsoyoglu and R. Snodgrass. Temporal and Real-Time Databases: A Survey. IEEE Transactions on Knowledge and Data Engineering, 7(4):513--532, 1995. Google ScholarDigital Library
- D. I. Sjoberg. Quantifying schema evolution. Information and Software Technology, 35(1):35--44, 1993.Google ScholarCross Ref
- F. Wang, C. Zaniolo, and X. Zhou. Archis: An xml-based approach to transaction-time temporal database systems. The International Journal of Very Large Databases, 17(6):1445--1463, 2008. Google ScholarDigital Library
Index Terms
- PRIMA: archiving and querying historical data with evolving schemas
Recommendations
Study and Comparison of Schema Versioning and Database Conversion Techniques for Bi-Temporal Databases
TIME '99: Proceedings of the Sixth International Workshop on Temporal Representation and ReasoningSchema evolution and schema versioning are two techniques used for managing database evolution. Schema evolution keeps only the current version of a schema and database after applying schema changes. Schema versioning creates new schema versions and ...
Schema Versioning: Queries to the Generalized Temporal Database System
DEXA '99: Proceedings of the 10th International Workshop on Database & Expert Systems ApplicationsRaw data and database structures are evolving entities that require adequate support for past, present and even future versions. Temporal databases supporting schema versioning were developed with the aim of satisfying this requirement. This poster ...
Schema Versioning in Multi-temporal XML Databases
ICIS '08: Proceedings of the Seventh IEEE/ACIS International Conference on Computer and Information Science (icis 2008)Schema evolution keeps only the current data and the schema version after applying schema changes. On the contrary, schema versioning creates new schema versions and preserves old schema versions and their corresponding data. Much research work has ...
Comments