D. J. Penney and J. Stein. Class modification in the GemStone object-oriented DBMS. In ACM Conference on Object-Oriented Programming, Systems, Languages, and Applications (OOPSLA). Oct. 1987. 16  Home/Search   Document Not in Database   Summary   Related Articles   Check

....be generated. For the change propagation problem, several solutions have been proposed and implemented in real systems, which can be ascribed to four main approaches: 1. Immediate conversion (coercion) changes are propagated via immediate object conversion used for instance in GemStone [23]; 2. Deferred conversion (lazy updates, screening) changes are propagated via deferred object conversion used for instance in ORION [4] 3. Filtering: changes are never propagated: objects are assigned to different schema versions according to their semantics indeed used for instance in ....

D. J. Penney and J. Stein. Class Modification in the GemStone object-oriented DBMS. In Proc. of the Int'l Conf. on Object-Oriented Programming Systems, Languages, and Applications (OOPSLA) , pages 111--117, Orlando, FL, December 1987.

....Previous systems do not provide a satisfactory solution to these problems. Stop the world systems guarantee that applications and later upgrades cannot interfere with transform functions of an upgrade U , but they have di#culty ordering transform functions within the same upgrade. Some systems [45, 6, 36] avoid problems by severely limiting the expressive power of transform functions, not allowing them to make any method calls. Others (e.g. 4] make the execution of transform functions order independent by maintaining two copies of the database during the upgrade. The transform functions ....

....deal with supporting application access to the same object via multiple potentially incompatible interfaces and are very di#erent from the e#ciency and correctness issues in the evolutionbased upgrade systems. The schema evolution approach is used in Orion [6] OTGEN [36] O2 [24, 53] GemStone [12, 45], Objectivity DB [44] Versant [49] and PJama [5, 4] systems, and is the only approach available in any commercial RDBMS. None of the existing schema evolution systems provides both expressive and e#cient upgrades. Furthermore, none bases the correctness of the upgrade system on the property of ....

D. J. Penney and J. Stein. Class modification in the GemStone object-oriented DBMS. In Object-Oriented Programming, Systems, Languages, and Applications (OOPSLA), October 1987.

....be generated. For the change propagation problem, several solutions have been proposed and implemented in real systems, which can be ascribed to four main approaches: 1. Immediate conversion (coercion) changes are propagated via immediate object conversion used for instance in GemStone [34]; 2. Deferred conversion (lazy updates, screening) changes are propagated via deferred object conversion used for instance in ORION [2] 3. Filtering: changes are never propagated: objects are indeed assigned to different schema versions according to their semantics used for instance in ....

D. J. Penney, J. Stein, Class Modification in the GemStone Object-Oriented DBMS, in: Proc. of the Int. Conf. on Object-Oriented Programming Systems, Languages, and Applications (OOPSLA), Orlando, FL, 1987, pp. 111--117.

....for upgrading the persistent objects. These upgrades involve 2 changes to the code implementing the persistent objects, as well as changes to the persistent objects themselves. Much research has been done on software evolution in persistent object systems. PJama [3, 12] JPS [6, 31] and GemStone [17, 40] support some form of software evolution using modified JVMs. Software evolution cannot be implemented on unmodified JVMs. 2.4 Reflective Interface for Java Metaobject protocols [23] o#er a principled way of extending the behavior of programs. Metaobjects can be used to transparently implement ....

D. J. Penney and J. Stein. Class modification in the GemStone object-oriented DBMS. In Object-Oriented Programming, Systems, Languages, and Applications (OOPSLA), October 1987.

....format using a special purpose data translation language. This approach is a powerful one, but creation of the transformer is a manual process. More recent database systems generate transformation functions based upon the changes made to the type definitions. Orion [BKKK87, KK88] and GemStone [PS87] are object oriented database systems that provide some evolution support. In these systems, evolution is defined in terms of primitive operations that change individual type definitions, such as adding instance variables to a class, removing instance variables from a class, and renaming instance ....

D. Jason Penney and Jacob Stein. Class modification in the GemStone object-oriented DBMS. In Proceedings of the ACM Conference on Object-Oriented Programming Systems, Languages, and Applications, pages 111--117, Orlando, Florida, October 1987.

....defined on specific classes. 0He distinguishes these fi om preconditions and postconditions defined on routines. n His invariant rule also requires that, when these procedures are applied, the arguments and state satisfy the preconditions for the procedures. 12Casais [31] compares the GemStone [92], Orion [9] 02 and OTGen object oriented database systems with respect to class invariants. GemStone is a registered trademark of Servio Logic. 84 In summary, in refactoring the term class ivariat is used in a manner similar to Meyer s [79] use of the term, although in refactoring the invariant ....

....invalidated because the data they reference has been altered due to a schema change. Some research into OODBs has considered versionlug issues and multiple inheritance, outside the scope of this refactoring research. Conversely, OODB research has not focused on 2Other systems include Gemstone [92], 02 and OTGen. Casais [31] comptres features of these object oriented database systems with regard to schema evolution. 122 several topics important in refactoring, such as simplifying conditional expressions using invariants, and converting an association modeled using inheritance into an ....

D. Jason Penney and Jacob Stein. Class modification in the GemStone object-oriented dbms. In Proceedings of OOPSLA '87, 1987.

