The following issue has been updated:
Updater: Gavin King (mailto:ga...@in...)
Date: Wed, 9 Jul 2003 6:39 PM
Changes:
priority changed from Blocker
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-155&page=history
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-155
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-155
Summary: Optimistic locking by columns' original values
Type: New Feature
Status: Unassigned
Priority: Minor
Project: Hibernate2
Components:
core
Versions:
2.0.1
Assignee:
Reporter: Christian Bauer
Created: Tue, 8 Jul 2003 3:36 PM
Updated: Wed, 9 Jul 2003 6:39 PM
Description:
Ability to support optimistic locking by columns' original values. When UPDATE statements
are generated, in addition to the primary key, the WHERE clause includes either all of the
columns' original values, or just the changed columns' original values. This allows
optimistic locking without requiring the datamodel to have a "timestamp" or "version"
column.
---------------------------------------------------------------------
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
|
