The following sections outline the runtime interfaces you can use to access Kodo-specific functionality from JDO. Each interface contains services and convenience methods missing from the JDO specification. Kodo strives to use the same naming conventions and API patterns as standard JDO methods in all extensions, so that Kodo JDO APIs feel as much as possible like standard JDO APIs.
interface extends the basic
javax.jdo.PersistenceManagerFactory with Kodo-specific
offers APIs to obtain managed and unmanaged
PersistenceManagers from the same factory, to
access the query cache, and to perform other Kodo-specific
operations. See the
interface Javadoc for details.
PersistenceManagers implement the
interface. This interface extends the standard
javax.jdo.PersistenceManager. Just as the
PersistenceManager is the primary
window into JDO runtime services, the
KodoPersistenceManager is the primary window from JDO
into Kodo-specific functionality. We strongly encourage you to
investigate the API extensions this interface contains.
Kodo extends JDO's standard query functionality with the
kodo.jdo.KodoQuery interface. See its
details on the convenience methods it provides.
kodo.jdo.KodoExtent offers convenience methods
not found in standard
Kodo expands JDO's standard
Section 10.1, “Data Cache” has detailed information on
Kodo's data caching system, including
Kodo includes a JDO-flavored facade to its internal query cache.
kodo.jdo.QueryResultCache includes APIs much
like those in the
acting on queries rather than persistent objects. See
Section 10.1.3, “Query Cache” for details on query caching
Kodo goes one step further, extending
to add additional JDBC-specific tuning methods.
Unless you have customized Kodo to use a non-relational back-end
(see Section 9.9, “Non-Relational Stores”), all
FetchPlans in Kodo implement
JDBCFetchPlan, so feel free to cast to
kodo.jdo.KodoJDOHelper is a static helper
class that adds Kodo-specific utility methods to