ObjectDB ObjectDB

Internal Website Search

31-40 of 200 resultsRefresh
16

Working with JPA Entity Objects

at it is that the persistence context also functions as a local cache for a given EntityManager. ObjectDB also manages a level 2 shared cache for the EntityManagerFactory as well as other caches as explained in
13

Setting and Tuning of JPA Queries

). This could be useful when the shared L2 cache is enabled and entity objects may already be available in the cache. Setting Query Hint (Scopes) Query hints can be set in the following scopes (from global
13

Retrieving JPA Entity Objects

of the database. The persistence context serves as a cache of retrieved entity objects. If a requested ... with data that is retrieved from the database (or from the L2 cache - if enabled). The new entity object
13

JPA Miscellaneous

This section contains miscellaneous JPA types. The PersistenceUtil and PersistenceUnitUtil interfaces provide general utility methods: The Cache interface and the CacheRetrieveMode and CacheStoreMode enum types serve in managing the EntityManagerFactory's shared (level 2) cache: Other enum types are provided for setting of various JPA operations:
10

javax.persistence.SharedCacheMode

, Comparable<SharedCacheMode> Specifies how the provider must use a second-level cache for the persistence unit. Corresponds to the value of the persistence.xml shared-cache-mode element, and returned as ... SharedCacheMode ALL All entities and entity-related state and data are cached. All entities and entity
1

javax.jdo.PersistenceManager

of interest to the listener Since: JDO 2.0 void checkConsistency() Validates the PersistenceManager cache with the datastore. Validates the PersistenceManager cache with the datastore. This method has no effect ... of instances in the cache against the datastore. An implementation might flush instances as
1

javax.jdo.datastore.DataStoreCache

implementations allow instances to be cached in a second-level cache, and allow direct management of the cache by knowledgeable applications. This interface standardizes this behavior. Since: JDO 2.0 void evict(Object oid) Evict the parameter instance from the second-level cache. Evict the parameter
1

javax.jdo.datastore.DataStoreCache.EmptyDataStoreCache

support a second-level cache. Since: JDO 2.0 DataStoreCache.EmptyDataStoreCache() Since: JDO 2. Since: JDO 2.0 void evict(Object oid) Evict the parameter instance from the second-level cache. Evict the parameter instance from the second-level cache. Parameters: oid - the object id of the instance
1

[ODB1] Chapter 9 - ObjectDB Explorer

the Explorer into your Java code. Refreshing the Cache When a database is open in the Explorer using client ... another process the viewer windows in the Explorer might display content from the cache that does not reflect the real content in the database. In this case you can refresh the cache and the viewer
0

[ODB1] Chapter 8 - ObjectDB Server

the cache and improve server performance: > java -server -Xmx512m com.objectdb.Server start To stop

Getting Started

ObjectDB is very easy to use. Follow the Getting Started Tutorial and the Quick Tour manual chapter and in minutes you may be able to write and run first Java programs against ObjectDB.

Prior knowledge or experience in database programming (SQL, JDBC, ORM, JPA, etc.) is not required, but some background in using the Java language is essential.

Need Help?

  1. Search ObjectDB website
  2. Read the FAQ
  3. Follow the Tutorials
  4. View or post in the forum
  5. Search or file an issue
  6. Contact support