Hibernate version: 3.0.2

Is there an equivalent to XDoclet's unsaved-value in Hibernate Annotations?

Or how would Hibernate know that '0' is my unsaved value identifier when my id type is 'int'?

Rgds, Ales

no problem for hibernate 3, it knows that for int id, unsaved-value = 0

How about if I wanted to set unsaved value to '-1' or some other x != 0?

Hibernate will either use the timestamp or version property, or will actually query the second-level cache or, worst case, the database, to see if the row exists in hibernate3 at least for assigned generators.
I hope we'll no longer need the error-prone unsaved-value anymore.