zeravlai wrote : Also Manik, in mvcc-entity predefined cache config,
there's a comment saying that READ_COMMITTED is as strong as neccesary for most
2nd level cache use cases. What's the meaning of this sentence bearing in mind
your reply ?
R_C is (slightly) more efficient that R_R in our MVCC
Hibernate has a first level cache in it's session. Which will provide you with
R_R regardless of how your second level cache is configured.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4220896#4220896
Reply to the post :
Thanks for the info Manik,
so, then, given the tree structure of the cache and the R_R isolation level,
would it be possible to fall into a phantom read anomaly (considering the
JPA/Hibernate) ?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4221001#4221001
Also Manik, in mvcc-entity predefined cache config, there's a comment saying
that READ_COMMITTED is as strong as neccesary for most 2nd level cache use
cases. What's the meaning of this sentence bearing in mind your reply ?
Thanks again.
View the original post :
