Type Evolution and Instance Adaptation

Clamen, Stewart M.

doi:10.21236/ada248435

Cited by 11 publications

(4 citation statements)

References 8 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In this section, we discuss our proposal for a new meta‐model based on class versioning . Our meta‐model is used for representing in the database the data models of applications through its basic entities: data objects and meta‐objects.…”

Section: The Aspect‐oriented Framework For Object Orthogonal Persistencementioning

confidence: 99%

Modularizing application and database evolution - an aspect-oriented framework for orthogonal persistence

Pereira

Perez-Schofield

Ortín

2016

Softw. Pract. Exper.

View full text Add to dashboard Cite

Summary In the maintenance of software applications, database evolution is one common difficulty. In object‐oriented databases, this process comprises schema evolution and instance adaptation. Both tasks usually require significant effort from programmers and database administrators. In this paper, we propose orthogonal persistence and aspect‐oriented programming to support semi‐transparent database evolution. A default mechanism for instance evolution is defined, but the user may provide modularized solutions using the aspect‐oriented paradigm. We present our framework AOF4OOP to test the feasibility of our proposed approach. This prototype allows programmes to transparently access data in other versions of the database schema. We evaluate our framework, comparing it to related approaches using two real applications and measuring the improvement of the productivity of the programmer. Copyright © 2016 John Wiley & Sons, Ltd.

show abstract

Section: The Aspect‐oriented Framework For Object Orthogonal Persistencementioning

confidence: 99%

Modularizing application and database evolution - an aspect-oriented framework for orthogonal persistence

Pereira

Perez-Schofield

Ortín

2016

Softw. Pract. Exper.

View full text Add to dashboard Cite

show abstract

“…The work on schema or class versioning (e.g., [26,49,22]) considers multiple co-existing versions of a schema or class. The work on object instance evolution (e.g., [8,31]) considers selective transformation of some but not all objects in a class.…”

Section: Related Workmentioning

confidence: 99%

Lazy modular upgrades in persistent object stores

Boyapati

Liskov

Shrira

et al. 2003

Proceedings of the 18th Annual ACM SIGPLAN Conference on Object-Oriented Programing, Systems, Languages, and Applications

View full text Add to dashboard Cite

Persistent object stores require a way to automatically upgrade persistent objects, to change their code and storage representation. Automatic upgrades are a challenge for such systems. Upgrades must be performed in a way that is efficient both in space and time, and that does not stop application access to the store. In addition, however, the approach must be modular: it must allow programmers to reason locally about the correctness of their upgrades similar to the way they would reason about regular code. This paper provides solutions to both problems.The paper first defines upgrade modularity conditions that any upgrade system must satisfy to support local reasoning about upgrades. The paper then describes a new approach for executing upgrades efficiently while satisfying the upgrade modularity conditions. The approach exploits object encapsulation properties in a novel way. The paper also describes a prototype implementation and shows that our upgrade system imposes only a small overhead on application performance.

show abstract

“…Under schema evolution, existing instances must be converted to the new format (the mechanisms for achieving this are discussed in Section 4.2) and thus existing applications are rendered incompatible. Versioning promotes program compatibility by leaving the existing definition in place (Zdonik 1990;Clamen 1992). …”

Section: Domain/type Evolutionmentioning

confidence: 99%