| G. Graefe and D. Maier. Query Optimization in Object-Oriented Database Management Systems with Encapsulated Behaviour. Technical report, Oregon Graduate Center, 1989. |
....is an issue that cannot be ignored. Finally, object oriented queries may contain method (i.e. function) calls. This yields the need to consider a preliminary phase to the optimization process which consists in finding the methods code (and eventually translates it to an algebraic formalism) [12]. One encounters then problems raised by the overloading of methods name which are common to object oriented languages. The goal of our work is not to introduce yet another technique for the optimization of object oriented queries, but to integrate in a common simple framewok the different ....
G. Graefe and D. Maier. Query Optimization in Object-Oriented Database Management Systems with Encapsulated Behaviour. Technical report, Oregon Graduate Center, 1989.
....the object, as illustrated by the constraints that must be declared in the GemStone example of Section 3.1.1. One suggestion for dealing with the privacy violation issue has been to reveal parts of the internal object structure in the object protocol, and only allow indexes on revealed structures [GM87]. An alternative in ODBMSs supporting the concept of attributes or properties visible at object interfaces would be to only define indexes for those attributes. However, if an attribute was actually computed, this would involve indexing on the result of a method execution, as before. If the index ....
G. Graef and D. Maier, "Query Optimization in Object-Oriented Database Management Systems: A Prospectus," Proceedings BTW-87 (Datenbanksysteme in Buro, Technik und Wissenschaft), Darmstadt, April 1987. 254
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