Mailing-List: contact users-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@openjpa.apache.org
Received-SPF: softfail (nike.apache.org: transitioning domain of
 luk.stadler@gmail.com does not designate 216.139.236.26 as permitted sender)
Date: Wed, 30 Oct 2013 01:54:53 -0700 (PDT)
From: lukair <luk.stadler@gmail.com>
To: users@openjpa.apache.org
Message-ID: <1383123293450-7585480.post@n2.nabble.com>
Subject: Prevent Optimistic-Locks with where-clause
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi there,

We have a highly concurrent websphere application where we have a lot of
optimisticLockExceptions at the moment. I'd like to know if OpenJPA has a
feature like EclipseLink where I can directly adress the OptimisticLock
problem with @OptimisticLocking. (see for example
http://buttso.blogspot.ch/2009/10/exploring-eclipselink-optimistlocking.html)

What we would need, is a feature which works like
@OptimisticLocking(type=OptimisticLockingType.CHANGED_COLUMNS) (see link
before). This describes a locking implementation which checks each changed
field(and only those) if they were change during the process and only cause
a optimistic lock if so. This means, the Update Query will have a longer
where clause which checks for changes on only the updated fields.

I found the very same feature request in JIRA
https://issues.apache.org/jira/browse/OPENJPA-1451 where Patrick writes
about Kodo's implementation, but isn't clear about how to do that
eventually.

Thanks,
Lukas


--
View this message in context: http://openjpa.208410.n2.nabble.com/Prevent-Optimistic-Locks-with-where-clause-tp7585480.html
Sent from the OpenJPA Users mailing list archive at Nabble.com.