Just to expand, the purpose of this is to prevent accidental overwrites of changes. In the previous example, we don't want Person B to overwrite Person A's changes. I see that Ignite Transaction has a concurrency mode, but it's purpose seems to be to ensure the consistency of transaction ordering, which is different from my use case. Please correct me if I'm wrong.
-- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/CacheStore-implementation-using-Hibernate-tp1423p1453.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
