I have a version tag:
<version name="civUpdateDt" type="dbtimestamp">
<column name="CIV_UPDATE_DT" not-null="false" default="0"/>
</version>

Everything works fine except on the first update because the column CIV_UPDATE_DT is null. Hibernate throws the Stale Object State Exception even when I pass in a null value for that column. Is there a way around this?

thanks,
Peter

I've figured out why this is happening by looking at Hibernates SQL:

update EID.CIVILIANS set CIV_UPDATE_BY = 'John', CIV_UPDATE_DT=?, CIV_FNAME=? where CIV_ID=? and CIV_UPDATE_DT=?

if the CIV_UPDATE_DT is null then it should be:

CIV_UPDATE_DT is ?
not
CIV_UPDATE_DT=?

The database updates 0 rows because of this and Hibernate throws a row mismatch exception, which gets converted to a StaleObjectStateException. Is there any fix for this? Putting CIV_UPDATE_DT in the where clause doesn't seem necessary if Hibernate has already done the check.

Just to answer this, Hibernate really doesn't support null values for the version fields. Most of the time this shouldn't be a problem, we just have a quirky database that has two timestamp fields, one for insert and one for update.