Hi all,

I would like to share the following link with you:
Generally I believe that a standard for object-oriented
queries would be very benefitial for all object database-
and O-R vendors. It would allow to build a tool base on
both sides of the API.

I like Gavin King's thoughts on the matter and I am
watching closely, where the design is going. Maybe Gavin
can be the driving force to bring object-oriented queries
into JDO 2.0.

Although his API for hibernate is substantially different
to our S.O.D.A. API that we built into db4o, the principle
approach is the same:

- It should be possible to construct a query with the
minimum use of strings possible. Strings are "bad". They
are not checked during compile time and they can not be
refactored with IDEs.

- It should be possible to plug any object into a query
graph. This allows object reuse and minimizes the total
amount of code necessary.

- It should be possible to create queries step-by-step,
node-by-node. This allows the construction of queries
to be delegated to multiple method calls within an
application, a requirement to allow a high amount of
code reuse.


Our S.O.D.A. approach adds one further step:
- It should be possible to instruct the query processor
to execute user code.


It's nice to see that there are other people that
dislike JDOQL.


Kind regards,
Carl
--
Carl Rosenberger
db4o - database for objects - http://www.db4o.com