I am not sure @DocumentId is the right place to host it. Should it be rather on
the embedding entity to be able to customize in which scenario id is indexed?
In a way, includePath="city.id" is the indicator I am looking for.
On 16 févr. 2012, at 11:54, Sanne Grinovero wrote:
> This is related t
Hi all,
Re: http://java.dzone.com/tips/clearing-hibernate-second-leve
Re: https://community.jboss.org/message/718710#718710
Shouldn't Hibernate offer an API (independent of the cache provider) to clear
all 2LC caches, including all entity, all collection and all query/timestamp
caches?
Beneath
There is already:
sf.getCache().evictEntityRegions()
sf.getCache().evictCollectionRegions()
sf.getCache().evictDefaultQueryRegion()
sf.getCache().evictQueryRegions()
I can see a benefit to having evictQueryRegions() imply
evictDefaultQueryRegion()
But, I fail to see a real benefit to a singular
Well one reason would be to trigger clearing of the update-timestamps
cache. I am leery of exposing a method to allow just that
fuinctionality.
On Wed 22 Feb 2012 10:00:43 AM CST, Steve Ebersole wrote:
> There is already:
> sf.getCache().evictEntityRegions()
> sf.getCache().evictCollectionRegio
