Hibernate version:
3.2.4

Mapping documents:
<class table="ABC" name="com.xxx.ABC" dynamic-insert="true" dynamic-update="true">

<id type="java.lang.Long" column="ABC_ID" access="property" name="abcId" unsaved-value="null">
<generator class="sequence">
<param name="sequence">ABC_ID_SEQ</param>
</generator>
</id>
<version type="java.lang.Long" column="HIBERNATE_VERSION" access="field" name="hibernateVersion"/>

...
</class>

I have noticed that if unsaved-value property is present at id or version declaration then dynamic updated doesn't work.

Would like to know the explanation behind it for this behavior.

How did you notice it? I don't thin it's a wanted behaviour and I guess there is a problem in your testcode?

Thanks for the reply..

To get dynamic update working I guess we don't need to do any thing.

So here is the flow.

1. Start a transaction (in our case it's EJB )
2. load an object
3. Make changes to object and persist it.

So if you change the hbm file with un-saved attribute the dynamic update set to true it wil update all the column.

Following is the code snippet for my unit test case enevironment where actually I'm using transactional template from spring to have transaction.


super.performInTransaction(new TransactionCallBack()
{
public Object perform(PersistenceManager persistenceManager)
throws Exception
{
_memberData.setName("blah");
updateObject(_memberData);
return null;
}});


I haven't tried with higher version as it might be fixed also and if u r aware please let me know.