Re: Is a Query langauge really necessary in an OODB?

topmind wrote:

> Well the OO approach violates *sharability* of data across
> multiple paragigms and languages. ("My method or no method")
>
> Thus, we trade one evil for another. Joyous.

The class of an object could be available to all users on the system. It is the class that holds the definition of the method. Any user can run that method on any object in that class, once the server provided the lock for it. Since objects are small items in a DB, I can see a large amount of concurrency.

May you elaborate on what you wrote? You may have an example I am not considering.  

Kyle Lahnakoski                                  Arcavia Software Ltd.
(416) 892-7784                                 http://www.arcavia.com