db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dag.Wan...@Sun.COM (Dag H. Wanvik)
Subject Re: is there a lower-level (non-SQL) API for Derby?
Date Mon, 05 Jan 2009 14:51:31 GMT
Tim Dugan <TDugan@prospricing.com> writes:

> I'm looking to see if Derby can be used similarly to Berkeley DB --
> a lower-level API.  Can anyone tell me?

No, there is no public lower level API.

> Maybe to the access area of the "Store Layer" which in some Derby
> documentation is described like this:
> "The Store layer is split into two main areas, access and raw. The
> access layer presents a conglomerate (table or index)/row based
> interface to the SQL layer. It handles table scans, index scans,
> index lookups, indexing, sorting, locking policies, transactions,
> isolation levels."

Right, there are internal layers in the architecture, but they do not
constitute public APIs at the present time. Note that when you use
Derby embedded combined with prepared statements, the SQL overhead is
typically low, we have measured in the order of 15-20% extra for read
operations of small records with a simple primary key (we used the
internal APIs to make a comparison), where data fit in the in-memory
cache. But YMMV, of course.

> Now that Derby is included in Java 16--I am having a really hard
> time finding Java documentation that talks about Derby.

The Java DB docs are essentially the Derby docs rebundled. You can
find them here:


The Derby version is here:



View raw message