About cache

api-jpa

JPA Annotations for Classes

Reference (JavaDoc) of JPA 2 class annotations, including @Entity, @Embeddable, @IdClass, @Cacheable, @EntityListeners, etc.... can be further configured by annotations that specify cache preferences and lifecycle event listener policy (as explained in ...

 
issue

Terracotta Ehcache Integration

Hello , it will be good if you make alliance with terra-cotta ehcache. Their distributed memory cache is very fast.IF we mix with your engine. It will be very great for us. ... with terra-cotta ehcache. Their distributed memory cache is very fast.IF we mix with your engine. It will be very great for ...

 
api-jdo

pin(oid)

Pin the parameter instance in the second-level cache.(Method of javax.jdo.datastore.DataStoreCache)

 
api-jpa

SharedCacheMode.NONE

Caching is disabled for the persistence unit.(Enum Constant of javax.persistence.SharedCacheMode)

 
forum_thread

Problem with @Basic(fetch = FetchType.LAZY)

I have a class where two fields are annotated with @Basic(fetch = FetchType.LAZY) due to them containing quite long Strings and me loading ALL entities of the database on application startup (swing app) This class should hopefully demonstrate the problem: ... //Close everything and reopen to make sure no cache of the description / code is left behind emf = ...

 
api-jdo

Persistent.cacheable

Whether this field/property is cacheable in a Level2 cache.(Annotation Element of javax.jdo.annotations.Persistent)

 
api-jdo

makeTransactional(pc)

Make an instance subject to transactional boundaries.(Method of javax.jdo.PersistenceManager)

 
api-jdo

unpinAll(subclasses, pcClass)

Unpin instances from the second-level cache.(Method of javax.jdo.datastore.DataStoreCache)

 
api-jdo

evictAll(subclasses, pcClass)

Mark the parameter instances as no longer needed in the cache.(Method of javax.jdo.PersistenceManager)

 
forum_thread

Many connections possible? and will it makes problem in future?

Hello , we are currently making new instant messenger but we were planing to use some security addons and privileges on access some of the fields on java side.   My questions is about : 1-) Can objectdb server handle 200.000+ connections at the same time concurrently ? Does it have queue and cache ? 2-) Can we give privileges to users , for example some users can only read some fields and some just can write java fields. Some users only allowed insert ability. ... at the same time concurrently ? Does it have queue and cache ? 2-) is it dangerous to use that system on many online users ? ...