Eclipse Community Forums: EclipseLink

Help

Home

Home » Eclipse Projects » EclipseLink » Locking and Version

Show: Today's Messages :: Show Polls :: Message Navigator

Locking and Version [message #759243]

Sun, 27 November 2011 21:37

pop prem
Messages: 20
Registered: June 2010

Junior Member

Hi,

I need to clarify some of my doubts related to eclipselink locking.

How can i configure eclipselink that a row level lock should be held rather than a table level? I'm using spring transactions and havn't touched any configurations related to locking in eclipselink, so it uses default locking (optimistic). Please correct me if i'm wrong here.

I have added @Version column in my entity classes to support locking mechanism. Is this a good way or do i have to use the Locking API in code too like entityManager.lock or @Lock etc? Should i use these locks in code even when i have configured database transactions through spring? I'm confused with the usage of code level locking and declarative transaction management.

Thanks.

Report message to a moderator

Re: Locking and Version [message #759369 is a reply to message #759243]

Mon, 28 November 2011 08:48

James Sutherland
Messages: 1844
Registered: July 2009

Senior Member

Row versus table locks are up to your database, and can only be configured on your database. You can execute a native SQL query if you really want to lock an entire table, although not normally a good idea.

See,
http://en.wikibooks.org/wiki/Java_Persistence/Locking

James : Wiki : Book : Blog

Report message to a moderator

Previous Topic:	EclipseLink Maven repository missing
Next Topic:	Locking and Version

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Wed May 22 17:59:33 EDT 2013