Current status of LDB

Changed the source files to work with SHORE 3.0 interim snapshot and gcc 3.2.

Minor Changes:

• Fixed unions and the XML example.
• Made it work for RHL 9.0.

Changes:

• Added support for methods for the RPC interface.
• Fixed the error messages for the RPC interface.
• Added the executables oql_client/odl_client for oql/odl (through RPC).
• Created a complete example using Java (directory example/java).
• Fixed various bugs.

Changes:

• Now we support updates in the C++/Java bindings.

• dest += query and dest -= query don't work for collections of strings when the query is a constant string. eg, e.degrees += "PhD" doesn't work. Use dest := dest+set(query) instead.

Changes:

• Now LDB automatically enforces ODL relationships.
• Added Java and C++ interfaces based on remote procedure calls (RPCs). See the Language Description. Currently, it allows querying but not updating. Looks as ugly as ODBC/JDBC. Changed VOODOO to work with the new RPCs. Added a new tcl script for ad-hoc OQL queries.

• LDB is still single-threaded/single-user. The problem is that, in the current Shore interim release, POSIX thread cores don't work on Linux. I have to wait for a fix.
• Need to support updates in the C++/Java bindings.
• Unions (used by the XML example) need to be fixed.

First release of LDB based on SHORE 2.0. The major difference between the old Lambda-DB and the new LDB is that LDB uses the SHORE 2.0 storage manager while Lambda-DB uses the higher-level SDL layer of SHORE 1.1.1. The main reason for this major change is that the SHORE project does not support SDL any more. To use the SHORE 2.0 storage manager, we had to write our own VAS (Value-Added Server), which looks similar to that of SDL (directory storage_manager). Like SHORE 2.0, LDB can hopefully be ported to many different platforms, even though we have only test it on Linux and Solaris. Currently, LDB is single-user (not client-server) and does not automatically enforce ODL relationships (must be set by hand). These will be fixed in a future release. Finally, the evaluation engine needs lots of fine-tuning.

Please look at Lambda-DB status for the status of the old lambda-DB releases.