Hibernate version: 2.1.7c

Senario:
The user creates a new 'estimate' the estimate's composite PK has the estimate number in it. The user is allowed to enter in the estimate number. If the user enters a number that is pre-existing they will recieve a duplicate key entry when they attempt to save. Yes, the transaction was rolled back and the session is then discarded.

Which is correct. However, the object that was attempted to be saved had its version automatically updated by Hibernate even though the save failed.

Is this the proper behavior?

-David