The problems are (1) what provider to use and (2) what access strategy
to use.
We are not like most other providers that only offer a single type of
cache and strategy.
On 05/02/2011 04:09 PM, Emmanuel Bernard wrote:
> I agree with you.
> Today, if you do not / forgot to specify
> "javax.pers
I agree with you.
Today, if you do not / forgot to specify "javax.persistence.sharedCache.mode",
you're up for a long debugging ride before figuring it out.
So +1 for ENABLE_SELECTIVE.
That is the default if people use hbm.xml files + SessionFactory anyways.
Emmanuel
On 2 mai 2011, at 15:55, S
The JPA specification allows us to choose what happens when
shared-cache-mode is not specified (JPA 2.0 3.7.1 specification).
Hibernate currently (as best as I can tell), defaults to
shared-cache-mode of NONE.
Should we change the shared-cache-mode default to ENABLE_SELECTIVE in
Hibernate 4.0?
Mostly we discussed the new metamodel code and whether to push forward
with it for 4.0. Also we discussed EntityManagerFactory building.
[05/02/11 11:01] Meeting ended Mon May 2 16:01:52 2011 UTC.
Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
[05/02/11 11:01] Minut
Hi,
Great summary Gunnar :-)
I also thought about the API for quite some time and could not find
a solution keeping the current "grouping" and the single invocation chain
w/o introducing cases for invalid usages.
Initially I thought about keeping these inconsistencies for the sake
of keeping the c
