ObjectDB ObjectDB

Internal Website Search

101-110 of 200 resultsRefresh
16

Query results are not up to date for entities, not primitives

This could be the result of getting query results from the cache. There is no difference between criteria queries and string based JPQL queries regarding the cache (and actually every criteria query it converted by ObjectDB to JPQL). But some cache operations cannot be used with queries that return
16

JBOSS AS7 7.1.1 - Entity not persisted and createNamedQuery fire exception

get persisted. No exception either. Some cache misconfiguration ? As for the NamedQuery problem ... reasonable. Maybe some configuration can be done at JTA or cache level of JBoss in the jboss configuration ... " default-cache-container="hibernate">             <cache-container name="hibernate" default-cache
15

OptimisticLockException

amount of code. questions: 1. is there a way to do this automatically (or alternatively to turn off caching??) 2 ... Moshal You can disable the L2 cache (or empty it with evict) and empty the EntityManager (L1) cache ... locks: a) is the object is globally locked at the database when retrieved from L2 cache ? b
3

Use temporary files to enable very large transactions

because the objects are kept in the first level cache of ObjectDB. In the forum thread http://www.objectdb ... the first level cache (by flush() and detach()). But an array of bytes, any ObjectDB memory ... the byte arrays are the db cache pages because the size of the arrays is identical to the cache page
2

SharedCacheMode.ALL

Enum Constant javax.persistence.SharedCacheMode ALL All entities and entity-related state and data are cached. Since: JPA 2.0
2

clearCachedProviders()

Method javax.persistence.spi.PersistenceProviderResolver void clearCachedProviders() Clear cache of providers. Since: JPA 2.0
0

javax.jdo.annotations.Cacheable

javax.jdo.annotations Annotation Cacheable Target: Classes and fields (including property get methods) Annotation to specify that this class/field/property is cacheable in a Level 2 cache. This corresponds to the xml attribute "cacheable" of the "class", "field" and "property" elements. Since: JDO
0

getIgnoreCache()

Method javax.jdo.PersistenceManager boolean getIgnoreCache() Get the ignoreCache setting for queries. IgnoreCache set to true specifies that for all Query instances created by this PersistenceManager, the default is the cache should be ignored for queries. Returns: the ignoreCache setting. Since: JDO 1.0
0

evictAll()

Method javax.jdo.PersistenceManager void evictAll() Mark all persistent-nontransactional instances as no longer needed in the cache. It transitions all persistent-nontransactional instances to hollow. Transactional instances are subject to eviction based on the RetainValues setting. Since: JDO 1.0 See Also: evict(Object pc)
0

evictAll(subclasses, pcClass)

Method javax.jdo.PersistenceManager void evictAll( boolean subclasses, Class pcClass ) Mark the parameter instances as no longer needed in the cache. Parameters: subclasses - if true, mark instances of subclasses also pcClass - the class of instances to evict Since: JDO 2.1

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