OODBs have been used for many non-traditional application areas like multimedia databases and geographic information systems.
Concurrency control in OODBs is more complicated than concurrency control schemes traditional relational databases due to the following reason[5,6].
We use both a calculus and an algebra as intermediate forms because the calculus closely resembles current OODB languages and is easy to put into canonical form, while the algebra is lower-level and can be directly translated into the execution algorithms supported by database systems.
The simplicity of our method is due to the monoid comprehension calculus as an intermediate form for OODB queries.
1991; Diaz and Jaime 1997], adds active facilities to the OODB ADAM, in which instances, classes, rules, and events are represented uniformly as database objects.
1994] is an active rule system for the [O.sub.2] commercial OODB [Deux et al.
The following sections explain the extension of the Elk Scheme interpreter into an OODB
that has been specialized for hypermedia.
and distributed systems, it is the behavioral nature of systems where objects persist over long periods of time that causes problems.
MovieComponents "wrap" QuickTime movies, large multimedia data objects (from five to several hundred MB) too complex to be easily stored in the hypermedia's OODB
. Hence, they are better handled using MovieFiles referred to by the component contents. In this case, the component contents is again a file identification object.
A cooperative commit will update the part in the OODB
. A variant of this cooperation mode is having each user make changes that are not immediately committed, but which may be undone without other users seeing them.
Combining an OODB
with a transparent object-oriented interprocess communications mechanism we have described to be considerably simplified.
system is faster than both the in-house system and POSTGRES on the insert operation because it clusters different record types on the same disk page.