Proceedings of the Fourth International Conference on Information and Knowledge Management - CIKM '95 1995
DOI: 10.1145/221270.221595
|View full text |Cite
|
Sign up to set email alerts
|

Towards supporting hard schema changes in TSE

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
5
0

Year Published

2000
2000
2008
2008

Publication Types

Select...
1
1

Relationship

0
2

Authors

Journals

citations
Cited by 2 publications
(5 citation statements)
references
References 7 publications
0
5
0
Order By: Relevance
“…Only for capacity-increasing changes, the actual database schema is changed. Besides the set of primitive changes known from other approaches, TSE was extended to handle more complex changes [Ra and Rundensteiner, 1995a].…”
Section: Object-oriented Datawarementioning
confidence: 99%
See 1 more Smart Citation
“…Only for capacity-increasing changes, the actual database schema is changed. Besides the set of primitive changes known from other approaches, TSE was extended to handle more complex changes [Ra and Rundensteiner, 1995a].…”
Section: Object-oriented Datawarementioning
confidence: 99%
“…Views are an integral part of many database systems and are commonly used to continuously support different versions of a schema [Liu et al, 1993, 1994, Ra and Rundensteiner, 1995a,b, 1997, Crestana-Jensen et al, 2000, or to support coupled evolution without having to change or recreate the original database [Tresch andScholl, 1993, Brèche et al, 1995]. In modelware, grammarware and XMLware, (editable) views are not widely used, hence their application to coupled evolution is lacking.…”
Section: Feature Portabilitymentioning
confidence: 99%
“…Systems that enable interoperability for multiple software applications in dynamic environments must allow applications to evolve and flexibly change their data requirements, while minimizing or even eliminating the impact of such change on other existing applications. Several approaches [3,11,15,17,18] have been proposed to support schema evolution and/or data integration needs by using object-oriented views. Nevertheless, these approaches run into a potential problem of generating a large number of schema versions over time resulting in an excessive build-up of classes and underlying object instances, not all being necessarily still in use.…”
Section: Motivationmentioning
confidence: 99%
“…In transparent schema evolution systems [17,18,21], each user 3 constructs a customized interface by selecting a subset of classes from the shared database. All the schema change requests made by the developer are issued against her customized view schema with which she is familiar (Figure 1(a)).…”
Section: The Tse System: Problem Descriptionmentioning
confidence: 99%
See 1 more Smart Citation