ObjectDB ObjectDB

Internal Website Search

71-80 of 200 resultsRefresh
22

EntityManager.find(entityClass, primaryKey) is slow when accessing non-existent IDs

PT3.369S read 999999 warm select all  uncached existing PT0.266S read 999999 warm select all  cached ...     read 0      hot select first cached   unexisting <- 1 PT0.331S read 999999 hot select first cached ...      hot select deep  cached   unexisting <- 2 PT0.286S read 999999 hot select deep  cached   existing
21

significant performance decrease

to around 30% when the number of entities was just half of the current). We tried to optimize the cache ... ="write" /> <locking version-check="true" /> <processing cache="2048mb" max-threads="10" synchronized="false"/> <query-cache results="1024mb" programs="500" /> <extensions drop="temp,tmp
4

getSharedCacheMode()

the specification of how the provider must use a second-level cache for the persistence unit. The result of this method corresponds to the shared-cache-mode element in the persistence.xml file. Returns: the second-level cache mode that must be used by the provider for the persistence unit Since: JPA 2.0
4

Server out of memory exceptions

side was stable. Memory usage on the server side became higher mainly due to increasing page cache size. I see that the test uses 4 different databases (2 large and 2 small). The default size of each page cache (per database) is 64MB, so the cache of the two large databases consumes at least 128MB (probably
0

javax.jdo.identity.SingleFieldIdentity

name. Since: JDO 2.0 int hashCode() Return the cached hash code. Return the cached hash code. Returns: the cached hash code. Since: JDO 1.0 void readExternal(ObjectInput arg0)throws IOException
0

javax.jdo.identity.ShortIdentity

class name. Since: JDO 2.0 int hashCode() Return the cached hash code. Return the cached hash code. Returns: the cached hash code. Since: JDO 1.0 void readExternal(ObjectInput in)throws IOException
0

checkConsistency()

Method javax.jdo.PersistenceManager void checkConsistency() Validates the PersistenceManager cache ... transaction is active, this method verifies the consistency of instances in the cache against the datastore ... the consistency of the instances in the cache against the datastore. If any inconsistencies are detected
0

setDetachAllOnCommit(flag)

the cache after commit is defined by the retainValues flag. With this flag set to true, during beforeCompletion all cached instances are prepared for detachment according to the fetch plan in effect ... callback, all detachable persistent instances in the cache transition to detached; non-detachable
0

javax.jdo.identity.LongIdentity

. Since: JDO 2.0 int hashCode() Return the cached hash code. Return the cached hash code. Returns: the cached hash code. Since: JDO 1.0 void readExternal(ObjectInput in)throws IOException
0

javax.jdo.identity.CharIdentity

hashCode() Return the cached hash code. Return the cached hash code. Returns: the cached hash code

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