lockItem then remove then unlockItem
There is another usage pattern that is used to invalidate entries
afterQuery performing "bulk" HQL/SQL operations:
lockRegion then removeAll then unlockRegion
| Modifier and Type | Method and Description |
|---|---|
| public Object | Returns: a key which can be used to identify this collection on this same regionthe primary identifier of the Collection id, CollectionPersister the descriptor of the collection for which a key is being generated collectionDescriptor, SessionFactoryImplementor a reference to the current SessionFactory factory, String the tenant id, or null if multi-tenancy is not being used. tenantIdentifier)
Deprecated
as a consequence of
To create instances of CollectionCacheKey for this region, Hibernate will invoke this method
exclusively so that generated implementations can generate optimised keys.
SessionFactoryImplementor being deprecated.
|
| public Object | Returns: original key passed togenerateCacheKeykey previously returned from cacheKey)generateCacheKeyPerforms reverse operation to |
| generateCacheKey | back to summary |
|---|---|
| public Object generateCacheKey(Object id, CollectionPersister collectionDescriptor, SessionFactoryImplementor factory, String tenantIdentifier)
Deprecated as a consequence of To create instances of CollectionCacheKey for this region, Hibernate will invoke this method exclusively so that generated implementations can generate optimised keys.
| |
| getCacheKeyId | back to summary |
|---|---|
| public Object getCacheKeyId(Object cacheKey) Performs reverse operation to
| |