[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3857?page=c...
]
Elhanan Maayan updated HHH-3857:
--------------------------------
Attachment: TestProject.zip
unable to re-produce , but using mysql environment.
dyanmic update doesn't work if unsaved-value is present at ID or
at version declaration
---------------------------------------------------------------------------------------
Key: HHH-3857
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3857
Project: Hibernate Core
Issue Type: Bug
Components: core
Affects Versions: 3.2.4
Environment: DB:Oracle 11G, WAS 6.1, Transaction suport from EJB, Spring or
TransactionCallback from hibernate.
Reporter: Amardeep Singh
Priority: Minor
Attachments: TestProject.zip
If unsaved-value is present at ID or version declaration the dynamic update is not
working.
So the following mapping will not update the columns dynamically.
<hibernate-mapping>
<class table="LPN" name="com.xxx.LPN"
dynamic-insert="true" dynamic-update="true">
<id type="java.lang.Long" column="LPN_ID"
access="property" name="lpnId" unsaved-value="null">
<generator class="sequence">
<param name="sequence">LPN_ID_SEQ</param>
</generator>
</id>
<version type="java.lang.Long" column="HIBERNATE_VERSION"
access="field" name="hibernateVersion"/>
but if I remove the *unsaved-value=null* from above mapping then it would start working.
This is not a blocker for us but looks like we cannot have both things working at same
time for us.
--
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....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira