1993
DOI: 10.1007/3-540-57342-9_73
|View full text |Cite
|
Sign up to set email alerts
|

Maintaining behavioral consistency during schema evolution

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

1997
1997
2001
2001

Publication Types

Select...
4
2

Relationship

1
5

Authors

Journals

citations
Cited by 8 publications
(5 citation statements)
references
References 10 publications
0
5
0
Order By: Relevance
“…The container classes are specified manually, and code must be transformed manually if a container class is required by a code transformation rule and none is available. For strongly typed languages there are the complications discussed in [7].…”
Section: Cg Program Transformationsmentioning
confidence: 98%
See 3 more Smart Citations
“…The container classes are specified manually, and code must be transformed manually if a container class is required by a code transformation rule and none is available. For strongly typed languages there are the complications discussed in [7].…”
Section: Cg Program Transformationsmentioning
confidence: 98%
“…In this case, the code transformation rules had to be augmented somewhat in order to satisfy the type system. For a more complete discussion of type system issues see [7].…”
Section: Practical Experiencementioning
confidence: 99%
See 2 more Smart Citations
“…However, there has been surprisingly little attention paid in the database community toward this direction, although software reuse has been one of the critical issues in software engineering for the last decade. As [3] has shown, program adaptation can be exceedingly hard for typed languages (such as C++) even for simple schema changes. Therefore, it is important and beneficial to put some research effort on avoiding or minimizing program changes in anticipation of schema updates rather than trying to fix things after changes occured.…”
Section: Related Researchmentioning
confidence: 99%