From: <leg...@at...> - 2003-10-15 11:42:26
|
Message: The following issue has been re-assigned. Assignee: Gavin King (mailto:ga...@in...) Assigner: Gavin King (mailto:ga...@in...) Date: Wed, 15 Oct 2003 6:41 AM Comment: agreed. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-399 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-399 Summary: Query.setLockMode support for databases that do not support FOR UPDATE OF Type: Improvement Status: Assigned Priority: Major Project: Hibernate2 Components: core Versions: 2.0.3 Assignee: Gavin King Reporter: Gerjon de Vries Created: Tue, 14 Oct 2003 8:02 AM Updated: Wed, 15 Oct 2003 6:41 AM Environment: MySql 3.23.48-Max, using mysql-connector-java-3.0.8-stable Description: Query.setLockMode("alias", LockMode.UPGRADE) won't set a lockmode if the dialect does not support "FOR UPDATE OF" syntax. However, if the query is on only one table, or if all table aliases have a lockmode.upgrade, it could still set the lockmode by using "FOR UPDATE" instead of FOR UPDATE OF. Also, instead of silently ignoring the lockmode if the dialect does not support FOR UPDATE OF, one could make a case case for using "FOR UPDATE" instead, for such dialects. This would assure the at least the specified locks are set, while the current behaviour is to just ignore the locks. --------------------------------------------------------------------- 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 |