Citation Context

...osely defined term, a number of concepts, such as complex objects, object identity, methods, encapsulation, typing, and inheritance, have been identified as the most salient features of that approach =-=[13, 96, 113, 107, 10]-=-. One of the important driving forces behind the interest in object-oriented languages in databases is the promise they show in overcoming the, so called, impedance mismatch [74, 113] between programm...

Citation Context

...entials of functional database models, such as those proposed in in Daplex [49], Iris [14], and Omega [16]. MODM contains the basic features common to most semantic [1, 21] and object-oriented models =-=[2]-=-, such as GemStone [36], O2 [30], and Orion [28]. The model supports complex objects (aggregation), type membership (classification), subtype to supertype relationships (generalization), inheritance o...

Citation Context

...mming languages, but has found the type models typically provided in these disciplinary areas to be lacking. The database community has recently acknowledged many ofthe de ciencies of database models =-=[3, 27, 1]-=- for software engineering. In particular, the type models of database systems tend to be too simplistic. For example, traditional database systems fail to provide the basic building blocks to support ...

Citation Context

...olicy {p← q}, we require the same condition, n < p∨q—either p trusts n, or p believes that n is allowed to affect things that q is. Therefore we can write L(n) to denote the label corresponding to node n, which is {> → n;> ← n}, and express condition 1 simply as L(n) < Lo. Fabric classes may be parameterized with respect to labels or principals, so different instances of the same class may have different labels. This allows implementation of reusable classes, such as data structures that can hold information with different labels. By design, Fabric does not provide persistence by reachability [3], because it can lead to unintended persistence. Therefore, constructors are annotated to indicate on which store the newly created object should be made persistent. The call new C@s(...) creates a new object of class C whose store is identified by the variable s. No communication with the store is needed until commit. If the store of an object is omitted, the new object is created at the same store as the object whose method calls new. Objects may have non-final fields that are marked transient. These transient fields are not saved persistently, which is similar to their treatment by Java ser...