WSK only works for repeatable read. By default we use read committed.
On 27 Sep 2012, at 16:07, Mircea Markus <mircea.markus(a)jboss.com> wrote:
Hi,
By default our optimistic transactions don't have writeSkewCheck enabled so their
behaviour is counterintuitive for the user. That's because they don't fault the
commit in the case of a concurrent change.
Anyone can remember why these defaults are being used?
I'd rather have optimistic transactions with WSK enabled by default so that we
won't confuse users.
Cheers,
--
Mircea Markus
Infinispan lead (
www.infinispan.org)
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev
--
Manik Surtani
manik(a)jboss.org
twitter.com/maniksurtani
Platform Architect, JBoss Data Grid
http://red.ht/data-grid