Multiobjects to Ease Schema Evolution in an OODBMS

Al-Jadir, Lina; Léonard, Michel

doi:10.1007/978-3-540-49524-6_25

Cited by 15 publications

(8 citation statements)

References 17 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The detailed algorithms of these primitive methods can be found in [4]. to SC, an error is returned.…”

Section: Manipulating a Multiobjectmentioning

confidence: 99%

Encapsulating classification in an OODBMS for data mining applications

Al-Jadir

2001

Proceedings Seventh International Conference on Database Systems for Advanced Applications DASFAA 2001 DASFAA-01

View full text Add to dashboard Cite

Classijication is an important task in data mining. Encapsulating classijication in an object-oriented database system requires additional features: we propose multiobjects and schema evolution. Our approach allows us to store classification functions, and to store instances of each group in order to retrieve them later: Since the database is operational, it allows us also to perform dynamic classijication, i.e. adaYremove instances to/fom groups over time. Moreover; it allows us to update classification functions (if we choose another population sample or apply another classijier) and have the instances of groups consequently reclassified. We illustrate our approach with a target mailing application.

show abstract

“…The detailed algorithms of these primitive methods can be found in [4]. to SC, an error is returned.…”

Section: Manipulating a Multiobjectmentioning

confidence: 99%

Encapsulating classification in an OODBMS for data mining applications

Al-Jadir

2001

Proceedings Seventh International Conference on Database Systems for Advanced Applications DASFAA 2001 DASFAA-01

View full text Add to dashboard Cite

show abstract

“…Table VII compares the SADES evolution features with the various research and commercial systems in the schema evolution category: ORION [3], Farandole 2 [54,55], PJama [4,56], Iris [6], Tigukat [8], PKM [7], O2 [5,57], Versant [36], Jasmine [37] and Gemstone [58]. SADES is the only system providing customizable support for structural consistency and integrated support for object versioning in the evolution model.…”

Section: Comparison With Existing Taxonomies and Systemsmentioning

confidence: 99%

A database evolution taxonomy for object-oriented databases

Rashid

Sawyer

2005

J. Softw. Maint. Evol.: Res. Pract.

View full text Add to dashboard Cite

Like any other database application, object database applications are subject to evolution. Evolution, however, is a critical requirement in object-oriented databases as it is a fundamental characteristic of complex applications such as computer-aided design and manufacturing (CAD/CAM) and office information systems. Object-oriented databases are inherently suited to supporting such applications. In this paper we present a database evolution taxonomy for object-oriented databases. We describe a conceptual database model and use it to define the taxonomy. We also present the various invariants and rules governing the various evolution operations. The execution sequence of rules is described. An implementation of the database model and the evolution taxonomy in the Semi-Autonomous Database Evolution System (SADES), is discussed. The implementation employs aspect-oriented programming techniques to provide a flexible means of transforming objects upon evolution, and implementing some application-specific evolution primitives. A case study compares the evolution taxonomy with existing evolution approaches. The comparison demonstrates that the taxonomy and its corresponding implementation in SADES provide improved coverage of the fundamental evolution operations to which an object database might be subjected. At the same time, erosion of the database structure is avoided by maintaining a coherent and comprehensible view of historical changes. A. RASHID AND P. SAWYER• to correct mistakes in the database design; • to add new features during incremental design; and • to reflect changes in the structure of the real-world artefacts modelled in the database. Therefore, like any other database application, object database applications are subject to evolution.However, evolution is a critical requirement in object-oriented databases because their inherent support for complex data types makes them highly suitable for supporting complex applications such as computer-aided design and manufacturing (CAD/CAM) and office information systems. Due to the underlying rich data model (in contrast with conventional data-intensive record-processing applications), these applications require dynamic modifications to both the data residing within the database and the way the data has been modelled, i.e., both the objects residing within the database and the schema of the database are subject to change. Furthermore, there is a requirement to keep track of the change in case it needs to be reverted. Therefore, in addition to offering traditional database functionality such as persistence, transaction management, recovery and querying facilities, an objectoriented database management system needs to provide the ability to evolve dynamically, through various versions, both the objects and the class definitions (which form the database schema) in the database.An object database is, therefore, subject to three types of changes over its lifetime.• Class hierarchy modification: introduction of new classes, deletion of existing classes and modificatio...

show abstract

“…The evolution of object-oriented databases and relational databases, including the propagation of changes automatically down to the extension of the database, has received great attention and the research results have been included in prototypes or in commercial DBMS (see, for example [1]). However they lack the consideration of a conceptual level which allows the designer to work at a higher level of abstraction [10].…”

Section: Related Workmentioning

confidence: 99%

“…In general, database evolution activities are considered of great practical importance since they normally consume a large amount of resources [10]. As a consequence, much research has been focused on analysing ways of facilitating this type of activity [1,16].…”

Section: Introductionmentioning

confidence: 99%

An Architecture for Managing Database Evolution

Domı́nguez

Lloret

Zapata

2003

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Abstract. This paper presents an architecture for managing database evolution when all the components of the database (conceptual schema, logical schema and extension) are available. The strategy of evolution in which our architecture is based is that of 'forward database maintenance', that is, changes are applied to the conceptual schema and propagated automatically down to the logical schema and to the extension. In order to put into practice this strategy, each component of a database is seen under this architecture as the information base of an information system. Furthermore, a translation information system is considered in order to manage the translation of conceptual elements into logical schema elements. A current Oracle implementation of this architecture is also presented.

show abstract

Multiobjects to Ease Schema Evolution in an OODBMS

Cited by 15 publications

References 17 publications

Encapsulating classification in an OODBMS for data mining applications

Encapsulating classification in an OODBMS for data mining applications

A database evolution taxonomy for object-oriented databases

An Architecture for Managing Database Evolution

Contact Info

Product

Resources

About