I have a table that has a primary key and another value that is not a primary/foreign key, but is set as a not-null IDENTITY that is incremented by 1.

How do I set this up in my mappings? This is what I am currently doing (originally generated from the database schema using a tool):



In the above historystepId is the primary key, and historyOrder is just another column in the database that happens to be an IDENTITY. But this mapping does not work because historyOrder is not-null and passing null to a not-null property causes hibernate to throw an error when inserting.

Normally with a auto-incremented primary key you can set the id to null and have the database generate the id for you and hibernate gladly passes the generated id back to you. Is there any way to get this non-primary identity column to work in hibernate3?

(I already tried removing not-null in the historyOrder property mapping)

Have you tried adding insert="false" update="false" to the property? that should keep Hibernate from throwing the error, but I don't think historyOrder will get updated with the generated value on insert. You would have to do a Session.refresh() to see the value, probably.

Thanks, I gave that a shot but hibernate still complains:


org.hibernate.PropertyValueException: not-null property references a null or transient value: com.mycompany.dto.history.historyOrder

Oh, you might have to change the type from long to java.lang.Long. I've gotten it to work with a java.lang.String. I didn't have unique="true", though, so you could see if removing that helps, too.

You were right, I was putting update=false and insert=false in the wrong place, but this worked:



Thanks for your help Nathan!