Message:
The following issue has been closed.
Resolver: Gavin King
Date: Tue, 21 Oct 2003 2:00 AM
Ummmm .... I can't see any reason to support this. AFAICT, this is an exotic feature that means diff things on diff databases. If you want to continue this discussion, the devel list is the correct place.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-398
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-398
Summary: Support for LOCK IN SHARE MODE
Type: New Feature
Status: Closed
Priority: Major
Resolution: WON'T FIX
Project: Hibernate2
Components:
core
Versions:
2.0.3
Assignee:
Reporter: Gerjon de Vries
Created: Tue, 14 Oct 2003 7:35 AM
Updated: Tue, 21 Oct 2003 2:00 AM
Environment: Not specific
Description:
Currently hibernate supports explicit locking strategies via LockMode.UPGRADE and LockMode.READ. However, there does not seem to be a lockmode that represents the SELECT xxxx LOCK IN SHARE MODE. (I.e. to select row(s) that should not be altered by other sessions, and need not be altered by the current transaction).
Is this going to be supported?
---------------------------------------------------------------------
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
|
