Message:
A new issue has been created in JIRA.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-163
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-163
Summary: Table locking
Type: New Feature
Status: Unassigned
Priority: Major
Project: Hibernate2
Components:
core
Versions:
2.0.1
Assignee:
Reporter: Christian Bauer
Created: Tue, 8 Jul 2003 3:43 PM
Updated: Tue, 8 Jul 2003 3:43 PM
Description:
I would like to have a way to lock objects in a more database
independent way, and in particular to lock a table. Now I need
to make it impossible for two instances of my client application
to perform a long task in parallel, but the present locking doesn't
work with databases that does not provide a "select for update".
On the other side, I guess that most databases provide table level
locking "LOCK TABLE ...". I would be a nice to have, currently I have
to isolate databases that don't support Hibernate locking and do my
own...
Oh, in the case of SapDb the locking problem could be solved by
using a row level lock (available) instead of a select for update.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
