9 | DELETE Queries in JPA/JPQL. For example, the EntityManager may not be aware that a cached entity object in its persistence |
9 | Query Parameters in JPA query string and use a cached compiled query program, if available. Secondly, embedding strings in |
9 | UPDATE SET Queries in JPA/JPQL with the database. For example, the EntityManager may not be aware that a cached entity object in |
9 | JPA Annotations for ClassesJPA defines three types of persistable classes which are set by the following annotations: Chapter 2 of the ObjectDB manual explains these annotations in detail. Entity and mapped super classes can be further configured by annotations that specify cache preferences and lifecycle event listener |
8 | javax.persistence.CacheStoreMode, Comparable<CacheStoreMode> Used as the value of the javax.persistence.cache.storeMode property to specify ... BYPASS Don't insert into cache. Don't insert into cache. Since: JPA 2.0 CacheStoreMode REFRESH Insert/update entity data into cache when read from database and when committed into database. Insert |
7 | ArrayIndexOutOfBoundException.ysoft.cache.objectdb.ObjectCacheDB.deleteInOpenTransaction(ObjectCacheDB.java:361) at com.ysoft.cache.objectdb.ObjectCacheDB.delete(ObjectCacheDB.java:356) at com.ysoft.cache.objectdb.ObjectCacheDB.delete(ObjectCacheDB.java:347) at eu.ysoft.safeq |
7 | javax.persistence.EntityManagerFactory Cache getCache() Access the cache that is associated with the entity manager factory (the "second level cache"). Access the cache that is associated with the entity manager factory (the "second level cache"). Returns: instance of the Cache interface Throws: IllegalStateException - if the entity manager |
0 | [ODB1] Chapter 5 - JDO Connections, it is recommended that write caching be disabled - at least for the database file and the recovery |
0 | getObjectById(oid, validate) ) This method locates a persistent instance in the cache of instances managed by this PersistenceManager. The getObjectById method attempts to find an instance in the cache with the specified JDO identity ... flag is false, and there is already an instance in the cache with the same JDO identity as the oid |
0 | javax.jdo.Query instances of affected classes in the cache are first flushed to the datastore. Instances in the cache or brought into the cache as a result of executing one of the deletePersistentAll methods undergo life ... to the application, instances of affected classes in the cache are refreshed to reflect |
