I have an existing database to which I am adding a hibernate 2.1 persistence layer. The database performs extensive modification logging and versioning.

In order to get hibernate versioning to work I need set the initial of version to 1. Then hibernate inserts the record with version equal to 1 and performs an update setting the version number to 2.

This creates two problems for me 1: After initial entry the version of the record is 2 instead of 1. 2: My modification log shows two versions of the record.

Since my database is already responsible for mainting version numbers it iqnores the initial value of the version on insert and sets the version number to 1 anyway. This is why I must default the value to 1 to get Hibernate versioning to work at all. It also increments the veresion number via triggers on update ignoring any new value set in the update statement.

My Question is:

Is there anyway to tell hibernate to use the version number in the where clause but not put it in the update clause and more importantly not execute the extra update statement to increment the version number after insert?

Well, the problem is the useless update. Tell me:

(1) the version of Hibernate
(2) the mapping
(3) the code you use to save the object[/quote]

[quote="gavin"]Well, the problem is the useless update. Tell me:

(1) the version of Hibernate

version 2.1 final (12.12.2003)

(2) the mapping

<?xml version="1.0"?>
<!DOCTYPE hibernate-mapping PUBLIC
"-//Hibernate/Hibernate Mapping DTD//EN"
"http://hibernate.sourceforge.net/hibernate-mapping-2.0.dtd" >

<hibernate-mapping>
<class
name="com.netregulus.persistent.core.StrategicIssue"
table="A_STRATEGIC_ISSUE"
dynamic-update="true"
dynamic-insert="true"
>
<id
name="strategicIssueId"
type="java.lang.Long"
column="STRATEGIC_ISSUE_ID"
unsaved-value="null"
>
<generator class="native">
<param name="sequence">seq_strategic_issue</param>
</generator>
</id>
<version
name="version"
column="VERSION"
type="java.lang.Integer"
/>
<property
name="issueDate"
type="java.sql.Timestamp"
column="ISSUE_DATE"
length="7"
>
..... lots more propertes and sets

(3) the code you use to save the object

It's a struts application. I store the business objects and original session on the users session between requests. On user submission I reconnect the session and execute the following code.

session.reconnect();
tx = session.beginTransaction();
if (!session.contains(object)) // in case the object to save is new and wan't loaded by the session
session.saveOrUpdate(object);
session.flush();
tx.commit();
session.disconnect();

Please upgrade to 2.1.3.

I don't see version 2.1.3 on the source forge download page. Do I need to build it from cvs?