Hi, could anyone elaborate a bit more on this statement?
Quote:
Caches data that is sometimes updated while maintaining the semantics of
"read committed" isolation level. If the database is set to "repeatable
read", this concurrency strategy almost maintains the semantics.
Repeatable read isolation is compromised in the case of concurrent writes.
This is an "asynchronous" concurrency strategy.
It's taken from ReadWriteCache javadoc:
http://docs.jboss.org/hibernate/stable/core/api/org/hibernate/cache/ReadWriteCache.htmlI can't figure out the case where the repeatable read isolation level is compromised, providing that the DB is also in repeatable read isolation mode.