When I call saveOrUpdate, then the version field is updated even if no other fields have changed... Is there anyway to tell Hibernate not to update the version field as long as no changes have been made?


Regards,

BTJ

This isn't possible?? Shouldn't it be?

BTJ

Hi

I seem to experience something similar...

My stateless session EJB returns a Hibernate object just selected from the DB (no direct call to save or saveOrUpdate), just select via HQL.

When it returns, it commits the txn that was started on hitting the EJB AND it updates the version number and ONLY the version number.

This seems to break the optimistic concurrency contract...

has anyone experienced this with 3.1.3?
What am I doing wrong?

Thanks

Benoit

i am experiencing the same problem and is very interested if someone can explain why this is happening..??

thanks

Rasmus

Hi,

I found the same problem when I was particularly interested in Hibernate performance. The solution is really easy (even I solved it) :-)

There is a property in tag class. I paste the content of Hibernate manual:


You may declare a persistent class using the class element:



(7) dynamic-update (optional, defaults to false): Specifies that UPDATE SQL should be generated at runtime and contain only those columns whose values have changed.

(8) dynamic-insert (optional, defaults to false): Specifies that INSERT SQL should be generated at runtime and contain only the columns whose values are not null.

Best regards.

thanks for your reply javier..!
dynamic update didnt solve my problem unfortunately - the version column was still being updated when commiting the transaction with only read queries. The problem is as far as i can tell that the queried objects for some reason become dirty and therefore will be updated on commit despite haven't modified them.
I solved the problem with a session.clear() before commit - however i am not sure it is the best solution. I would like to avoid the objects from being dirty in the first place. any idea..?

sorry if this is a trivial question..

best regards
Rasmus

I cant imagine why hibernate thinks your object is "dirty"

I can suggest the following option

1. Tell hibernate not to dirty check the object by setting read only



2. set the flush mode to manual

3. Implemetn your own dirty checking for that object in an interceptor...

can you post your EJB code using Hibernate

here is the code that returns true when checking for dirty.. (it works fine if i query another table)


String queryString2 = "from Customer";
List list2 = session.createQuery(queryString2).list();


and the corresponding hbm:

<hibernate-mapping>
<class name="model.Customer" table="customer" lazy="false">
<id name="customerId" column="customer_id" type="integer">
<generator class="sequence">
<param name="sequence">customer_sequence</param>
</generator>

</id>
<version name="version" column="version"/>
<property name="firstname" column="firstname" type="string" />
<property name="lastname" column="lastname" type="string" />
<property name="street" column="street" type="string" />
<property name="postalCode" column="postal_code" type="string" />
<property name="city" column="city" type="string"/>
<property name="email" column="email" type="string"/>



<set name="bookings" inverse="true">
<key column="booking_id"/>
<one-to-many class="model.Booking"/>
</set>


</class>
</hibernate-mapping>


thanks
rasmus