Semantics and implementation of schema evolution in object-oriented databases

Banerjee, Jayanta; Kim, Won; Kim, Hyoung-Joo; Korth, Henry F.

doi:10.1145/38713.38748

Cited by 424 publications

(243 citation statements)

References 6 publications

Supporting

Mentioning

236

Contrasting

Unclassified

Order By: Relevance

“…ORION [15,4] is an object-oriented database. It provides a solution to data migration based on dynamic schema evolution that targets the physical level.…”

Section: Related Workmentioning

confidence: 99%

Integrated Model-Based Software Development, Data Access, and Data Migration

Bordbar

Draheim

Horn³

et al. 2005

Model Driven Engineering Languages and Systems

View full text Add to dashboard Cite

Abstract. In this paper we describe a framework for robust system maintenance that addresses specific challenges of data-centric applications. We show that for data-centric applications, classical simultaneous roundtrip engineering approaches are not sufficient. Instead we propose an architecture that is an integrated model-based approach for software development, database access and data migration. We explain the canonical development process to exploit its features. We explain how the approach fits into the model-driven architecture vision. We report on experiences with the approach in the IMIS environmental mass database project.

show abstract

“…ORION [15,4] is an object-oriented database. It provides a solution to data migration based on dynamic schema evolution that targets the physical level.…”

Section: Related Workmentioning

confidence: 99%

Integrated Model-Based Software Development, Data Access, and Data Migration

Bordbar

Draheim

Horn³

et al. 2005

Model Driven Engineering Languages and Systems

View full text Add to dashboard Cite

show abstract

“…provides a complete collection of primitive changes [2] applicable to a schema. They are listed in Tab.…”

Section: Definition 4 (Legalmentioning

confidence: 99%

“…However careful and accurate the initial design may have been, a database schema is likely to undergo changes and revisions after implementation. In order to avoid the loss of data after schema changes, many object-oriented systems like O [ 1], ORION (ITASCA) [2], and GemStone [3] support schema evolution, which provides (partial) automatic recovery of the extant data by adapting them to the new schema. However, if only the updated schema is retained, all the applications compiled with the past schema may cease to work.…”

Section: Introductionmentioning

confidence: 99%

“…To this purpose, we will define focuses on the operational aspects of schema versioning in order to provide users with a provably correct evolving schema whose data can then be manipulated through different schema versions. In general, the schema change support implies the adoption of statements for schema modification defined by means of primitives (LLPs -Low Level Primitives) acting on "atomic" elements of the underlying data model [2]. Starting from a general object-oriented model, we will first formally define the semantics at schema and data level of a well-understood taxonomy of schema changes.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

A formal model for temporal schema versioning in object-oriented databases

Grandi

Mandreoli

2003

Data & Knowledge Engineering

View full text Add to dashboard Cite

In this paper we present a formal model for the support of temporal schema versions in object-oriented databases. Its definition is partially based on a generic (ODMG compatible) object model and partially introduces new concepts. The proposed model supports all the schema changes which are usually considered in the OODB literature, for which an operational semantics and a formal analysis of their correct behaviour is provided. Semantic issues arising from the introduction of temporal schema versioning in a conventional or temporal database (concerning the interaction between the intensional and extensional levels of versioning and the management of data in the presence of multiple schema versions) are also considered.

show abstract

“…Banerjee and Korth, 1987;Penney and Stein, 1987) and class versioning (Skarra and Zdonik, 1988;Bjornerstedt and Hulten, 1989;Monk and Sommerville, 1993). Unlike class modification which takes an existing class definition and converts its instances into those of the modified class definition, class versioning allows multiple versions of a class to coexist by retaining the old class definition as well as creating a new version.…”

Section: Problems In Evolution Of Distributed Servicesmentioning

confidence: 99%

A model for evolution of services in distributed systems

Senivongse

1996

Distributed Platforms

View full text Add to dashboard Cite

Large software systems are never static. They exist in an environment that is subject to constant changes in both functionality and technology. This is particularly a problem for large-scale distributed systems, where different components may be subject to different, divergent, pressures. This paper describes work carried out on an RM-ODP-based model for evolution of distributed application services under such conditions. It examines problems that may occur when services evolve to their new versions without corresponding evolution in their clients and presents a mechanism to preserve such old services as are still needed. The model uses the idea of 'mapping' to provide the impression of old services using their new versions. A prototype of the model has been implemented on the ANSAware platform, giving an example of how the model can be applied in a working distributed environment.

show abstract

Semantics and implementation of schema evolution in object-oriented databases

Cited by 424 publications

References 6 publications

Integrated Model-Based Software Development, Data Access, and Data Migration

Integrated Model-Based Software Development, Data Access, and Data Migration

A formal model for temporal schema versioning in object-oriented databases

A model for evolution of services in distributed systems

Contact Info

Product

Resources

About