Message:
The following issue has been closed.
Resolver: Gavin King
Date: Tue, 21 Oct 2003 7:48 PM
This must have already been fixed in Hibernate 2.1, since FooBarTest.testRe=
fresh() tests this exact thing. Try the latest 2.1 release. :)
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?=
key=3DHB-413
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-413
Summary: session.getCurrentLockMode(obj) and session.refresh()
Type: Bug
Status: Closed
Priority: Major
Resolution: DUPLICATE
Project: Hibernate2
Components:=20
core
Versions:
2.0.3
Assignee: Gavin King
Reporter: Philippe Chal=C3=A9at
Created: Tue, 21 Oct 2003 5:33 AM
Updated: Tue, 21 Oct 2003 7:48 PM
Environment: Win XP, Linux, SAP DB
Description:
The following code doesn't have the expected behaviour :
System.out.println("=3D> " + session.getCurrentLockMode(obj));=20
session.refresh(obj, LockMode.UPDGRADE);
obj.getCode(); // To be sure that there is no pb with proxy (initialize)
System.out.println("=3D> " + session.getCurrentLockMode(obj));=20
With "show sql", it gives me this :
=3D> READ
select ik, code, noSocCom, noCliLiv from SV_Commande where ik=3D? for upd=
ate
=3D> READ=20
Philippe
---------------------------------------------------------------------
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
|