....policies for different application requirements. The elements of the DCDO solution are not necessarily unique and fundamentally different from existing techniques to solve related problems. In particular, the model and implementation uses ideas from schema evolution in object oriented databases [6, 7, 8, 19, 22, 54, 55, 56, 62, 63, 64], and from Microsoft s Component Object Model [15, 26, 53] However, these approaches were not designed for distributed object computing systems, which impose different constraints and challenges. High level designs appropriate for this environment have not yet been developed to take advantage of ....

....of Chapter 4 have been adapted. This section concentrates on strategies that deal with the effects that changing a class has on existing instances and applications programs. 3. The schema evolution literature contains several examples of more complete and detailed taxonomies for different OODBMSs [6, 62, 48]. CHAPTER 7. RELATED WORK 138 7.2.1 Class Modification Class modification is the process of changing a single version of a database schema, and updating the contents of the database to reflect that schema. Examples of OODBMSs that support class modification include Orion, GemStone, OTGen, and O ....

[Article contains additional citation context not shown here]

Penney, D.J., Stein, J., "Class modification in the GemStone object-oriented DBMS," OOPSLA `87: Proceedings of the Conference on Object-Oriented Programming: Systems, Languages, and Applications, pp. 111-17, 1987.

No context found.

D. J. Penney and J. Stein. Class modification in the GemStone object-oriented DBMS. In ACM Conference on Object-Oriented Programming, Systems, Languages, and Applications (OOPSLA). Oct. 1987. 16

No context found.

D. J. Penney and J. Stein, "Class modification in the GemStone object-oriented dbms," in OOPSLA87, (Orlando, Florida), pp. 111--117, 1987.

No context found.

D. J. Penney and J. Stein. Class Modification in the GemStone object-oriented DBMS. In Proc. of Int'l Conf. on Object-Oriented Programming Systems, Languages, and Applications (OOPSLA), December 1987.

No context found.

D. J. Penney and J. Stein. Class Modification in the GemStone object-oriented DBMS. In Proc. of Int'l Conf. on Object-Oriented Programming Systems, Languages, and Applications (OOPSLA), December 1987.

No context found.

Penney, D. J. / Stein, J. "Class modification in the Gemstone Object-Oriented DBMS" OOPSLA '87 proceedings

No context found.

D.J. Penney and J. Stein. Class Modification in the GemStone Object-Oriented DBMS. In N. Meyrowitz, editor, Proceedings of the ACM Conference of Object-Oriented Systems, Languages and Applications (OOPSLA), pages 111--117, Orlando, Florida, October 1987.

No context found.

D.J. Penney and J. Stein. Class Modification in the GemStone Object-Oriented DBMS. In N. Meyrowitz, editor, Proceedings of the ACM Conference of Object-Oriented Systems, Languages and Applications (OOPSLA), pages 111--117, Orlando, Florida, October 1987.

No context found.

D.J. Penney and J. Stein. Class Modification in the GemStone Object-Oriented DBMS. In N. Meyrowitz, editor, Proceedings of the ACM Conference of Object-Oriented Systems, Languages and Applications (OOPSLA), pages 111--117, Orlando, Florida, October 1987.

No context found.

D. J. Penney and J. Stein. Class Modification in the GemStone object-oriented DBMS. In Proc. of the Int'l Conf. on Object-Oriented Programming Systems, Languages, and Applications (OOPSLA), pages 111--117, December 1987.

No context found.

D. Jason Penney and Jacob Stein. Class Modification in the GemStone Object-Oriented DBMS. In Proceedings of the Conference on Object-Oriented Systems, Languages and Applications (OOPSLA), Orlando, Florida, USA, pages 111--117, October 1987.

No context found.

D. Penney and J. Stein. Class modification in the GemStone objectoriented DBMS. In Proc. OOPSLA '87, pages 111--117, Orlando, FL, October 1987. 66

No context found.

D. J. Penney and J. Stein. Class modification in the GemStone object-oriented DBMS. In Object-Oriented Programming, Systems, Languages, and Applications (OOPSLA), October 1987.

No context found.

D. Jason Penney and Jacob Stein. Class modification in the GemStone object-oriented DBMS. In Object-Oriented Programming, Systems, Languages, and Applications (OOPSLA), October 1987. 162

No context found.

D. J. Penney and J. Stein. Class modification in the GemStone object-oriented DBMS. In Object-Oriented Programming, Systems, Languages, and Applications (OOPSLA), October 1987.

No context found.

Penney, D.J. and Stein, J. Class modification in the GemStone object-oriented DBMS. OOPSLA '87 (SIGPLAN Notices), 22(12):111-117. 1987.

No context found.

D. J. Penney and J. Stein. Class Modification in the GemStone object-oriented DBMS. In Proc. of the Int'l Conf. on Object-Oriented Programming Systems, Languages, and Applications (OOPSLA), pages 111--117, Orlando, FL, December 1987.

No context found.

D. Jason Penney and Jacob Stein. Class Modification in the GemStone object-oriented DBMS. In Norman Meyrowitz, editor, Proceedings of the Conference on Object-Oriented Programming Systems, Languages and Applications, Association of Computing Machinery, 1987.

No context found.

Jason D. Penney and Jacob Stein. Class modification in the GemStone objectoriented DBMS. In Norman Meyrowitz, editor, Object-Oriented Programming Systems, Languages and Applications Conference, in Special Issue of SIGPLAN Notices, pages 111--117, Orlando, Florida, December 1987. ACM, ACM Press. Special Issue of SIGPLAN Notices, Vol.22, No.12.

First 50 documents  Next 50

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC