dtsur wrote:
From documentation, I realized that Hibernate will determine whether to insert or update an object based on the object id, if null-> insert, else update (Reservation: when generator method is not assigned, e.g. identity).
If that so, I wonder whether I can enforce hibernate to insert the object although its Id exists.
Today, although the insert operation is cascading to the referenced objects, it recognizes that the objects were already created in the past and doesn't make the necessary duplication (of course with a new given ID)
Thanks in advance
Daphna
Wouldn't that be very likely to result in PK constraint violations?