Despite the superior expressive power of the Object-Oriented Database Management System (OODBMS) in comparison to the established relational systems, the acceptance of the OODBMS will ultimately depend on its performance. The key to this may well lie with how persistent objects are accessed. Discuss the design goals for the incorporation of persistence in a programming language.
What will be an ideal response?
Design goals:
? Persistence should be orthogonal to type. Persistence should be a property of object instances
and not types. It should be possible to allocate objects of any type in either volatile or
persistent store.
? There should be no run-time penalty for code that does not deal with persistent objects.
? Allocation and manipulation of persistent objects should be similar to the manipulation of
transient objects. For example, it should be possible to move objects from persistent store to
volatile store and vice versa in much the same way as it is possible to move objects from the
stack to the heap and vice versa.
? Inadvertent fabrication of object identities should be prevented.
? Language changes should be kept to a minimum.
You might also like to view...
__________ is the time at which a task becomes ready for execution.
Fill in the blank(s) with the appropriate word(s).
'A' < 'a' && 4 <= 8 || 2.5 >= 7 || 4 < yBased on the code above, which part of the expression is not evaluated?
A. 2.5 >= 7 B. 4 < y C. 2.5 >= 7 || 4 < y D. 4 <= 8